Operations | Monitoring | ITSM | DevOps | Cloud

In the last few months we have focused more on improving the usefulness of our service status pages, added new sections for outages and reliability, and improved SEO (that's part of the business!). Product changes include new services and improvements in parsing and detection.

Some users in Germany and the United Kingdom who reach Microsoft 365 through Global Secure Access (GSA) may have been unable to use Outlook, Outlook on the web, OneDrive, SharePoint Online, Microsoft Teams and Windows 365 Cloud PCs on October 13, 2026, according to Microsoft's service health updates as recorded by IncidentHub. Microsoft's final update records the start at 07:40 UTC and the end at 18:31 UTC the same day - about 10 hours 51 minutes - and narrows the geographic scope to Germany only.

Google Cloud Storage in us-central1 (Iowa) had elevated latency and error rates on upload and write operations on October 8, 2026, and a smaller subset of reads was also affected, according to Google's incident page. Google records the start at 11:00 UTC and the end at 23:30 UTC the same day - 12 hours 30 minutes. The outage report - fetched on October 12, 2026 - includes a preliminary incident report as of this writing.

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.

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.

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.

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).

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.

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.

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).