Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Sep 23, 2026

  1. TeamViewerWestUS2 - Intermittent Login Issues

    We experienced intermittent login issues affecting customers access to the DEX Platform. Impacted users reported the following symptoms: Unable to successfully complete login to the DEX Platform. Receiving the error message: "Application cannot be served because the license has expired" after logging in. Our Site Reliability Engineering (SRE) and Cloud teams investigated the issue and implemented a resolution. Service has been fully restored, and affected users are now able to access the platform normally.

    Resolved

  2. OVHcloud - Public Cloud[EU-WEST-PAR][Containers & Orchestration] - Managed Kubernetes Service incident notification

    We had an incident on Containers & Orchestration offer which has now been resolved. Here are some supplementary details : <b>Start time :</b> 22/09/2026 17:20 UTC <b>End time :</b> 23/09/2026 09:30 UTC <b>Impacted Service(s) :</b> The Managed Kubernetes Service temporarily experienced network disruptions. <b>Customers Impact :</b> Customer experienced network issue in their cluster that made their nodes flap in NotReady state. <b>Root Cause :</b> This incident was caused by this incident : https://public-cloud.status-ovhcloud.com/incidents/pcwhfzd30hp1 We thank you for your understanding and patience throughout this incident.

    Resolved

  3. OVHcloud - Public Cloud[EU-WEST-PAR][Network] - Public network incident notification

    We would like to inform you that an incident occurred in the EU-WEST-PAR region. This incident has now been resolved. Please find the details of this incident below : <b>Start time :</b> 22/09/2026 17:20 UTC <b>End time :</b> 23/09/2026 09:30 UTC <b>Impacted Service(s) :</b> Public Cloud services hosted in the EU-WEST-PAR region, including customer networks, experienced increased latency and packet loss. <b>Customers Impact :</b> Customers experienced latency and packet drops when accessing their Public Cloud services and networks hosted in the EU-WEST-PAR region. <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.

    Resolved

  4. MakeScenario logs in UI not loading

    Scenario logs in the UI were not loading. Clicking on logs in scenario history timed out. Fetching logs via API was not impacted. All zones were affected. The issue was already fixed.

    Resolved

  5. GrafanaIRM Access Issues for a Small Group of Users

    Between 14:57 UTC on 22 September and 09:00 UTC on 23 September, a small group of users experienced unexpected access issues and undelivered pages in Grafana IRM. This has been fully resolved and all affected users should now have normal access. Thank you for your patience.

    Resolved

  6. Vonage APIVoice API Latency Issue - USE1

    Vonage services have been fully restored following the service interruption impacting your calls, which began at 2026-09-21 01:27 UTC. Full resolution has been confirmed effective 2026-09-22 18:44 UTC. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact api.support.vonage.com.

    Resolved

  7. Webflow[RESOLVED] Reports of form submission notification emails not being delivered for some customers

    This incident is now resolved. Form submission notification emails were impacted between 00:46 UTC on September 21 and 15:33 UTC on September 22. New form submissions are now triggering notification emails as expected. During this time, form submissions continued to be received and saved as expected, and webhook delivery was unaffected. Notification emails that were not delivered during the affected timeframe will not be delivered retroactively. Affected customers can review submissions from this timeframe via: - the Forms tab in Site settings - the data_forms MCP tool - the Form Submissions API endpoints We appreciate your patience while we worked with our upstream provider to resolve this issue.

    Resolved

  8. OVHcloud - Public Cloud[WAW][Storage] - Block Storage Incident Notification

    We are pleased to inform you that the incident affecting our Storage offering has been resolved. <b>Start time :</b> 23/09/2026 13:07 UTC <b>End time :</b> 23/09/2026 17:09 UTC <b>Root Cause :</b> https://network.status-ovhcloud.com/incidents/jy9dbvzlrzyw We apologize for any inconvenience caused and appreciate your understanding.

    Resolved

  9. OVHcloud - Public Cloud[WAW1][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> 23/09/2026 13:07 UTC <b>End time :</b> 23/09/2026 17:09 UTC <b>Root Cause :</b> https://network.status-ovhcloud.com/incidents/jy9dbvzlrzyw We apologize for any inconvenience caused and appreciate your understanding.

    Resolved

  10. LinodeEmerging Service Issue - Cloud Manager and API

    We haven't observed any additional issues with the Cloud Manager or API, and will now consider this incident resolved. If you continue to experience issues, please contact us at 855-454-6633 (+1-609-380-7100 Intl.), or send an email to support@linode.com for assistance.

    Resolved

  11. AmplitudeSnowflake Data Share export delivery issue

    The authentication issue affecting Snowflake Data Share delivery has been resolved. Snowflake Data Share exports are operating normally. No data loss is expected, and no customer action is needed.

    Resolved

Sep 22, 2026

  1. ReplitConnector status mismatch and removal errors

    The issue affecting existing connector connections has been resolved. Previously connected integrations should now appear again without reconnecting. If a connection still appears unavailable or you see a setup or removal error, please contact support with the affected connector and project so we can investigate.

    Resolved

  2. StripeAPI call success rate drop

    From 19:13 to 22:19 UTC, we saw elevated error rates and response times with the API. This is now resolved.

    Resolved

  3. HarnessIACM Module Registry performance degradation

    ## 1. Summary On Monday, September 15, 2026, some customers using Infrastructure as Code Management \(IaCM\) Module Registry on Prod EU1, and later Prod1, experienced timeouts and failed requests. ‌ Affected customers saw Module Registry operations hang or fail in the UI, and IaCM pipelines that look up modules or module-registry connectors during Initialize or Plan could stall and then expire. This was not a platform-wide outage. Other Harness modules were not broadly impacted. We have no report of customer data loss. Workspace plan/apply that did not need Module Registry during the failing calls continued as normal. # 2. Impact * Product area: IaCM Module Registry \(UI and API\) and IaCM pipelines that call Module Registry during Initialize or Plan. * Customer experience: timeouts and failed Initialize/Plan steps; Module Registry UI/API delays or failures. In at least one case, the Module Registry CLI continued to work while the plan path timed out. * Environments: Prod EU1, then Prod1. This was not a full multi-cluster outage. * Severity: S-2. * Data: no data loss reported. # 3. Root Cause A sudden traffic surge caused backend connections to hit capacity limits, leading to client-side timeouts. Increasing capacity and restarting the IaCM service cleared remediated the issue # 4. Remediation **Immediate:** restarted the IaCM service to release stale connections and restore Module Registry and related pipeline steps. **Capacity:** increased the backend capacity for  Module Registry database connection **Permanent:** Tune and optimize the backend for latency and resiliency so that we can absorb traffic spikes without impact. ‌ # Next Steps ‌ To prevent such issues happening again, Harness is working on ‌ _We apologize for the disruption to Module Registry and to pipelines that depend on it. Please reach out to your Harness support contact if you have any further questions about this incident._

    Resolved

  4. HarnessIACM Module Registry timeouts

    # Root Cause Analysis Report ## IaCM Module Registry Timeouts ## 1. Summary On Monday, September 15, 2026, some customers using Infrastructure as Code Management \(IaCM\) Module Registry on Prod EU1, and later Prod1, experienced timeouts and failed requests. ‌ Affected customers saw Module Registry operations hang or fail in the UI, and IaCM pipelines that look up modules or module-registry connectors during Initialize or Plan could stall and then expire. This was not a platform-wide outage. Other Harness modules were not broadly impacted. We have no report of customer data loss. Workspace plan/apply that did not need Module Registry during the failing calls continued as normal. # 2. Impact * Product area: IaCM Module Registry \(UI and API\) and IaCM pipelines that call Module Registry during Initialize or Plan. * Customer experience: timeouts and failed Initialize/Plan steps; Module Registry UI/API delays or failures. In at least one case, the Module Registry CLI continued to work while the plan path timed out. * Environments: Prod EU1, then Prod1. This was not a full multi-cluster outage. * Severity: S-2. * Data: no data loss reported. # 4. Root Cause A sudden traffic surge caused backend connections to hit capacity limits, leading to client-side timeouts. Increasing capacity and restarting the IaCM service cleared remediated the issue # 5. Remediation **Immediate:** restarted the IaCM service to release stale connections and restore Module Registry and related pipeline steps. ‌ **Capacity:** increased the backend capacity for  Module Registry database connection ‌ **Permanent:** Tune and optimize the backend for latency and resiliency so that we can absorb traffic spikes without impact. ‌ # Next Steps ‌ To prevent such issues happening again, Harness is working on ‌ _We apologize for the disruption to Module Registry and to pipelines that depend on it. Please reach out to your Harness support contact if you have any further questions about this incident._

    Resolved

Older incidents