Notice history

01 Jan 202499.9888% uptime

01 Feb 202499.9689% uptime

31 Mar 202499.9709% uptime

01 Jan 20240.0000% uptime

01 Feb 20240.0000% uptime

31 Mar 20240.0000% uptime

01 Jan 2024100.000% uptime

01 Feb 202493.6329% uptime

31 Mar 202497.1996% uptime

01 Jan 2024100.000% uptime

01 Feb 2024100.000% uptime

31 Mar 2024100.000% uptime

01 Jan 2024100.000% uptime

01 Feb 2024100.000% uptime

31 Mar 2024100.000% uptime

Resolved
Friday 29, March, 2024 at 2:56 PM
Resolved
Friday 29, March, 2024 at 2:56 PM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Friday 29, March, 2024 at 2:55 PM
Investigating
Friday 29, March, 2024 at 2:55 PM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Friday 22, March, 2024 at 11:09 AM
Resolved
Friday 22, March, 2024 at 11:09 AM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Friday 22, March, 2024 at 11:08 AM
Investigating
Friday 22, March, 2024 at 11:08 AM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Saturday 16, March, 2024 at 7:51 PM
Resolved
Saturday 16, March, 2024 at 7:51 PM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Saturday 16, March, 2024 at 7:47 PM
Investigating
Saturday 16, March, 2024 at 7:47 PM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Saturday 02, March, 2024 at 10:47 PM
Resolved
Saturday 02, March, 2024 at 10:47 PM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Saturday 02, March, 2024 at 10:44 PM
Investigating
Saturday 02, March, 2024 at 10:44 PM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Wednesday 28, February, 2024 at 9:14 PM
Resolved
Wednesday 28, February, 2024 at 9:14 PM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Wednesday 28, February, 2024 at 9:04 PM
Investigating
Wednesday 28, February, 2024 at 9:04 PM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Saturday 24, February, 2024 at 5:32 AM
Resolved
Saturday 24, February, 2024 at 5:32 AM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Saturday 24, February, 2024 at 5:31 AM
Investigating
Saturday 24, February, 2024 at 5:31 AM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Sunday 03, March, 2024 at 9:26 PM
Resolved
Sunday 03, March, 2024 at 9:26 PM
This incident has been resolved.
Monitoring
Friday 23, February, 2024 at 8:17 PM
Monitoring
Friday 23, February, 2024 at 8:17 PM
We implemented a fix and are currently monitoring the result.

Resolved
Wednesday 31, January, 2024 at 10:36 AM
Resolved
Wednesday 31, January, 2024 at 10:36 AM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Wednesday 31, January, 2024 at 10:35 AM
Investigating
Wednesday 31, January, 2024 at 10:35 AM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Saturday 13, January, 2024 at 11:10 PM
Resolved
Saturday 13, January, 2024 at 11:10 PM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Saturday 13, January, 2024 at 11:08 PM
Investigating
Saturday 13, January, 2024 at 11:08 PM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Jan 2024 to 01 Mar 2024

Ahrism1 - Notice history