Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Feb 6, 2026

  1. Lightning AIWebsite down

    We experienced an outage impacting access to lightning.ai between 2:00pm and 2:06pm Pacific. The situation is now resolved.

    Resolved

  2. CloudsmithService Degradation

    We have confirmed that services have continued to operate normally after the earlier mitigations were implemented.

    Resolved

  3. HeyGenVoice cache degradation

    We have identified the problem and put in a correction. Service should be behaving as usual. The cache was in a bad state and some speech audio generations would have been corrupted. This issue began with a deployment on our side at 3am PST. So any videos between then and 1130am PST might have been impacted

    Resolved

  4. BunnyPullzone Creation Failures

    Our API team identified root cause and performed a deployment change on our network to resolve the issue.

    Resolved

  5. TrueLayerPayouts Degraded Performance

    Normal service has been restored. EU Payouts should now be reaching their terminal status normally. Impact start time: 06/02/2026, 09:04 UTC Impact end time: 06/02/2026, 10:15 UTC Client actions: None

    Resolved

  6. GhostTraffic Analytics Delay

    This incident is now resolved. Analytics are now displaying new events as expected and the backlog has cleared. If you experience any missing events or traffic please reach out to Ghost(Pro)'s Support Team.

    Resolved

  7. FigmaFigma Make Publishing Disruption

    From 7:05 PM UTC on Feb 5 to 12:00 AM UTC on Feb 6, some users experienced issues when prompting in Figma Make or Sites with code components. This issue has been resolved.

    Resolved

Feb 5, 2026

  1. AsanaAPI monitoring

    Our engineers have rolled back recent changes to our primary monitoring systems, and our API and mobile systems are fully operational.

    Resolved

  2. RenderDegraded deploys in Ohio and Virginia

    We implemented updates to builds and deploys to improve handling of slow updates. As a result of these changes, build and deploy performance has recovered.

    Resolved

  3. HubSpotHelp Desk and Conversations Inbox channels not receiving ticket

    Between 03:25 PM (UTC -05:00) and 03:59 PM (UTC -05:00), many customers in all affected regions experienced issues with helpdesk, inbox. This was caused by a database impairment. As of 03:59 PM (UTC -05:00), our helpdesk, inbox are 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

  4. MintlifyEditor displaying parsing errors for some users

    This issue has been fully resolved. The root cause was identified and a fix has been deployed. All editor functionality has been restored. If you are still experiencing any issues, please contact support.

    Resolved

  5. AssemblyAIAsync + LLM gateway APIs returning 5xx

    **Summary: January 29 Outage** On January 29, our Async Transcription and LLM Gateway went down for 25 minutes, followed by two hours of degraded performance. Here's what happened. Our traffic has been steadily increasing and we received an influx of batch transcription jobs that were higher than usual. Autoscaling did what it should—spun up workers. We ran out of spot instances, fell back to on-demand, then hit AWS's Elastic Network Interface limit. Every ECS task needs an ENI. With no ENIs available, our authentication service couldn't rotate its tasks. It scaled to zero. Everything stopped. When we tried to recover, a Lambda function meant to help with failures was hammering the AWS API with describe calls, rate-limiting the very operations we needed to bring things back. A tool built for recovery was blocking recovery. **What actually went wrong:** We didn't monitor ENI utilization and our authentication service shared resources with batch workers. Traffic spike in one starved the other. **What we're doing:** Short-term: ENI alerts, isolate auth on dedicated capacity, fix the Lambda. Medium-term: Full multi-region for everything. This was preventable. We had the warning signs and didn't connect them. We're sorry, and we're fixing it.

    Resolved

Older incidents