Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Aug 3, 2026

  1. New RelicIssues loading Alerts and Activity page

    Between 08:13 and 9:30 UTC on August 3rd, customers in the EU and US regions may have experienced an issue when trying to load the Alerts and Issues page in the New Relic UI. The issue is now resolved, and the impacted services have returned to normal service. Please close and re-open the Alerts page to resolve the issue.

    Resolved

Aug 2, 2026

Aug 1, 2026

  1. AssemblyAIDegraded Universal-3.5 Pro streaming in us-east

    This incident affected a subset of Universal-3.5 Pro streaming sessions in the us-east region on July 31 between 20:15 and 22:15 UTC. Affected sessions connected successfully but did not process incoming audio, so no transcript was returned while the connection remained open. Other regions, other streaming models, and our asynchronous API were unaffected. We apologize for the disruption to your workflows. If you have any questions, please reach out to support@assemblyai.com.

    Resolved

  2. StripeElevated API errors

    From 12:04 to 12:26 UTC on August 1st, we saw elevated error rates and response times with the Stripe API. The issue is resolved and we will continue to monitor.

    Resolved

  3. AkamaiEdge Delivery Issues

    We can confirm that the issue was mitigated at 09:05 UTC on August 1, 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/0D5a700001LizHpCAJ 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

  4. Liquid WebVMware MT Service Degradation

    Service has been restored at this time, and the affected VMware MT-hosted services are operating normally. Thank you for your patience and understanding while our teams worked to resolve this issue.

    Resolved

  5. StripeElevated API errors

    From 23:55 July 31st - 00:17 August 1st UTC, we saw elevated error rates and response times with the API. We are now seeing recovery and will continue monitoring.

    Resolved

Jul 31, 2026

  1. Box[Medium] Issues with Search service, Box Sign Templates and Metadata queries

    We recently addressed an issue that affected Box Search and related Query functionality, including the Public APIs and Box Apps features that rely on them. We would like to take the opportunity to explain what happened and the steps we have taken to prevent it from happening again. On July 7, 2026 between 06:22 AM and 08:53 AM PT, some customers may have experienced elevated latencies and intermittent errors when using the Box Search and Query functionality. Public APIs for these features, Box Apps, Web App Search, and other functionalities that depends on Search and Query APIs were also impacted. This incident was caused by a sudden surge in indexing traffic that overwhelmed services in one of our subsystems, before they could be scaled up or rate limiting could kick in. We were able to remediate the issue by isolating the offending traffic and allowing the surge of indexing work to finish processing and drain. Regular traffic routing was restored once the affected infrastructure was healthy again. # **Analysis** This incident revealed an opportunity to improve how we protect our search indexing subsystem from sudden~~,~~ and concentrated surges of load. While our stateless services can quickly autoscale horizontally, our stateful systems cannot be scaled as quickly to handle sudden surges in load. We’ve historically focused on query traffic driven load and over-provisioned to handle any increases in internally generated indexing load. This incident revealed that sudden and large indexing surges can impact stability more than we anticipated. Our safeguards did not sufficiently slow or throttle a large burst of re-indexing traffic, and a temporary configuration change in place at the time of this incident caused files to be re-indexed in full even when only non-content attributes had changed, amplifying the load. # **Corrective Actions** Box has initiated the following corrective actions: * Add per source rate limiting to the indexing pipeline so a large burst of work cannot overwhelm the subsystem. * Optimize indexing load, so files are only re-indexed when their content has actually changed. * Set safer limits on how much work the pipeline will accept at once. * Improve monitoring and alerting to detect unusual spikes in processing earlier and respond before customers are impacted. ‌ We are continuously working to improve Box and want to make sure we are delivering the best product and user experience we can. We hope this provides clarity on what occurred and the steps we are taking. We would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team

    Resolved

Older incidents