Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Sep 8, 2026

  1. LinodeService Issue - Cloud Manager and API

    Between approximately 10:15 and 12:18 UTC on September 7, 2026, customers could have experienced elevated error rates and 5xx response codes when using Cloud Manager or performing API calls.  The investigation revealed that the issue started due to increased API load that over-utilized our database resources which in turn led to the symptoms seen by users. To mitigate the issue, the team addressed the elevated API load issue which brought back utilization of our resources within normal ranges. Ongoing actions include monitoring platform stability, and planning enhancements to API rate limiting. 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

  2. LiveKitSome sessions incorrectly shown as active

    A subset of room sessions that ended around 4 September 09:57 UTC were not recorded with an end time. These sessions continue to appear as active in the Cloud dashboard and in session records, and no `room_ended` end time is reflected for them. This was a reporting issue only. Rooms ended normally for participants, live traffic was not affected, and there is no impact on usage or billing. The underlying cause has been identified and fixed. Affected sessions from this window may continue to display as active; they can be safely disregarded.

    Resolved

Sep 7, 2026

  1. LinodeService Issue - US-SEA (Seattle, WA)

    On August 21, 2026 starting approximately at 17:23 UTC, customers using the Seattle data center \(US-SEA\) were unable to provision new nodes or complete host jobs, whereas customers outside Seattle were unaffected.  The investigation revealed that this was due to a Linux kernel issue that was triggered on a network router due to increased network traffic at this site while a specific BIOS setting was enabled.  This caused system instability and affected job processing in the US-SEA region. To mitigate the impact, the Akamai team disabled a problematic setting and rebooted the affected system, restoring service and moving the situation to a monitoring state by 21:59 UTC on August 21, 2026. As preventive actions, Akamai will audit hardware configurations to ensure the problematic feature is explicitly disabled, and implement enhanced monitoring to detect similar issues in the future.  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

  2. Vonage APIService issue in Voice API platform

    Vonage services have been fully restored following today’s service Voice API platform, which began at 7 Sep 2026 15:04:44 UTC. Full resolution has been confirmed effective 7 Sep 2026 16:43:18 UTC. Thank you for your patience and understanding as we worked to restore services as quickly as possible. If you have any questions, please contact [api.support.vonage.com OR https://www.vonage.com/support/].

    Resolved

  3. PandaDocIncident notification

    This incident is resolved. Document processing (private and public documents) is operating normally as of 20:28 PDT. What happened: Between 17:00 and 20:28 PDT, document processing (private and public documents) was unavailable for many customers. After receiving reports, we took action, investigated, and restored normal operation. If you were affected, please reach out to our support team with your document link if you have documents that were completed between 17:00–20:28 PDT and are missing a signed PDF — our team will generate it for you internally. Please contact our Support team if you continue to experience issues: https://support.pandadoc.com/en/articles/9715061-how-to-contact-pandadoc-support

    Resolved

  4. ZapierFreshservice - Webhook delivery disruption

    Freshservice webhook triggers are now delivering to Zapier again following a fix deployed by Freshservice. We’ve confirmed incoming webhook activity has resumed and are continuing to monitor volumes. 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

Older incidents