StatusCast incident

Status pages and admin application unavailable

Resolved after 1 day 20 hours, affecting Status pages and Admin application and 1 more, on April 4, 2026.

resolved Apr 05, 2026, 09:00 PM UTC

In working with Microsoft, StatusCast’s team confirmed that the disruption was due to an outage with SQL Databases located in Azure’s US East region which is where StatusCast is primarily hosted: StatusCast itself was impacted by this outage from approximately 8:19 PM EDT and had fully recovered by 9:03 PM EDT. StatusCast’s team will continue to work closely with Microsoft to further optimize its offering to help ensure that impact of service provider outages is as minimal as possible.

Started
Apr 04, 2026, 12:19 AM UTC
Resolved
Apr 05, 2026, 09:00 PM UTC
Duration
1d 20h
Detected by Pingoru
Apr 04, 2026, 12:19 AM UTC

Affected components

Status pagesAdmin applicationStatus pagesAdmin applicationStatus pagesAdmin applicationStatus pagesAdmin application

Update timeline

  1. identified Apr 04, 2026, 12:19 AM UTC

    At approximately 8:19PM EDT, StatusCast’s engineers were alerted that some status page and admin applications were inaccessible. The team identified that its hosting partner, Microsoft, was experiencing some issues in its US East region related to app services and SQL databases connections. As of 9:03PM EDT services have been restored and StatusCast’s team is currently working with Microsoft to fully investigate the incident. Once the team has completed it’s investigation we will follow up with an RCA. At this time StatusCast should be operating fully as expected, if you continue to have any further issues please contact us at [email protected]

  2. resolved Apr 04, 2026, 01:03 AM UTC

    As of 9:03PM EDT services have been restored and StatusCast’s team is currently working with Microsoft to fully investigate the incident. Once the team has completed it’s investigation we will follow up with an RCA.

  3. resolved Apr 05, 2026, 09:00 PM UTC

    In working with Microsoft, StatusCast’s team confirmed that the disruption was due to an outage with SQL Databases located in Azure’s US East region which is where StatusCast is primarily hosted: StatusCast itself was impacted by this outage from approximately 8:19 PM EDT and had fully recovered by 9:03 PM EDT. StatusCast’s team will continue to work closely with Microsoft to further optimize its offering to help ensure that impact of service provider outages is as minimal as possible.

Your product runs on more than StatusCast

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →