Notice history

01 Dec 202499.9821% uptime

01 Jan 202599.9597% uptime

28 Feb 202599.9231% uptime

01 Dec 20240.0000% uptime

01 Jan 20250.0000% uptime

28 Feb 202520.8557% uptime

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

01 Dec 2024100.000% uptime

01 Jan 2025100.000% uptime

28 Feb 2025100.000% uptime

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

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

Resolved
Thursday 20, February, 2025 at 8:15 PM
Resolved
Thursday 20, February, 2025 at 8:15 PM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Thursday 20, February, 2025 at 8:11 PM
Investigating
Thursday 20, February, 2025 at 8:11 PM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Thursday 20, February, 2025 at 4:00 PM
Resolved
Thursday 20, February, 2025 at 4:00 PM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Thursday 20, February, 2025 at 3:59 PM
Investigating
Thursday 20, February, 2025 at 3:59 PM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

Resolved
Monday 17, February, 2025 at 4:02 AM
Resolved
Monday 17, February, 2025 at 4:02 AM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Monday 17, February, 2025 at 4:00 AM
Investigating
Monday 17, February, 2025 at 4:00 AM
Ahrism1 cannot be accessed at the moment. This incident was created by an automated monitoring service.

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

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

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

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

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

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

Resolved
Wednesday 18, December, 2024 at 6:37 PM
Resolved
Wednesday 18, December, 2024 at 6:37 PM
Ahrism1 is now operational! This update was created by an automated monitoring service.
Investigating
Wednesday 18, December, 2024 at 6:35 PM
Investigating
Wednesday 18, December, 2024 at 6:35 PM
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