Hrishikesh Barua

Introduction​

Railway-hosted domains returned HTTP 404 to new connections in all four Railway regions on September 30, 2026, for about five minutes between roughly 07:35 and 07:40 UTC. This happened after a new version of Railway's routing service went live before the database schema change it depended on had been applied. Railway's report says its running workloads were not affected and no data was lost, and existing connections stayed up, although some private networking lookups between services failed in the same window.

Railway's first public status update went out at 07:48 UTC, about eight minutes after routing had recovered, and described itself as a "post facto" report. The incident was marked resolved at 08:17 UTC, and Railway published a detailed incident report on its blog at 22:42 UTC the same day.

Introduction​

IncidentHub tracked 30,246 outages across 1,082 providers between January and June 2026. Dependency risk is a major factor when your business depends on third-party services. A vendor outage monitor and status page aggregator can help you stay on top of which vendors are down, and which are up.

UptimeRobot announced in July 2026 that it had acquired the status page aggregator IsDown. IsDown's own announcement had said earlier that the product, name, team, and prices would stay the same, with billing moving to UptimeRobot. If you are looking at other options, here is a list of some tools that do the same job.

Sites like Downdetector work differently, using reports from users rather than official status pages, so they aren't in this list.

Every feature and plan below was taken from each product's own website on September 21, 2026, named in each section. Products change, so please check the named sites before you decide.

Introduction​

Namecheap took more than 5,000 servers offline on August 13, 2026 after cooling systems failed at RadiusDC's Phoenix datacenter, and brought services back in stages over roughly 28 and a half hours. The shutdown was deliberate, intended to protect hardware from overheating. It reached most of the product line - hosting, EasyWP, Private Email, DNS management, URL redirect management and the support helpdesk - while DNS zone resolution was unaffected. The emergency maintenance post opened at 12:35 UTC on August 13 and was marked resolved at 17:00 UTC on August 14.

Last updated on August 12, 2026.

Introduction​

On August 6, 2026, GitHub opened an incident for degraded Actions performance at 15:22 UTC. Within about twenty minutes, Actions availability was listed as degraded, workflow runs were failing to start or failing partway through, and the Actions REST API was returning errors. Pages was pulled into the same incident shortly afterwards. The status page marked Actions and Pages as mitigated at 00:05 UTC on August 7, and closed the incident at 02:04 UTC.

What the live updates showed at the time was a multi-hour recovery through constrained capacity, throttled webhooks, invalid job assignment, and self-hosted runner problems - followed by cleanup work that continued after the incident was marked resolved. GitHub added a root cause analysis to the incident page on 11 August 2026, appended to the 7 August resolve post rather than as a separate update.

What's New in IncidentHub in July 2026?​

IncidentHub's latest product update includes a Multi-Client plan built specifically for MSPs and agencies with per-client status pages, service components as top-level objects on status pages, and support for more vendors (1125+ and counting).

Introduction​

On July 24, 2026, AWS lost connectivity between the us-west-2 (Oregon) region and the Seattle Metro. The initial impact window was 20 minutes for most and 1 hour 17 minutes for a few customers using AWS Direct Connect through EqSe2, Westin Building Exchange, Seattle. Any traffic that both started and ended inside the region kept working, whereas anything crossing the region boundary saw timeouts and errors. This included the AWS Management Console for some customers.

Downstream services took longer to recover. IncidentHub recorded 9 confirmed cascade incidents across 7 providers, and 3 possible cascade events at 3 more.

Introduction​

On July 23, 2026, Microsoft Azure experienced a connectivity outage in the West US region that blocked traffic entering or leaving the region for nearly five hours. Workloads that stayed entirely inside West US were not affected. Microsoft's preliminary Post Incident Review (PIR) attributes the failure to a bug in maintenance request conversion software that removed IP routes from more devices than intended during routine device maintenance.

IncidentHub detected a wave of downstream SaaS outages tied to the Azure incident. Acknowledgement times on those status pages varied widely - from a few minutes to more than three hours after Azure's impact began.

Introduction​

Last updated on October 7, 2026.

The first half of 2026 reinforced a key idea about Cloud and SaaS reliability - dependency risk. IncidentHub tracked 30,246 outages across 1,082 providers between January and June 2026. May was the busiest month, with 6,070 incidents. Cloud providers led in the total number of outages (4,723), followed closely by developer tools (4,589).

Besides volume, AI providers moved firmly into the production infrastructure layer with LLM outages resulting in disruption across EdTech, developer tooling, customer support, and communication tools. Automation created new failure modes of its own: Google Cloud's May suspension of Railway's account resulted in almost all their workloads being unavailable. Edge and CDN incidents kept multiplying downstream, IAM remained a login bottleneck for entire product stacks, and Canvas's May security incident took classrooms offline during exam season.

This report breaks down H1 2026 by layer - cloud, edge and DNS, IAM, developer tools, collaboration, AI, payments, observability, and EdTech - with the major incidents, category trends, and cascade patterns based on the data.

Introduction​

On July 16, 2026, AWS experienced a disruption in its CloudFront service, which affected a large number of websites and applications. The outage was caused by a configuration loading failure in CloudFront's VPC Origins feature. This was AWS's most widely-felt outage after last year's outage on October 20th, which caused widespread damage.

Last updated on September 23, 2026.

Introduction​

Handling client calls when a third-party vendor has an outage - this will sound familiar if you are a managed service provider (MSP). Your first instinct would be to check if the vendor's status page or social media handle shows anything, or check crowdsourced websites like Downdetector. Or even ask your client to check themselves.

These approaches do not scale when you have more than a few clients, many vendor status pages to check, and clients with different stacks. Public status pages do not always show your client specific issues (e.g. Microsoft 365, Microsoft Azure). Crowdsourced websites can have false positives, and you are delegating something that you should have handled yourself to a third-party website.

This article is about two different strategies you can use to close the gap. Both give your clients an automatically updated status view of the third-party SaaS and Cloud services they depend on, with data gathered from official sources, under your brand. One is a hosted, white-labeled status page you switch on and never have to build. The other is a dashboard you build yourself on top of a live data feed. Which one fits your situation depends on whether you have developers and what you've already got running.

What's New in IncidentHub in June 2026?​

IncidentHub's latest product update includes private status ingestion for Microsoft Azure and Microsoft 365, a simpler UI for alerts configuration, an option to disable the public status page, and a better looking status page layout. Plus, support for more vendors (1070+ and counting).

As always, I am grateful to all our customers and beta testers who have shared their feedback which has made IncidentHub better.

What's New in IncidentHub in May 2026?​

IncidentHub's latest product updates include a new Business plan with Teams support, early outage detection v1, and more integrations with ticketing systems. The public status now includes a disable feature. As before, many features are driven by feedback, and I am grateful to all our customers who have shared their feedback with us.

Executive Summary​

Hashicorp's co-founder Mitchell Hashimoto decided to pull out his Ghostty project from GitHub in April 2026 due to GitHub's reliability issues. He did this after 18 years of using GitHub, saying that GitHub "is no longer a place for serious work".

GitHub has experienced a significant decline in reliability over the past 6 months, and Hashimoto is not alone in expressing this sentiment. In the past 12 months, GitHub has experienced 48 major outages, including outages in GitHub Actions, Copilot, Pull Requests, and core Git operations.

This article analyzes in depth GitHub's outage history between May 2025 and April 2026, the possible causes, and the impact on developers and businesses. IncidentHub has monitored every GitHub outage for the past 12 months and beyond - read on to find out what the data reveals.

The Alert Fatigue Problem in SaaS Dependent Teams​

IncidentHub tracked 48000 SaaS and Cloud outages in 2025. The average organization depends on 100+ SaaS apps, making third-party vendor monitoring a crucial aspect of risk management and business continuity for almost all modern organizations.

Better SaaS outage alerting is about monitoring the right parts of your third-party services, and routing alerts to the right people at the right time.

This article covers the six criteria that separate useful cloud outage alerts from noisy ones, how IncidentHub's alerting works, real-world scenarios where it matters, and who this tool is built for.

Introduction​

IncidentHub's latest product updates focus on improving the public status page, adding integrations with ticketing systems, private status page ingestion, and making the notifications more useful to the end user. Some of these improvements are driven by user feedback.

Feedback is what makes the product better, and I am personally grateful to all our customers who have shared their feedback with us.