|
By Hrishikesh Barua
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).
|
By Hrishikesh Barua
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.
|
By Hrishikesh Barua
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.
|
By Hrishikesh Barua
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).
|
By Hrishikesh Barua
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.
|
By Hrishikesh Barua
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.
|
By Hrishikesh Barua
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.
|
By Hrishikesh Barua
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.
|
By Hrishikesh Barua
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.
|
By Hrishikesh Barua
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.
- July 2026 (5)
- June 2026 (2)
- May 2026 (1)
- April 2026 (2)
- March 2026 (1)
- February 2026 (1)
- January 2026 (1)
- December 2025 (1)
- November 2025 (1)
- October 2025 (2)
- August 2025 (2)
- July 2025 (2)
- May 2025 (1)
- April 2025 (1)
- March 2025 (2)
- January 2025 (1)
- December 2024 (5)
- November 2024 (5)
- October 2024 (5)
- September 2024 (4)
- August 2024 (3)
- July 2024 (1)
- June 2024 (1)
- May 2024 (1)
The early warning system for all your third-party cloud and SaaS services. Get notified proactively and prevent incidents in third party vendors from affecting your applications.
IncidentHub monitors public status pages of all your third-party services and alerts you when there are incidents:
- Monitor All Your Cloud and SaaS Service Vendors: We support all major Cloud and SaaS services. Don't see one that you use? Let us know and we will add it.
- Use It out of the Box: We focus on simplicity. You can start monitoring your service vendors in just a couple of steps.
- Receive Real Time Notifications: Receive notifications when there is an outage in one of the services you depend on.
- Plug Into Your Existing Tools: Seamlessly integrate with your existing notification and alerting ecosystem - no need to install anything new.
Monitor All Your Third-Party Cloud and SaaS Services in One Place.