Notice history

99.9084% uptime

01 Jun 2025 · 99.9005%01 Jul · 99.8656%31 Aug · 99.9619%

01 Jun 202599.9005% uptime

01 Jul 202599.8656% uptime

31 Aug 202599.9619% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

83.3333% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

0.0000% uptime

01 Jun 2025 · 0.0000%01 Jul · 0.0000%31 Aug · 0.0000%

01 Jun 20250.0000% uptime

01 Jul 20250.0000% uptime

31 Aug 20250.0000% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

100.000% uptime

01 Jun 2025 · 100.000%01 Jul · 100.000%31 Aug · 100.000%

01 Jun 2025100.000% uptime

01 Jul 2025100.000% uptime

31 Aug 2025100.000% uptime

View current status

01 Aug 2025

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

ResolvedTuesday 12, August, 2025 at 7:01 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingTuesday 12, August, 2025 at 6:59 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMonday 11, August, 2025 at 11:43 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingMonday 11, August, 2025 at 11:41 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMonday 11, August, 2025 at 2:03 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingMonday 11, August, 2025 at 2:00 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

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

01 Jul 2025

ResolvedMonday 21, July, 2025 at 12:41 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingMonday 21, July, 2025 at 12:39 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedSunday 20, July, 2025 at 1:30 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingSunday 20, July, 2025 at 1:28 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedThursday 17, July, 2025 at 4:55 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingThursday 17, July, 2025 at 4:52 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

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

ResolvedWednesday 16, July, 2025 at 10:25 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingWednesday 16, July, 2025 at 10:22 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Jun 2025

ResolvedMonday 30, June, 2025 at 5:27 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingMonday 30, June, 2025 at 5:23 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedSunday 29, June, 2025 at 2:11 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingSunday 29, June, 2025 at 2:07 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedFriday 27, June, 2025 at 7:58 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingFriday 27, June, 2025 at 7:55 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedFriday 27, June, 2025 at 5:50 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingFriday 27, June, 2025 at 5:47 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedWednesday 25, June, 2025 at 9:44 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingWednesday 25, June, 2025 at 9:42 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Jun 2025 to 01 Aug 2025

Ahrism1 - Notice history

r/Ahrism experiencing major outage

Notice history

01 Aug 2025

01 Jul 2025

01 Jun 2025