Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Sep 30, 2026

  1. Weights & BiasesAPI Degraded

    An incident with Google Cloud caused our API and site to become degraded or unavailable. We apologize for the disruption. https://status.cloud.google.com/incidents/J5ia5t9p3g9Q5Wi7r8Ev

    Resolved

  2. OVHcloud - Public Cloud[DE1/DE2][Compute - Instance] - Compute Instance Incident Notification

    We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 30/09/2026 11:00 UTC <b>End time :</b> 30/09/2026 12:37 UTC <b>Root Cause :</b> This incident was caused by this maintenance : https://network.status-ovhcloud.com/incidents/psvb5n915gr6 We apologize for any inconvenience caused and appreciate your understanding.

    Resolved

  3. Vonage APIAdvanced Machine Detection Issues

    We identified an issue affecting our Advanced Machine Detection product. The issue has been resolved, and we are continuing to monitor the service for any additional impact. Impact period Start: 11:21 UTC End: 12:24 UTC Duration: 1 hour 3 minutes We apologize for any inconvenience this may have caused. If you have any questions or require further assistance, please contact Vonage Support at https://api.support.vonage.com/hc/en-us.

    Resolved

  4. SinchDelivery Issue Guatemala - Tigo

    This incident has been resolved. Incident Start Time: 2026-09-29 23:27 UTC Incident Start Time: 2026-09-30 09:01 UTC

    Resolved

  5. AkamaiIncreased latency during upstream provider maintenance in Singapore, Hong Kong, and Japan

    We can confirm that the issue was mitigated on September 30, 2026, and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001V0be8CAB or reaching out to Akamai Support. We apologize for the impact and thank you for your patience and continued support. We are committed to making continuous improvements to make our systems better and prevent a recurrence of this issue.

    Resolved

  6. ChargebeeAPI Service Degradation

    We experienced a brief service interruption in the EU region between 09:14 UTC and 09:20 UTC that resulted in failed API requests for some merchants. Services have recovered. We apologize for any disruption this may have caused.

    Resolved

Older incidents