On May 9, 2026, the cloud service landscape experienced several notable incidents, including multiple outages from various providers alongside reported degraded performances. While some issues were promptly resolved, the ongoing outage of M-Pesa overshadowed the day, impacting its availability drast…
losclouds research
Availability archive · 3 min read · 517 words
On May 9, 2026, the cloud service landscape experienced several notable incidents, including multiple outages from various providers alongside reported degraded performances. While some issues were promptly resolved, the ongoing outage of M-Pesa overshadowed the day, impacting its availability drastically. The monitoring insights from losclouds.com provide critical visibility into an unusual day for many cloud services.
- Start Time: 2026-05-09
- Duration: 25 minutes
- Updates: 2
- Impact: The outage, detected early in the day, was resolved swiftly with minimal user impact, reflecting strong incident management practices.
- Start Time: 2026-05-09
- Duration: 25 minutes
- Updates: 2
- Impact: Users experienced brief interruptions in workflow management capabilities, but services were restored quickly.
- Start Time: 2026-05-09
- Duration: 26 minutes
- Updates: 2
- Impact: Similar to Retool Workflows, this outage led to temporary service disruption but was resolved promptly, minimizing overall impact.
- Start Time: 2026-05-09
- Duration: 30 minutes
- Updates: 2
- Impact: This service disruption affected translation capabilities for users, but was also resolved within a short time frame.
- Start Time: 2026-05-09
- Duration: 20 minutes
- Updates: 2
- Impact: Users reported a brief denial of access, quickly addressed by the maintenance teams.
- Start Time: 2026-05-09
- Duration: 41 minutes
- Updates: 2
- Impact: This outage was among the longer incidents of the day, causing significant inconvenience before teams managed to restore services.
- Start Time: 2026-05-09
- Duration: 20 minutes
- Updates: 2
- Impact: Users experienced sluggish performance, which may have affected fulfillment operations but was resolved without extensive downtime.
- Start Time: 2026-05-09
- Duration: 21 minutes
- Updates: 2
- Impact: The degraded performance was noted by users, though it was resolved quickly.
- Start Time: 2026-05-09
- Duration: 21 minutes
- Updates: 2
- Impact: Users reported performance issues while accessing services, but Yelp corrected the issues in a timely manner.
- Start Time: 2026-05-07
- Duration: Ongoing
- Updates: 1
- Impact: M-Pesa continues to experience a total outage, with a 0.00% uptime reported and significant user complaints highlighting the critical nature of this incident.
| Metric | Value |
|---|---|
| Total Incidents | 10 |
| Total Outages | 7 |
| Total Degraded Services | 3 |
| Ongoing Outage | 1 |
| Providers Monitored | 30+ |
| Average Response Times | Varies (Notable low for M-Pesa: 0ms) |
As we look forward, the situation with M-Pesa remains a primary concern, with ongoing impacts on user operations. It will be crucial for the service to address the outage swiftly to regain user trust. The other providers have shown resilience with quick resolutions to their incidents today. Continuous monitoring and proactive incident management will be essential in mitigating future disruptions, and we encourage all providers to enhance their incident response strategies to minimize impact on customer experience.