Notice history

01 Feb 202599.9008% uptime

01 Mar 202599.9910% uptime

30 Apr 202599.9630% uptime

01 Feb 20250.0000% uptime

01 Mar 20250.0000% uptime

30 Apr 202540.5718% uptime

01 Feb 2025100.000% uptime

01 Mar 2025100.000% uptime

30 Apr 2025100.000% uptime

01 Feb 2025100.000% uptime

01 Mar 2025100.000% uptime

30 Apr 2025100.000% uptime

01 Feb 2025100.000% uptime

01 Mar 2025100.000% uptime

30 Apr 2025100.000% uptime

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

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

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

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

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

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

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

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

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

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.

01 Feb 2025 to 01 Apr 2025

Ahrism1 - Notice history