Notice history

99.9485% uptime

01 Dec 2024 · 99.9821%01 Jan 2025 · 99.9597%28 Feb · 99.9008%

01 Dec 202499.9821% uptime

01 Jan 202599.9597% uptime

28 Feb 202599.9008% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

83.3333% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

0.0000% uptime

01 Dec 2024 · 0.0000%01 Jan 2025 · 0.0000%28 Feb · 0.0000%

01 Dec 20240.0000% uptime

01 Jan 20250.0000% uptime

28 Feb 20250.0000% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

100.000% uptime

01 Dec 2024 · 100.000%01 Jan 2025 · 100.000%28 Feb · 100.000%

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

View current status

01 Feb 2025

ResolvedWednesday 26, February, 2025 at 5:39 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingWednesday 26, February, 2025 at 5:37 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedMonday 24, February, 2025 at 1:25 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingMonday 24, February, 2025 at 1:24 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedSunday 23, February, 2025 at 5:17 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingSunday 23, February, 2025 at 5:14 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedSaturday 22, February, 2025 at 4:41 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingSaturday 22, February, 2025 at 4:38 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedThursday 20, February, 2025 at 8:20 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingThursday 20, February, 2025 at 8:16 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Jan 2025

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

ResolvedFriday 17, January, 2025 at 2:35 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingFriday 17, January, 2025 at 2:32 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedThursday 09, January, 2025 at 5:17 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingThursday 09, January, 2025 at 5:11 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedThursday 09, January, 2025 at 11:06 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingThursday 09, January, 2025 at 11:03 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Dec 2024

ResolvedSaturday 28, December, 2024 at 4:43 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingSaturday 28, December, 2024 at 4:42 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedThursday 26, December, 2024 at 5:57 AMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingThursday 26, December, 2024 at 5:55 AMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

ResolvedWednesday 18, December, 2024 at 6:37 PMUTC
Ahrism1 is now operational! This update was created by an automated monitoring service.
InvestigatingWednesday 18, December, 2024 at 6:35 PMUTC
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

01 Dec 2024 to 01 Feb 2025

Ahrism1 - Notice history

r/Ahrism experiencing major outage

Notice history

01 Feb 2025

01 Jan 2025

01 Dec 2024