Notice history - Calamity, Inc. - Status

May 2026

Jun 2026

Jul 2026

May 2026

Jun 2026

Jul 2026

May 2026

Jun 2026

Jul 2026

May 2026

Jun 2026

Jul 2026

Notice history

Jul 2026

Resolved
July 11, 2026 at 8:51 PMUTC
Resolved
July 11, 2026 at 8:51 PMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
July 11, 2026 at 8:46 PMUTC
Investigating
July 11, 2026 at 8:46 PMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
July 10, 2026 at 10:22 PMUTC
Resolved
July 10, 2026 at 10:22 PMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
July 10, 2026 at 10:17 PMUTC
Investigating
July 10, 2026 at 10:17 PMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
July 10, 2026 at 8:21 PMUTC
Resolved
July 10, 2026 at 8:21 PMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
July 10, 2026 at 8:16 PMUTC
Investigating
July 10, 2026 at 8:16 PMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
July 10, 2026 at 6:30 AMUTC
Resolved
July 10, 2026 at 6:30 AMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
July 10, 2026 at 6:25 AMUTC
Investigating
July 10, 2026 at 6:25 AMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
July 09, 2026 at 8:25 PMUTC
Resolved
July 09, 2026 at 8:25 PMUTC
Main is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
July 09, 2026 at 8:20 PMUTC
Investigating
July 09, 2026 at 8:20 PMUTC

Jun 2026

Resolved
June 30, 2026 at 11:06 PMUTC
Resolved
June 30, 2026 at 11:06 PMUTC
Stand Relay is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
June 30, 2026 at 11:01 PMUTC
Investigating
June 30, 2026 at 11:01 PMUTC

Resolved
June 30, 2026 at 9:35 PMUTC
Resolved
June 30, 2026 at 9:35 PMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
June 30, 2026 at 9:30 PMUTC
Investigating
June 30, 2026 at 9:30 PMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
June 30, 2026 at 11:41 AMUTC
Resolved
June 30, 2026 at 11:41 AMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
June 30, 2026 at 11:36 AMUTC
Investigating
June 30, 2026 at 11:36 AMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
June 29, 2026 at 6:30 PMUTC
Resolved
June 29, 2026 at 6:30 PMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
June 29, 2026 at 6:25 PMUTC
Investigating
June 29, 2026 at 6:25 PMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
June 28, 2026 at 10:47 PMUTC
Resolved
June 28, 2026 at 10:47 PMUTC
Stand Relay is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
June 28, 2026 at 10:42 PMUTC
Investigating
June 28, 2026 at 10:42 PMUTC

May 2026

Resolved
May 30, 2026 at 4:24 PMUTC
Resolved
May 30, 2026 at 4:24 PMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
May 30, 2026 at 4:19 PMUTC
Investigating
May 30, 2026 at 4:19 PMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
May 30, 2026 at 5:11 AMUTC
Resolved
May 30, 2026 at 5:11 AMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
May 30, 2026 at 5:06 AMUTC
Investigating
May 30, 2026 at 5:06 AMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
May 29, 2026 at 7:53 AMUTC
Resolved
May 29, 2026 at 7:53 AMUTC
Automatically resolved as the server successfully responded to monitoring.
Identified
May 29, 2026 at 6:15 AMUTC
Identified
May 29, 2026 at 6:15 AMUTC
The underlying node that this VM is on is currently down. We have reached out to our hoster.
Investigating
May 29, 2026 at 12:45 AMUTC
Investigating
May 29, 2026 at 12:45 AMUTC

Resolved
May 28, 2026 at 7:15 PMUTC
Resolved
May 28, 2026 at 7:15 PMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
May 28, 2026 at 7:10 PMUTC
Investigating
May 28, 2026 at 7:10 PMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

Resolved
May 28, 2026 at 4:18 PMUTC
Resolved
May 28, 2026 at 4:18 PMUTC
Signalling is back up. This incident was automatically resolved by Instatus monitoring.
Investigating
May 28, 2026 at 4:13 PMUTC
Investigating
May 28, 2026 at 4:13 PMUTC
Signalling is down at the moment. This incident was automatically created by Instatus monitoring.

May 2026 to Jul 2026