Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Apr 8, 2026

  1. NeonES-1837380

    Some performance degradation may have beed observed in SA-East-1 (Sao Paolo). This issue is now resolved. No further updates will be posted.

    Resolved

  2. ZapierCopilots "Ask" mode is not working correctly

    Copilot "Ask" mode is up and running again and and can be utilized for all accounts. Earlier today the "Ask" mode was malfunctioning, causing repeated prompts, duplicate messages, and eventual crashes when users attempted to build Zaps. If you experience ongoing issues, contact Support by clicking above or go to: https://zapier.com/app/get-help Thank you for your patience.

    Resolved

  3. GitLabDegraded GitLab Duo PerformanceDegraded Performance

    Duo performance has returned to normal so we are resolving this incident. If you're still experiencing Duo performance problems, please open a ticket with support. More information can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21726

    Resolved

  4. ZapierErrors related to Custom Actions and Code by Zapier steps

    We've identified and resolved the soft timeout limit errors that were impacting Code by Zapier and Custom Action steps. This issue was affecting the execution and processing of these steps across multiple Zaps. All affected runs have been automatically replayed. If you experienced any issues or need additional support, please feel free to reach out at https://zapier.com/app/get-help

    Resolved

  5. GitHubDisruption with some GitHub services

    Between 01:36 and 08:11 UTC on Thursday March 12, GitHub.com experienced elevated error rates across Git operations, web requests, and related services. During a planned infrastructure upgrade, a configuration issue caused newly provisioned Kubernetes nodes to run an incompatible version of etcd, which disrupted cluster consensus across several production clusters. This led to intermittent 5XX errors on git push, git clone, and page loads. Deployments were paused for the duration of the incident.<br /><br />Once the incompatible nodes were identified, they were removed and cluster consensus was restored. A validation deploy confirmed all systems were healthy before normal operations resumed.<br /><br />To prevent recurrence, we are adding programmatic enforcement of version compatibility during node replacements, implementing monitoring to detect split-brain conditions earlier, and updating our recovery tooling to reduce restoration time.

    Resolved

  6. PlivoPHLO: Inbound call failures — sub-account numbers on main account PHLO apps

    Dear Valued Customer, We observed some inbound calls to PHLO applications were not being processed successfully. This affected a specific configuration where a phone number rented to a sub-account was attached to a PHLO application owned by the parent account. A recent deployment introduced a change in the request authentication flow that did not account for this configuration. The issue has been identified and fixed. Customers using phone numbers and PHLOs directly under their main account were not impacted. If you have any questions or need further assistance, please don't hesitate to contact Plivo Support through our Support Portal(https://support.plivo.com/hc/en-us).

    Resolved

  7. GitLabGitLab.com Service DegradationDegraded Performance

    Performance has returned to normal and users should no longer be experiencing degraded performance. This incident is resolved, but if you still have trouble, please open a support ticket. More details can be found here: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21732

    Resolved

  8. HubSpot"HubSpot Error: Unable to Create New Companies Due to Domain Entry Issue"

    Between 10:55 AM (UTC -04:00) and 11:28 PM (UTC -04:00), some customers in all affected regions experienced issues with company record creation. This was caused by bad deploy which has been rolled back. As of 11:28 PM (UTC -04:00), company record creation is working properly and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.

    Resolved

  9. Webflow[RESOLVED] Reports of issues accessing Webflow

    Between 14:19 and 14:43 UTC, some customers experienced issues accessing Webflow. This has now been resolved, and services are operating normally. We appreciate your patience while we worked to restore service.

    Resolved

  10. Webflow[RESOLVED] Reports of CSS not loading for a very small number of hosted sites

    A small number of hosted sites experienced an issue that affected how styles were published, which may have caused pages to appear without styling. We've identified and fixed this issue and all affected sites should be working as previously expected. We are further investigating to see if any additional action is needed.

    Resolved

  11. DevinSession crashes

    Cognition detected signifiant numbers of crashing sessions and pushed a fix within 20 min. Sessions that were active during the impacted period will likely to crash, but resume successfully if woken.

    Resolved

Apr 7, 2026

  1. RenderUnable to view workflows in the Dashboard

    Between 18:04 and 19:10 UTC, workflows were unable to be viewed in the Dashboard. All workflows continued to run and were otherwise operational. This issue has been resolved.

    Resolved

  2. GitHubDegraded performance in merge queue

    On February 17, 2026, between 17:07 UTC and 19:06 UTC, some customers experienced intermittent authentication failures affecting GitHub Actions, parts of Git operations, and other authentication-dependent requests. On average, the Actions error rate was approximately 0.6% of affected API requests. Git operations ssh read error rate was approximately 0.29%, while ssh write and http operations were not impacted. During the incident, a subset of requests failed due to token verification lookups intermittently failing, leading to 401 errors and degraded reliability for impacted workflows.<br /><br />The issue was caused by elevated replication lag in the token verification database cluster. In the days leading up to the incident, the token store’s write volume grew enough to exceed the cluster’s available capacity. Under peak load, older replica hosts were unable to keep up, replica lag increased, and some token lookups became inconsistent, resulting in intermittent authentication failures.<br /><br />We mitigated the incident by adjusting the database replica topology to route reads away from lagging replicas and by adding/bringing additional replica capacity online. Service health improved progressively after the change, with GitHub Actions recovering by ~19:00 UTC and the incident resolved at 19:06 UTC.<br /><br />We are working to prevent recurrence by improving the resilience and scalability of our underlying token verification data stores to better handle continued growth.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

    Resolved

  3. GitHubDisruption with some GitHub services

    On March 19, 2026 between 16:10 UTC and 00:05 UTC (March 20), Git operations (clone, fetch, push) from the US west coast experienced elevated latency and degraded throughput. Users reported clone speeds dropping from typical speeds to under 1 MiB/s in extreme cases. The root cause was network transport link saturation at our Seattle edge site, where a fiber cut affecting our backbone transport resulted in saturation and packet loss. We had a planned scale-up in progress for the site that was accelerated to resolve the backbone capacity pressure. We also brought online additional edge capacity in a cloud region and redirected some users there. Current scale with the upgraded network capacity is sufficient to prevent reoccurrence, as we upgraded from 800Gbps to 3.2Tbps total capacity on this path. We will continue to monitor network health and respond to any further issues.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/xs6xtcv196g7

    Resolved

  4. GitHubCopilot Coding Agent failing to start some jobs

    Between 15:20 and 20:18 UTC on Thursday April 2, Copilot Cloud Agent entered a period of reduced performance. Due to an internal feature being developed for Copilot Code Review, the Copilot Cloud Agent infrastructure started to receive an increased number of jobs. This load eventually caused us to hit an internal rate limit, causing all work to suspend for an hour. During this hour, some new jobs would time out, while others would resume once rate limiting ended. Roughly 40% of jobs in this period were affected.<br /><br />Once the cause of this rate limiting was identified, we were able to disable the new CCR feature via a feature flag. Once the jobs that were already in the queue were able to clear, we didn't see additional instances of rate limiting afterwards.<br /><br />This was the same incident declared in https://www.githubstatus.com/incidents/d96l71t3h63k

    Resolved

  5. SquarespaceConnectivity issues

    On Tuesday, March 31st, 2026, many Squarespace websites experienced unavailability for an aggregate of 53 minutes, between 4:43 PM and 5:36 PM EDT. During this incident, we failed to serve approximately 28% of customer requests. Site visitors saw slow loads or “Service Unavailable” errors impacting site loading, login, site editing, Campaigns, Domains, and our Commerce platform. At 4:43 PM EDT we performed a network configuration change in one of our points of presence \(PoP\). This change impacted critical networking equipment within that region. Our teams were notified immediately via automated alerts, internal reports, and additional customer reports. At 4:48 PM EDT our system automatically routed traffic off of this PoP. This action should have contained the impact. However, another region was already offline due to planned maintenance. As a result, the majority of our traffic was ultimately routed to a single PoP. In aggregate, this increased load overwhelmed our website lookup infrastructure in this region, severely impacting visitor requests. At 5:08 PM EDT, our teams resolved the original network configuration issue. We continued to see customer impact, so at 5:20 PM EDT we cleared the website lookup cache in the active region. This exacerbated the issue due to an additional misconfiguration within the lookup infrastructure.  At 5:35 PM EDT we successfully routed traffic back onto the original PoP, which had fully recovered. By 5:36 PM EDT our systems were serving all customer requests normally. We deeply apologize for this incident. Ensuring Squarespace sites remain up and available is of the utmost importance to us. Our team has prioritized improvements to the mitigation of similar issues and scaling our edge capacity as necessary. Thank you for your patience.

    Resolved

  6. RollbarIncreased processing pipeline latency

    This incident was resolved. Rollbar processing pipeline latency (measured at p99) was elevated above our 30-second p99 SLO today during the following windows: 02:02AM - 02:35AM PDT: 30s - 7.0 minutes latency 06:02AM - 07:03AM PDT: 30s - 3.9 minutes latency 08:00AM - 09:02AM PDT: 30s - 37.2 minutes latency 09:02AM - 09:52AM PDT: 30s - 23.1 minutes latency p50 stayed at SLO (~5s) during the entire time period, and no data was lost. The initial cause analysis is a particular traffic pattern. We're investigating the root cause to ensure the system is resilient to this traffic pattern going forward.

    Resolved

  7. HubSpotHigh ingestion latency for UnifiedEvents

    Between 10:00 AM (UTC -04:00) and 12:45 PM (UTC -04:00), some customers in North America experienced delays with event processing. This was caused by a server impairment. As of 12:45 PM (UTC -04:00), event processing is restored and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.

    Resolved

Older incidents