Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Nov 13, 2026

  1. Vonage APIIssues Impacting WhatsApp API

    Vonage services have been fully restored following today's service interruption affecting inbound WhatsApp messages and webhooks, which began at 2026-11-13 18:31:00 UTC. Full resolution has been confirmed effective 2026-11-13 22:00:00 UTC. Please note inbound messages sent and callbacks not received during the incident are lost. Impacted customers will receive a formal RFO. 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.

    Resolved

  2. Claude / AnthropicElevated errors affecting the Microsoft 365 connector

    This incident has been resolved. From 08:03 PT / 16:03 UTC on November 12 to 08:40 PT / 16:40 UTC on November 13, mail, calendar and search tools in the Microsoft 365 connector and Claude for Outlook returned errors for many requests because of a Microsoft 365 service incident. Microsoft is still completing its recovery, so you may see occasional errors or delays.

    Resolved

  3. CalendlyCalendar syncing and connection issues

    This incident is resolved. Our third-party calendar provider has reported general recovery, and calendar syncing, availability, and connections are working normally again. All calendar updates that were delayed during the incident have been processed. We're sorry for the disruption and thank you for your patience. If you still see a problem with your calendar, please contact our support team.

    Resolved

  4. OpenCodeSlow responses

    Responses took longer than usual to start. Go: muse-spark-1.3-contributor experienced slower responses.

    Resolved

  5. BrazeEmail Delivery delays to Microsoft inboxes

    We are considering this incident resolved. Braze has observed continued stability and lower latency across email sends for Microsoft-hosted inboxes over the last few hours.

    Resolved

  6. UpstashDegraded performance on Upstash Box

    The high load on Upstash Box has been mitigated. New box creation and remote executions are working normally again. The incident lasted from 18:17 to 19:35 UTC. We’re sorry for the disruption and will keep monitoring the system.

    Resolved

  7. ResendMicrosoft 365 Incident

    Email delivery to Microsoft-hosted addresses has returned to normal, and we’ve delivered emails that were in a “Delivery Delayed” status after retrying them. Microsoft is still recovering, so a small number of messages may take a little longer to arrive. As always, we’ll continue monitoring delivery to Microsoft.

    Resolved

  8. DaytonaOutage

    Resolved – API and sandbox access restored This incident is resolved. API response times and error rates have been back to normal since 19:13 UTC, and all operations, including creating, starting and connecting to sandboxes, are working as expected. The disruption was caused by a sharp increase in API request volume that overloaded our caching layer; we have increased its capacity and reduced the load our services place on it to prevent a repeat. If you are still seeing errors, please retry the request and contact support if the problem persists. We apologise for the disruption.

    Resolved

  9. AkamaiEmail Systems Widespread Outage

    We can confirm that the issue was mitigated at 18:44 UTC on November 13, 2026 and the service has resumed normal operation. Customers and partners can view additional details about the incident by logging in to: https://community.akamai.com/customers/s/feed/0D5a700001esRIKCA2 or reaching out to Akamai Support. 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 a recurrence of this issue.

    Resolved

  10. MailgunDelivery Delays for Microsoft Mailbox Providers

    Delivery rates to Microsoft mailbox providers have returned to normal levels. Some messages may have expired with the status code 602 and a message of “Too old”. Those messages were not delivered and will need to be retried.

    Resolved

  11. GitHubIncident with Pull Requests

    This incident has been resolved. Thank you for your patience and understanding as we addressed this issue. A detailed root cause analysis will be shared as soon as it is available.

    Resolved

  12. OpenCodeSlow responses

    Responses took longer than usual to start. Pay-as-you-go: glm-5.3-flash experienced slower responses.

    Resolved

  13. HubSpotHubSpot is experiencing issues

    Outlook inboxes & calendar are now fully operational following an issue with Microsoft 365. HubSpot conducts a thorough review after every incident to understand how we can respond better in future. 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

  14. OpenCodeSlow responses

    Responses took longer than usual to start. Go: mimo-v2.6-flash experienced slower responses.

    Resolved

Older incidents