Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Apr 22, 2026

  1. Intercom - AUFin is experiencing issues

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

  2. Intercom - EUFin is experiencing issues

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

  3. Intercom - USFin is experiencing issues

    This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@intercom.io: mailto:team@intercom.io if you have any further questions or if you’re still seeing any unexpected behaviour

    Resolved

  4. ZapierChatbot

    The issue affecting chatbot users has been resolved. Chat completion features are now functioning normally, and users should no longer encounter error messages when interacting with chatbots.

    Resolved

Apr 21, 2026

  1. Help ScoutAI Feature Issue

    Thanks for your patience today folks. This issue has been resolved an all AI features should be functioning normally again. Apologies for the disruption!

    Resolved

  2. MintlifyUpstream security event - Vercel

    The Mintlify team has confirmed that no suspicious or unexpected actions were taken against any Mintlify services or infrastructure that would indicate Mintlify was affected by Vercel's ongoing incident, and have taken steps to ensure no compromise could have occurred directly on Mintlify's own infrastructure. Additionally, as stated by Vercel and their security partners, no supply chain attack has been detected: https://vercel.com/kb/bulletin/vercel-april-2026-security-incident As such, the Mintlify team is closing this status page as resolved, but will continue to monitor the ongoing situation, and are available via our normal support channels to answer any questions.

    Resolved

  3. HubSpotSome automation and workflow actions are delayed

    Between 08:57 AM EST and 3:34 PM EST some customers in North America experienced issues with workflow and automation delays. This was caused by an issue processing a small subset of actions causing a backlog in the processing. As of 3:34 PM EST, our systems are working properly and the incident has been fully resolved. We are continuing to monitor for further impact. 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

  4. DescriptUnderlord is down for users

    This issue is now resolved and functionality has been restored. In the event that errors persist, please try refreshing the web editor/desktop app.

    Resolved

  5. LovableCustom domains stuck on setting up

    The issue causing custom domains to get stuck on "Setting up" has been resolved. All affected domains should now automatically become live. If yours is still stuck, try removing and re-adding it to your project.

    Resolved

  6. GitHubIncident with Codespaces

    On April 16, 2026 between 09:30 UTC and 17:15 UTC, users experienced failures when attempting to connect to GitHub Codespaces via the VS Code editor. During this time, approximately 40% of codespace start operations failed. Users connecting via SSH were not impacted. <br /><br />The issue was caused by a failure in an upstream download service that prevented the VS Code Server from being retrieved during codespace startup. The impact was mitigated by implementing a workaround to use an alternative download path when the primary endpoint is degraded. <br /><br />We are working with the upstream dependency to address the root cause of the download service failure, and we are improving our fallback mechanisms to reduce the impact of similar upstream failures in the future.

    Resolved

  7. PaddleWebhook & Email Delivery

    The underlying issue affecting Email, Webhooks & Alerts has been resolved. The service became fully operational again, processing new webhooks and outbound emails at 12:07 BST, and all delayed webhooks and outbound emails were successfully reprocessed by 12:12 BST. Our teams will continue to monitor the services closely to ensure ongoing stability. 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

  8. GitHubDisruption with some GitHub services

    On April 17, 2026, between 14:46 UTC and 15:12 UTC, users experienced a degraded web experience on GitHub.com. During this time, approximately 1.5% of web requests resulted in errors, with some users encountering slow page loads or failed requests. The issue was caused by capacity saturation of a caching component in one of our data center regions. We mitigated the issue by redirecting traffic to an unaffected region and rolling back a recent deployment. The incident was fully resolved at 15:18 UTC. We are taking steps to provide appropriate capacity for this caching path to prevent recurrence.

    Resolved

  9. PaddleDiscount service degradation causing discount application failures

    We are pleased to confirm that this issue has been resolved, and normal service has now been fully restored. Our team will continue to monitor the situation closely over the next 24 hours to ensure ongoing stability. We sincerely apologize for any disruption this may have caused. If you have any further questions or concerns, please don’t hesitate to reach out to my team at sellers@paddle.com "sellers@paddle.com": mailto:sellers@paddle.com.

    Resolved

  10. HashiCorpHashicorp GPG Key Rotation

    Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.

    Resolved

  11. SpeechmaticsInvestigating - Degraded performance

    After monitoring this incident, we can confirm it has now been resolved. We apologise for any inconvenience caused. If you are still facing issues with the service, please reach out to our support team here https://support.speechmatics.com.

    Resolved

  12. Intercom - EUFin AI Agent Degraded

    On April 21, 2026, between 09:57 UTC and 10:24 UTC, Fin was unable to reliably respond to customer conversations in the EU region. The issue has now been resolved and Fin is operating as expected. We will follow up with a full Root Cause Analysis once we understand the technical details of the issue.

    Resolved

  13. LovablePreview tab not showing

    We have identified the issue with the preview tab not showing and implemented a fix. The preview tab should now be visible in all projects. Thank you for your patience.

    Resolved

  14. E2BPartial outage in juliett cluster

    The issue affecting our services has been fully resolved, and systems are operating normally. We’ll continue to monitor closely to ensure stability. Thank you for your patience while we worked through this. E2B Team

    Resolved

  15. BuildKiteDegraded performance and increased error rates

    ## Service Impact On April 8th from 22:10 to 22:15 UTC and from 22:33 to 22:38 UTC all customers would have experienced an increase in latency browsing [buildkite.com](http://buildkite.com) and using Buildkite REST and GraphQL APIs, as well as latency creating triggered and scheduled builds of up to 12 minutes. A portion of customers also experienced increased latency and error rates for the Agent API, with the impact not being evenly distributed, causing some customers to experience a higher impact than others. Customers impacted experienced p99 latency of more than 1 second and error rates of 0.5%. Between 22:10 to 23:03 UTC a majority of customers experienced notification latency of between 5 and 33 minutes, which includes Github commit statuses and webhook delivery, as well as delays in processing incoming webhooks of up to 40 seconds. ## Incident Summary Our engineers noticed an increase in exceptions and shortly afterwards received an alert at 22:16 UTC for high CPU utilisation on a single node in a Redis cluster. Upon investigation we found a rate limiter was hot spotting on a single node within the cluster. Upon removing this limit at 22:33 UTC the impact of high Redis CPU utilization was mitigated, with CPU utilization falling to 5% for the affected node where it had been at 50% prior to the incident. Further investigations also revealed high load on a replica database was also contributing to high latency, which recovered at 22:37 UTC after a third replica was added. The rate limit which was responsible for high load on Redis had caused hot spotting on a single key because it was applied across all organizations. This limit was introduced in response to a previous incident but hadn’t been required since our work to horizontally shard our Pipelines database had distributed the load and enabled higher scalability in early 2024. ## Changes we've made These are the changes we’ve made in response to this incident: * Removed the global rate limit that was contributing to a significant proportion of load * Increased the number of read replicas for our customer information database to 3 and increased the instance size * We’ve reviewed our remaining rate limits and have confirmed that no other rate limits apply globally to all shards.

    Resolved

  16. HootsuiteIssues adding/reconnecting Bluesky accounts

    We’ve confirmed that Bluesky's error rates have stabilized, and the authentication flow in Hootsuite is now fully functional. Users should now be able to add or reconnect Bluesky accounts. Thank you for your patience while this was resolved!

    Resolved

  17. ZapierChatbots failing to load

    We have successfully resolved the chatbot availability issue that affected some of our users. Our engineering team identified and resolved the underlying authentication issue. All chatbot services are now operating normally. You should now be able to view and manage your chatbots in the dashboard and use them externally without any issues. We have monitored and verified that the service is working properly. We apologize for any disruption this may have caused. If you experience any further issues accessing your chatbots, please contact our support team: https://zapier.com/app/get-help.

    Resolved

  18. Zapieragents.zapier.com is down

    We confirm that the fix deployed has resolved the issue with Agents and Canvas, and both are functioning correctly. All Agent workflow executions that were stuck on 'In Progress' status during this incident have been replayed. If you are experiencing any issues with Zapier Agents or Canvas, please contact our support team through this link: https://zapier.com/app/get-help

    Resolved

Older incidents