Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jan 28, 2026

  1. CloudsmithDelayed Policy Evaluations

    We have resolved the incident affecting policy evaluations and are now monitoring the remaining backlog for EPM decision logs. Core services are fully operational,

    Resolved

  2. ElevenLabsIssue with exports in Dubbing

    We have confirmed that our fix successfully remediated the issue, and Dub Exportation is fully functional. Previous download attempts may need to be resubmitted.

    Resolved

  3. LeverIntermittent issues impacting Lever Reporting

    Our team has completed re-processing the missing data from January 20–23. All data updates are now fully restored and functioning as expected. We appreciate your patience while we worked to resolve this issue.

    Resolved

  4. GranolaGranola database connection issues

    The issues from earlier today should be solved - this was caused by a change that placed unexpected load on our database. We've fixed this now, so Granola should be operational as usual. If you're having issues, get in touch at hey@granola.so "hey@granola.so": mailto:hey@granola.so.

    Resolved

  5. BlaxelHigh jobs failure rate

    This incident has been resolved, and service is operating normally again. Thanks for your patience.

    Resolved

  6. SupabaseDegraded Performance for Supavisor

    Between 6am and 7am UTC our Supavisor cluster experienced instability, resulting in elevated error rates and increased client reconnects. The issue has since been resolved, and the service is operating normally. We are currently reviewing preventative measures to reduce the likelihood of recurrence.

    Resolved

  7. BufferIssue Publishing Posts to TikTok

    The posting success rate for TikTok has returned to normal, and we are no longer seeing issues with channel refreshes or account connections. We have not yet received formal confirmation from TikTok; however, all systems are currently operating as expected. As a result, we are resolving the incident at this time. We appreciate your understanding and apologise for any disruption this may have caused.

    Resolved

  8. ConfluenceConfluence site unreachable for some users

    ### Summary On Jan 08, 2026 between 14:54 UTC and 16:30 UTC, Atlassian customers using Confluence Cloud product\(s\) experienced degraded service with view/edit page experiences. The event was triggered by database overload due to an unexpected large burst of traffic. The database overload was the result of a configuration change, which led to a sudden spike in database connections, which impacted a subset of customers in a single partition in the us-east region. The incident was detected within 1 minute by by automated monitoring systems and mitigated by reducing the number of web server hosts connecting to the database layer, which put Atlassian systems into a known good state. The total time to resolution was about 1 hour and 26 minutes. ### **IMPACT** The overall impact was between Jan 08, 2026, 14:54 UTC and 16:30 UTC on Confluence Cloud products. The incident caused service disruption to customers in a single partition in the us-east region impacting the ability to view and edit pages. We observed partition-wide database saturation due to an unexpected large burst of traffic. Confluence Cloud components impacted during this window were: Login, View / Edit Page, Publish Page, Add Page, Comment. ### **ROOT CAUSE** A change was introduced that caused cross-region traffic routing for customers instead of routing to the same region. Some caches processing customer data were stale, which heavily loaded the databases and caused them to restart. As a result, the users of the product above could not login, view or edit pages, and the users received HTTP 500 and 504 errors. ### **REMEDIAL ACTIONS PLAN & NEXT STEPS** We know that outages impact your productivity. While we have a number of testing and preventative processes in place, this specific issue wasn’t identified due to a specific set of factors which resulted in this condition. We are prioritizing the following improvement actions to help avoid repeating this type of incident: * Fix the routing issue that resulted in cross-regional traffic * Decrease maximum number of connections per database instance, to allow for sufficient memory capacity to handle a surge in connections Furthermore, we deploy our changes progressively \(by cloud region\) to avoid broad impact but in this case, the impact was larger than desired. To minimize the impact of breaking changes to our environments, we will implement additional preventative measures such as enabling automatic vertical scaling when database clusters are running low on memory. We apologize to customers whose services were impacted during this incident; we are taking steps to help improve the platform’s performance and availability. Thanks, Atlassian Customer Support

    Resolved

  9. InngestError publishing events with metadata to Event API

    We shipped a fix earlier today at 20:40 UTC (Jan 27) that has resolved the issue after an extended monitoring window to confirm the issue did not return. The bug itself affecting some user requests was an issue due to a large "baggage" header which was beyond the limit of what the Event API's pubsub event stream can handle. Baggage headers are used for sending extra context within a request like open telemetry or APM tracing data. Some requests contained more than 1024 bytes which caused this issue. The fix applied earlier today gracefully now gracefully handles the situation where there are large baggage headers. This issue will not surface again.

    Resolved

Jan 27, 2026

  1. NotionSide Peek Page Crashes

    This issue has been resolved. For desktop users, please restart the app + update to the latest version of Notion to see changes reflected.

    Resolved

  2. GitHubDisruption with some GitHub services

    On January 22, 2026, our authentication service experienced an issue between 14:00 UTC and 14:50 UTC, resulting in downstream disruptions for users.<br /><br />From 14:00 UTC to 14:23 UTC, authenticated API requests experienced higher-than-normal error rates, with an average of 16.9% and occasional peaks up to 22.2% resulting in HTTP 401 responses for authenticated API requests. <br /><br />From 14:00 UTC to 14:50 UTC, git operations over HTTP were impacted, with error rates averaging 3.8% and peaking at 10.8%. As a result, some users may have been unable to run git commands as expected.<br /><br />This was due to the authentication service reaching the maximum allowed number of database connections. We mitigated the incident by increasing the maximum number of database connections in the authentication service.<br /><br />We are adding additional monitoring around database connection pool usage and improving our traffic projection to reduce our time to detection and mitigation of issues like this one in the future.<br />

    Resolved

  3. GitHubDisruption with some GitHub services

    Between 2026-01-13 22:20 and 2026-01-14 00:18 UTC, GitHub Code Search experienced an increase in latency and request timeouts. This was caused by some network transit links between GitHub and Azure Express Route experiencing a small error rate that contributed to applications requests failing, increasing application latency and timeouts. The incident resulted in less than 1% of requests to fail due to timeouts.<br /><br />We mitigated the incident by disabling the links in question. Monitoring each unique network path across providers would have allowed us to mitigate this earlier. We are running root cause analysis with network providers to help us reduce time-to-discover and time-to-mitigate.

    Resolved

  4. HashiCorpapp.terraform.io unavailable

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

    Resolved

Older incidents