Daily Cloud Availability Digest — May 2, 2026

On May 2, 2026, the cloud service landscape experienced a considerable number of incidents, primarily affecting the availability and performance of multiple providers. A total of 15 outages and degraded services were recorded, with notable incidents from Capcom, which faced several disruptions. User impact was evident, as several services recorded below-average uptime ratings and escalated response times. This report outlines the major incidents of the day, the availability scores that reflect the overall health of the providers, and key metrics to summarize the day's events.

Incidents

Capcom

Capcom experienced a total of five outages across the day, significantly impacting user experience. The incidents unfolded as follows:

• Incident 1: Outage detected at 10:15 AM, lasting approximately 30 minutes. Users reported service disruptions.
• Incident 2: A subsequent outage at 11:05 AM, lasting 25 minutes, continued to limit access to the service.
• Incident 3: Another outage was reported at 12:15 PM, persisting for 30 minutes. Updates confirmed persistent issues during this period, affecting many users.
• Incident 4: An additional outage occurred at 1:05 PM, lasting for 20 minutes. This heightened user frustration as multiple outages compounded within a few hours.
• Incident 5: Finally, at 2:00 PM, a further outage of 25 minutes was recorded, emphasizing a concerning trend for the provider, which totaled 2 hours and 30 minutes of downtime across the day.

Castbox

On May 2, Castbox reported an outage that began at 10:45 AM, persisting for 40 minutes. Users faced difficulty accessing the platform, with multiple updates issued to assure customers of the service restoration.

Other Providers

Several other providers faced short outages:

• Kamatera: An outage lasting 20 minutes began at 11:30 AM, swiftly resolved.
• China Unicom: Encountered a 20-minute outage starting at 12:00 PM.
• SimpliSafe: Experienced a 25-minute outage that commenced at 2:15 PM.
• sourcehut: Faced a 35-minute outage starting at 2:30 PM, creating disruption during critical hours.
• TigerGraph: An outage lasted 25 minutes from 3:45 PM.

In addition to the outages, both HomeLight and Alpine.js reported degraded performance, affecting user access and service reliability for 30 and 21 minutes, respectively.

Availability Score Summary

The following availability scores, compiled over a 24-hour window, highlight the challenges faced by impacted providers:

Community Outage Reports

In addition to the incidents, users submitted reports regarding outages with Alibaba Cloud, Microsoft Azure, and Amazon Web Services, signaling potential widespread issues.

Response Time Anomalies

No significant response time anomalies were detected for the day.

Looking Ahead

As we move into the next day, we advise monitoring the situation closely, particularly for Capcom and the affected providers. The repeated outages and degradation signal a need for ongoing transparency for customers relying on these services. Users are encouraged to remain informed through regular updates from losclouds.com as we continue to track and report on critical cloud availability metrics.