losclouds research
Availability archive · 3 min read · 544 words
Today, May 15, 2026, was marked by significant service disruptions across multiple cloud providers, notably affecting user experiences with several major platforms. The notable incidents included widespread outages for Mind, Wattpad, Kindle, Nubank, N26, and others, with ongoing issues at Mojeek and M-Pesa. The response times for these services also showed considerable delays, indicating heightened strain on their respective infrastructures.
Major Incidents
Outages
- Wattpad
- Incident: Outage detected
- Duration: 19 minutes
- Timeline: Disruption began in the morning and resulted in limited accessibility for users, with two updates provided to keep users informed of recovery efforts.
- Kindle
- Incident: Outage detected
- Duration: 21 minutes
- Timeline: Similar to Wattpad, Kindle faced an outage that was resolved relatively quickly, though it left many users without access to their services during this time.
- Nubank
- Incident: Outage detected
- Duration: 50 minutes
- Timeline: Users saw issues starting from the morning until services were restored post-incident communication.
- N26
- Incident: Outage detected
- Duration: 40 minutes
- Timeline: Users experienced a short yet impactful disruption that was communicated promptly.
- Mojeek
- Incident: Ongoing outage
- Timeline: Started earlier in the day and continues to affect user access. Reports indicate high customer impact, with latency and accessibility issues persisting, necessitating swift attention from their technical teams.
- M-Pesa
- Incident: Ongoing outage
- Timeline: Issues began on May 7, 2026, and have not yet been resolved, resulting in a complete service disruption and zero checks passing. Users are actively reporting issues, indicating significant frustration within the community.
Degraded Performance
- Minds
- Incident: Degraded performance
- Duration: 11 hours and 42 minutes (multiple reports)
- Timeline: Throughout the day, accessibility has been intermittently impacted, evidenced by multiple updates confirming the responsiveness of the service is not optimal.
- Magazine Luiza
- Incident: Degraded performance
- Duration: Totaled over 5 hours (across multiple instances).
- Timeline: The service showed multiple periods of degraded performance, notifying users about issues that ultimately took time to resolve despite stretches of downtime for the full outage previously recorded on May 14.
By the Numbers
| Metric | Value |
|---|---|
| Total Incidents | 37 |
| Resolved Incidents | 34 |
| Ongoing Outages | 2 |
| Lowest Availability | M-Pesa: 0.00% uptime |
| Worst Average Response | Mojeek: 7661ms avg response |
| High Response Stability | Checkio: 97.98% uptime |
Community Outage Reports
Increased community feedback for providers experiencing disruptions included two reports each for:
- Mojeek
- M-Pesa
- Namshi
- Magazine Luiza
Additionally, user reports recognized Amazon Web Services and smaller platforms like Civitai and Roboflow as experiencing minor disruptions.
Response Time Anomalies
No significant anomalies in response times were identified today, which may suggest that issues were largely related to outages rather than performance inconsistencies.
Looking Ahead
As we move forward, the focus remains on monitoring the ongoing disruptions at Mojeek and M-Pesa, which are significantly impacting user access and satisfaction. Improvements in communication and transparency from providers regarding incident resolutions and performance assessments will be crucial in restoring trust among their user bases. We encourage users to report any issues they encounter to ensure that we can track service health effectively.