Notice history

99.9725% uptime

01 Mar 2025 · 99.9910%01 Apr · 99.9560%31 May · 99.9709%

01 Mar 202599.9910% uptime

01 Apr 202599.9560% uptime

31 May 202599.9709% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

83.3333% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

0.0000% uptime

01 Mar 2025 · 0.0000%01 Apr · 0.0000%31 May · 0.0000%

01 Mar 20250.0000% uptime

01 Apr 20250.0000% uptime

31 May 20250.0000% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

100.000% uptime

01 Mar 2025 · 100.000%01 Apr · 100.000%31 May · 100.000%

01 Mar 2025100.000% uptime

01 Apr 2025100.000% uptime

31 May 2025100.000% uptime

View current status

01 May 2025

ResolvedTuesday 27, May, 2025 at 8:18 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingTuesday 27, May, 2025 at 8:17 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedSunday 11, May, 2025 at 6:51 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingSunday 11, May, 2025 at 6:50 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedFriday 09, May, 2025 at 1:14 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingFriday 09, May, 2025 at 1:12 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedThursday 08, May, 2025 at 2:37 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingThursday 08, May, 2025 at 2:36 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedFriday 02, May, 2025 at 8:57 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingFriday 02, May, 2025 at 8:54 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Apr 2025

ResolvedWednesday 30, April, 2025 at 9:28 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingWednesday 30, April, 2025 at 9:26 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMonday 14, April, 2025 at 10:59 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingMonday 14, April, 2025 at 10:57 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMonday 14, April, 2025 at 5:02 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingMonday 14, April, 2025 at 4:58 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMonday 14, April, 2025 at 3:40 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingMonday 14, April, 2025 at 3:35 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedSunday 13, April, 2025 at 2:11 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingSunday 13, April, 2025 at 2:10 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Mar 2025

ResolvedThursday 06, March, 2025 at 11:47 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingThursday 06, March, 2025 at 11:46 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedTuesday 04, March, 2025 at 12:02 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingTuesday 04, March, 2025 at 12:01 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Mar 2025 to 01 May 2025

Ahrism1 - Notice history

r/Ahrism experiencing major outage

Notice history

01 May 2025

01 Apr 2025

01 Mar 2025