Notice history

99.9756% uptime

01 May 2023 · 99.9552%01 Jun · 99.9815%31 Jul · 99.9910%

01 May 202399.9552% uptime

01 Jun 202399.9815% uptime

31 Jul 202399.9910% uptime

100.000% uptime

01 May 2023 · 100.000%01 Jun · 100.000%31 Jul · 100.000%

01 May 2023100.000% uptime

01 Jun 2023100.000% uptime

31 Jul 2023100.000% uptime

83.3333% uptime

01 May 2023 · 83.3333%01 Jun · 83.3333%31 Jul · 83.3333%

01 May 202383.3333% uptime

01 Jun 202383.3333% uptime

31 Jul 202383.3333% uptime

100.000% uptime

01 May 2023 · 100.000%01 Jun · 100.000%31 Jul · 100.000%

01 May 2023100.000% uptime

01 Jun 2023100.000% uptime

31 Jul 2023100.000% uptime

100.000% uptime

01 May 2023 · 100.000%01 Jun · 100.000%31 Jul · 100.000%

01 May 2023100.000% uptime

01 Jun 2023100.000% uptime

31 Jul 2023100.000% uptime

100.000% uptime

01 May 2023 · 100.000%01 Jun · 100.000%31 Jul · 100.000%

01 May 2023100.000% uptime

01 Jun 2023100.000% uptime

31 Jul 2023100.000% uptime

100.000% uptime

01 May 2023 · 100.000%01 Jun · 100.000%31 Jul · 100.000%

01 May 2023100.000% uptime

01 Jun 2023100.000% uptime

31 Jul 2023100.000% uptime

View current status

01 Jul 2023

Resolved
Wednesday 19, July, 2023 at 1:15 PMUTC
Resolved
Wednesday 19, July, 2023 at 1:15 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Wednesday 19, July, 2023 at 1:12 PMUTC
Investigating
Wednesday 19, July, 2023 at 1:12 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Jun 2023

Resolved
Friday 30, June, 2023 at 4:02 PMUTC
Resolved
Friday 30, June, 2023 at 4:02 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Friday 30, June, 2023 at 3:59 PMUTC
Investigating
Friday 30, June, 2023 at 3:59 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Saturday 03, June, 2023 at 9:53 PMUTC
Resolved
Saturday 03, June, 2023 at 9:53 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Saturday 03, June, 2023 at 9:50 PMUTC
Investigating
Saturday 03, June, 2023 at 9:50 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 May 2023

Resolved
Tuesday 23, May, 2023 at 9:02 AMUTC
Resolved
Tuesday 23, May, 2023 at 9:02 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Tuesday 23, May, 2023 at 8:49 AMUTC
Investigating
Tuesday 23, May, 2023 at 8:49 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Friday 19, May, 2023 at 6:20 PMUTC
Resolved
Friday 19, May, 2023 at 6:20 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Friday 19, May, 2023 at 6:18 PMUTC
Investigating
Friday 19, May, 2023 at 6:18 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Wednesday 17, May, 2023 at 11:52 PMUTC
Resolved
Wednesday 17, May, 2023 at 11:52 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Wednesday 17, May, 2023 at 11:50 PMUTC
Investigating
Wednesday 17, May, 2023 at 11:50 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 May 2023 to 01 Jul 2023

Ahrism1 - Notice history

All systems operational

Notice history

01 Jul 2023

01 Jun 2023

01 May 2023