Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Nov 3, 2026

  1. GitLabIssues Running PipelinesDegraded Performance

    This incident is now resolved, as we didn’t see the issue return during our monitoring period and CI/CD pipelines are running normally. We’re continuing to investigate the root cause internally with details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/23401.

    Resolved

  2. CloudflareMissing Logs and Traces in Cloudflare Observability Platform

    Between October 5 at 1:00 PM UTC and October 23 at 9:00 PM UTC, some customers may have experienced missing log events, incomplete traces, or inconsistent issue counts due to ingestion pipeline capacity limits. Traffic and Workers were not affected, and customers will not be billed for dropped events. Capacity has since been increased, and service has returned to normal.

    Resolved

  3. TelnyxMessaging Latency

    We believe the issue to be resolved now. We are actively working on ensuring that any webhooks which were delayed as a result of this incident get sent out to the appropriate webhook endpoints. We apologise for any inconvenience caused.

    Resolved

  4. AkamaiProperty Manager Property Activation Errors

    We became aware of an issue with Property Manager related to activating properties with errors indicating "cloudlet policy not found or not valid" blocking some property activations. The issue lasted between approximately 15:30 UTC on November 3, 2026 and 17:15 UTC on November 3, 2026. We can confirm that the issue is now resolved, 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/0D5a700001cwVdYCAU 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

  5. GitHubIncident with Actions, Pages, and Webhooks

    On October 30, 2026, from 17:50 to 18:32 UTC, Actions, Pages, and Webhooks experienced degraded performance. Actions workflow processing, Pages deployments, and webhook deliveries were delayed, and code search and live updates returned errors. Some Actions queues took additional time to drain after mitigation, and the incident was resolved at 19:23 UTC. <br /><br />The impact was triggered by maintenance on a cloud network gateway connecting an Actions service in the GitHub data center to Redis clusters in the Central US Azure region. The service's Redis client retried aggressively and redialed those connections. That produced a connection storm that saturated the gateway, with about 90% of connection attempts failing. Other services sharing the same network path were degraded as well. <br /><br />We mitigated the incident by removing the affected resources from rotation, which ended the connection storm and allowed the gateway to recover. We have already reduced the number of connection retries in the impacted service and are further improving retry behavior with jittered backoff, shorter connect timeouts, and retry budgets. We are also working with our infrastructure team to make GitHub more resilient to gateway maintenance.

    Resolved

  6. SendGridVoice Call Audio Delays When Using Media Streams

    We have observed a recovery in voice calls when using Media Streams and are monitoring service stability. We will provide another update in 16 hours or as soon as more information becomes available.

    No longer active

  7. TwilioVoice Call Audio Delays When Using Media Streams

    We have observed a recovery in voice calls when using Media Streams and are monitoring service stability. We will provide another update in 16 hours or as soon as more information becomes available.

    No longer active

  8. EtsySite Issues

    This incident has been resolved. If you are still experiencing an issue, please let us know in our Etsy Forums (https://community.etsy.com/t5/Technical-Issues/bd-p/bugs).

    Resolved

  9. SnowflakeINC20000294

    Current status: We've monitored the environment and confirmed that service has been restored. If you experience additional issues or have questions, please open a support case via Snowflake Community or the Support page in Snowsight. Customer experience: Customers hosted in the specified region may have been unable to access or use multiple Snowflake services and features. Affected users may have experienced errors or failures when connecting to Snowsight, managing data, loading data, or using applications. Incident start time: 06:01 UTC October 20, 2026 Incident end time: 14:00 UTC October 20, 2026 Preliminary root cause: A power event at our third-party cloud platform provider made one of the availability zones in the specified region unavailable. Snowflake infrastructure running in that zone, including components that support Snowsight, became unreachable, and requests that depended on it failed until workloads moved to the remaining availability zones. To limit further impact, we stopped placing new workloads in the affected zone and paused routine software updates in the region until the provider restored the zone. A root cause analysis (RCA) will be conducted and a summary will be made available within 10 business days.

    Resolved

  10. GrafanaGrafana Cloud: k6 timeouts

    We had a transient database slowdown causing a limited number of customers' k6 cloud runs to time out or abort in a window of a few minutes after Nov 2, 15:00 UTC. We are investigating the cause.

    Resolved

  11. OVHcloud - Public Cloud[GRA11][Network] - Network API incident notification

    We are pleased to inform you that the incident affecting our Network offering has been resolved. <b>Start time :</b> 03/11/2026 09:13 UTC <b>End time :</b> 03/11/2026 15:31 UTC <b>Root Cause :</b> This incident was caused by a software issue. We apologize for any inconvenience caused and appreciate your understanding.

    Resolved

  12. PostHogWorkflows Email Metric Ingestion Outage

    Between 10:58-11:36 GMT we had an incident that dropped email engagement events for emails sent from within workflows and broadcasts affecting downstream triggered automations for a handful of customers. At no point were emails lost. Additionally during this time period email metrics are showing inflated numbers. All affected customers will be contacted by us about their affected workflows and impact.

    Resolved

  13. GrafanaIncreased query latency for Logs in GCP US Central (prod-us-central-0)

    This incident has been resolved. Some Logs queries in GCP US Central (prod-us-central-0) were slower than usual between 12:08 and 12:34 UTC. Some Metrics alert and recording rule evaluations in the same region were also delayed between 12:11 and 12:44 UTC. Both issues have been mitigated.

    Resolved

  14. DaytonaDegraded performance: API and sandbox operations

    Between 13:05 and 14:40 UTC, the Daytona API had elevated latency and intermittent errors. Some sandbox create, start and stop operations were slow or failed during this window. The cause was a database overload brought on by an unusually high volume of repeated requests, which kept routine database maintenance from completing. We restored the database and confirmed that performance is back to normal. We're adding safeguards so a single source of traffic can't cause this again. If any of your sandboxes are still in an unexpected state, retry the operation or contact support.

    Resolved

  15. CoinbaseDelayed Sends and Receives - Sonic Network

    Some users may experience delayed sends and receives on the Sonic network. Buys, Sells, and Fiat withdrawals/deposits remain unaffected. We're working on this issue and will provide updates as soon as possible. Your funds are safe.

    Notice

  16. LiveKitDisconnections and failed connections in multiple regions

    **Summary** On October 31, 2026, between 07:10 and 07:43 UTC, an uncommon data pattern surfaced a latent software bug which caused media servers in several regions to restart repeatedly. A small percentage of participants were disconnected and the vast majority automatically reconnected. Impact was concentrated in North America. We stopped the trigger at 07:43 UTC and deployed a fix to all regions by 08:49 UTC. We apologize for the disruption this caused. **Root Cause** Applications can open their own data channel and send raw data over it, outside of LiveKit's standard data message format. Media servers forward this raw data to other participants in the room, wrapping it with the sender's identity so that receivers know who sent it. When a room spans multiple regions, the media servers hosting it also forward this data to each other. That server-to-server step sent the raw data without the sender's identity, and the receiving server assumed the identity would be present, which caused it to crash. This gap in our server-to-server protocol had been present for some time and was not introduced by a recent deployment. Starting at 07:10 UTC, one application sent raw data over its own data channel in a room that spanned multiple regions. Every server that received the forwarded message crashed at the same time, while the server the sender was connected to kept running and kept sending. Participants on the crashed servers automatically reconnected to other servers. Those servers then began hosting the room, received the next message, and crashed as well. This cycle repeated until we stopped the trigger at 07:43 UTC. In total, media servers in 12 of our data centers restarted, some of them up to 10 times. **Timeline \(UTC\)** 2026-10-31 07:10 - An application begins sending raw data over its own data channel in a multi-region room. Media servers in US East and Canada restart within seconds. 07:13 - Our monitoring detects the restarts and an incident is opened automatically. 07:10 to 07:43 - Media servers in 12 data centers restart repeatedly as participants reconnect to new servers. 07:43 - We block the traffic triggering the bug. There are no further restarts after this point, and customer impact ends. 07:46 - A fix for the bug is ready. 08:04 - The fix begins rolling out, starting with a small set of regions. 08:49 - The fix is deployed to all regions. **Scope of Impact** Realtime sessions: * Across all regions, about 1.5% were disconnected more than once within five minutes. * In US East, US Central, US West, Canada and Mexico, about 6% were disconnected more than once within five minutes. * The median time from disconnect to rejoin was about 3 seconds. Agents: * Agents were disconnected and reconnected the same way as other participants, with the same median reconnect time of about 3 seconds. An agent that reconnects keeps its conversation state, so most conversations continued after a short gap. Fewer than 1% of active agent sessions did not recover. Ingress, Egress and SIP: * Most active WHIP ingress streams were interrupted, and reconnects typically took about 40 seconds. Some WHIP ingress update and delete requests also failed. * About 5% of active egress sessions were disconnected. Most reconnected within a few seconds. * About 1% of SIP participants were disconnected, and half of them rejoined in under a second. Some SIP call transfers also failed. APIs: * About 1.3% of Room Service API requests failed during the window. ListParticipants and GetParticipant were the most affected. How to tell if you were affected: participants in affected sessions saw a reconnecting state, or a brief loss of audio and video. In session analytics, an affected participant appears to leave and rejoin the same room with the same identity between 07:10 and 07:43 UTC. **Detection and Response** Our monitoring detected the server restarts about 3 minutes after they began, and an incident was opened automatically. Identifying the specific room and traffic triggering the restarts took about 30 minutes. Once we found it, we blocked the trigger at 07:43 UTC and the restarts stopped immediately. We deployed a fix to all regions by 08:49 UTC. We did not post to our status page while the incident was in progress, and published a notice only after it was resolved. Our original post mistakenly sent notifications as we initially over-estimated the scope of impact. **Mitigations and Follow-ups** * We fixed the bug. Media servers now handle forwarded data that arrives without the sender's identity instead of crashing. This fix was deployed to all regions by 08:49 UTC. * Raw data forwarded between media servers now includes the sender's identity, so receiving servers always know who sent it. We appreciate your understanding and are committed to continuously improving our platform's reliability. If you have any questions, please reach out to our support team.

    Resolved

  17. GitHubIncident with API, Git, and Copilot requests

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Resolved

  18. GrafanaElevated Request Errors for Grafana Across Multiple Regions

    Between approximately 12:10 UTC and 13:22 UTC on 3 November (about 1 hour 12 minutes), Grafana across multiple Grafana Cloud regions experienced elevated request errors, causing slow-loading or failing dashboards and Explore queries. The issue has been resolved and service has been fully restored.

    Resolved

  19. SnykIssue Resolving Entitlements

    Services have remained stable throughout the monitoring period. The Snyk Incident Response has been stood down.

    Resolved

  20. SendGridSMS Delivery Delays from Twilio to Entel Bolivia

    We have observed a recovery in SMS delivery from Twilio to Entel network subscribers in Bolivia and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

    No longer active

  21. TwilioSMS Delivery Delays from Twilio to Entel Bolivia

    We have observed a recovery in SMS delivery from Twilio to Entel network subscribers in Bolivia and are monitoring service stability. We will provide another update in 4 hours or as soon as more information becomes available.

    No longer active

Older incidents