Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jun 19, 2026

  1. LinodeService Issue: Longview

    Starting around 23:15 UTC on June 15, 2026, some customers were unable to access the Longview graph dashboard. The investigation revealed that Linodes were unable to reach the Longview endpoint and were failing to report data. The impact was limited to reading the existing reporting data only and there was no permanent reporting data loss due to this issue. To mitigate the impact, we manually rebooted identified VM boxes to take effect and resolve Gateway errors. The impact was mitigated at 9:00 UTC on June 16, 2026, following this action. Post-mitigation, all expected data is available in the Longview graph dashboard. We will continue to investigate the root cause and will take appropriate preventive actions. 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 recurrence. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing, and any information herein is subject to change.

    Resolved

Jun 18, 2026

  1. ZapierDegraded performance for Zapier Agents

    Our Engineering team identified and resolved the issue causing degraded performance for Agents. Due to the nature of the issue, we're not able to replay Agent executions during the following incident windows 2026-06-18, between 5:47–7:15PM UTC 2026-06-18, between 8:32 PM–10:08 PM UTC Affected users have been notified via email The incident has been resolved, and Agents is now operating as expected.

    Resolved

  2. DescriptProjects reverting to earlier revisions after reopening

    The underlying cause of this issue has been resolved. Affected projects will not automatically restore to the correct version, but it is possible to manually restore the edits using the following steps: • In the Version History, look for an entry highlighted in yellow or red (around the failed merge) with a "Fix" button • Click "Fix" and use the Compare Changes option to open the ‘lost’ version in another tab • Copy/paste the missing content back into the current version If the highlighted entry does not contain the lost edits, work backward several versions to see if they appear, then follow the same steps to restore them

    Resolved

  3. HoneycombEnhance Issues

    Beginning June 17th, enhance-related requests were failing to complete. We've since identified and deployed a fix, and enhance is now fully operational. Thank you for your patience.

    Resolved

  4. GitHubMultiple services have elevated errors and endpoint failures when checking feature flags

    Between 17:38 UTC and 18:22 UTC on June 15, 2026, approximately 83% of requests to the analytics endpoint serving the /chronicle feature failed.  The cause was an internal feature-flag service that encountered a transient error and failed to recover, causing feature flag checks to fail. The analytics endpoint was gated behind one of these flags, resulting in requests being rejected. We restored service health by removing the feature flag gating the analytics endpoint and deploying that change. To avoid recurrence of similar incidents, we have changed the feature-flag client so that errors that are not known to be permanent are retried, and we are improving alerting and startup behavior so this class of failure is detected and recovered from faster.

    Resolved

  5. ZapierDelayed processing for webhook-based triggers

    This incident has been resolved. Earlier today, webhook-based triggers experienced processing delays when an unusually high volume of traffic from a third-party integration overwhelmed our shared trigger-processing system. As a result, trigger events across a range of apps were processed more slowly than usual, with delays peaking at around five minutes. We increased our processing capacity to clear the backlog, and the third-party integration also applied mitigations on their end to reduce the excess traffic. Trigger processing has returned to normal and our systems are fully operational. No trigger data was lost during the incident — affected events were delayed rather than dropped, and all delayed events have now been processed. If you have any questions, or are running into any other issues, please reach out to our support team: https://zapier.com/app/get-help Thanks again for your patience while we were working on resolving that.

    Resolved

  6. GitLabElevated errors in background job processingDegraded Performance

    A recent code change was rolled back and the error rates have subsided since it was merged. Our team has been monitoring and performance has returned to expected levels. This incident is now resolved. https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22335

    Resolved

  7. GitHubAuthentication issues related to API requests

    Between 15:05 UTC and 16:25 UTC, GitHub API services experienced degraded availability due to sporadic authentication failures affecting approximately 9% of requests. Customers experienced intermittent "logged out" behavior as erroneous 401 responses triggered repeated authentication flows in app integrations. Affected requests also experienced approximately 800ms of additional latency. <br /><br />A memcached proxy service rollout to our internal API infrastructure caused our authentication service to pick up an incorrect memcached host configuration, leading to intermittent authentication lookup failures. We mitigated the incident by deploying a configuration change to memcached to use the correct host. <br /><br />To prevent similar issues in the future, we plan to migrate our authentication system to the new memcached infrastructure to improve resilience and strengthen overall reliability posture.

    Resolved

  8. PaddlePartial Checkout Outage

    The issue affecting checkouts has been resolved. The third-party provider has restored their services, and we have removed the temporary mitigations. All systems are now operating normally, and checkouts are processing as expected. We apologize for any disruption this may have caused. If you have any questions or concerns, please contact us at sellers@paddle.com "sellers@paddle.com": mailto:sellers@paddle.com.

    Resolved

  9. Help ScoutGlobal Search Slowness

    This issue has been resolved. Global search and tag management are performing normally again. We're sorry for the disruption this caused. If you're still experiencing issues, please email help@helpscout.com, and we'd be happy to assist. Again, thank you for your patience while we got to the bottom of this.

    Resolved

Older incidents