Live outage feed

Outages and recoveries from the services you depend on.

Earlier incidents

40 incidents

Back to latest

Jun 3, 2026

  1. ReadMeReadMe Refactored Outage

    ### What Happened Beginning Tuesday, May 26, 2026, customers were experiencing slow loading and 503 errors across ReadMe-hosted docs and the admin dashboard. The outage was intermittent but recurring, with the worst periods hitting during business hours when traffic spiked. ### Root Cause An internal data backup process was generating excessive I/O on our storage layer. Under normal traffic conditions, this additional load was manageable. But when it coincided with peak customer traffic and elevated bot activity, total I/O demand exceeded system capacity, causing cascading request timeouts. The maintenance process ran on a recurring schedule, which is why the degradation followed a predictable pattern of spikes throughout each day. Separately, a surge in bot traffic to non-existent pages \(404s\) amplified the problem because those requests were not being served from cache. ### Resolution **Immediate fix:** We identified and disabled the maintenance process causing the excess I/O load. Within three hours, storage utilization returned to normal levels and remained stable. **Additional improvements shipped during the incident:** * Expanded caching across multiple layers, significantly reducing load on backend storage * Hardened 404 handling to serve error pages from cache instead of hitting the backend * Implemented rate limiting and IP-based protections against abusive bot traffic * Optimized several high-traffic API endpoints to reduce redundant backend calls * Added new monitoring and alerting for storage I/O thresholds ### Timeline May 26 - June 1, 2026 | Time | Status | Details | | --- | --- | --- | | Mon 5/26, 6:39 AM PDT | Investigating | Issue reported | | Mon 5/26, 7:26 AM PDT | Monitoring | Fix implemented, monitoring results | | Mon 5/26, 8:37 AM PDT | Resolved | Admin hub incident resolved | | Mon 5/26, 10:41 AM PDT | Investigating | Slow performance across customer hubs | | Mon 5/26, 10:49 AM PDT | Monitoring | Quick fix applied, investigating thorough fix | | Mon 5/26, 8:54 PM PDT | Resolved | Customer hub incident resolved | | Tue 5/27, 6:51 AM PDT | Investigating | Issue reported | | Tue 5/27, 7:52 AM PDT | Identified | Fix in progress | | Tue 5/27, 8:57 AM PDT | Monitoring | Slowly recovering | | Tue 5/27, 10:17 AM PDT | Update | Updated 6/3: A routine configuration update coincided with the downtime window, which led us to initially identify it as the cause. Further investigation confirmed the two were unrelated. See root cause and resolution above. | | Tue 5/27, 1:54 PM PDT | Update | Performance and loading still affected, rolling out fixes | | Tue 5/27, 3:37 PM PDT | Resolved | Incident resolved | | Wed 5/28, 6:40 AM PDT | Investigating | Issue reported | | Wed 5/28, 6:43 AM PDT | Identified | Fix being implemented | | Wed 5/28, 7:35 AM PDT | Update | Systems coming back up, working on permanent fix | | Wed 5/28, 8:27 AM PDT | Monitoring | Fix implemented, monitoring results | | Wed 5/28, 10:53 AM PDT | Update | Reports of degraded performance, actively investigating | | Wed 5/28, 1:04 PM PDT | Update | Systems appear stable, rolling out fixes | | Wed 5/28, 6:49 PM PDT | Monitoring | Improvements and fixes deployed, continuing to monitor | | Thu 5/29, 10:03 AM PDT | Monitoring | Systems stable. Bi-directional sync maintenance 9:50–11:59 AM ET. | | Thu 5/29, 11:36 AM PDT | Monitoring | Deploying targeted fixes. Serving all 404s from cache. Degraded read performance. | | Fri 5/30 | Monitoring | Monitoring continues | | Sat 5/31 | Monitoring | Weekend monitoring | | Mon 6/1, 11:16 AM PDT | Resolved | Root cause identified and resolved. Systems stable since Thursday, May 29. | ### Path Forward We are using this incident to make lasting improvements to reliability and incident response: * **Storage capacity and isolation:** Restructuring how background processes interact with production storage to eliminate contention under load. * **Caching and performance:** The caching improvements shipped during the incident are permanent. We are continuing to expand cache coverage across additional endpoints and page types. * **Bot and traffic protection:** Strengthening rate limiting and abuse detection to prevent bot traffic from contributing to backend load. * **Monitoring and alerting:** Adding proactive capacity monitoring with earlier thresholds so the team can intervene before customers are affected. * **Incident response:** Improving our internal processes for faster escalation and more frequent status page updates during multi-day incidents. ### Final Note During the incident, we posted an update referencing a platform update. That was our initial hypothesis based on timing. Further investigation confirmed it was unrelated. The change in question was a routine, isolated configuration update and had no impact on the outage or any other customers. We should have waited for confirmation before publishing it, and we're tightening our internal process for status page updates as a result. We know how critical your documentation is to your customers, and this level of disruption is not acceptable. We have already shipped meaningful improvements to prevent recurrence, and the work outlined above will continue through the coming weeks. If you have questions, reach out to your account team or contact [support@readme.io](mailto:support@readme.io).

    Resolved

  2. TrueLayerPLN Payouts Settlement Delays

    We experienced a degraded performance on PLN payouts due to an issue with our banking partner causing delayed settlements. All transactions have now reached their intended terminal status and new payouts are are settling in a timely manner. Impact start time: 03/06/2026, 13:05 UTC Impact end time: 03/06/2026, 13:50 UTC Client actions: None

    Resolved

  3. AmplitudeAmplitude Platform Unavailability

    Service has been restored for the Amplitude application, and users should now be able to access the application normally. We have implemented a fix and are monitoring the system to ensure continued stability. We do not expect any data loss at this time. Thank you for your patience.

    Resolved

  4. Svix[EU] Elevated response times and error rates affecting some customers.

    We experienced an issue where some customer in the EU region experienced elevated response times and error rates. The time frames when this occurred: 23:44 - 23:46, 00:05 - 00:13, 00:38 - 00:48, 03:27 - 03:29, 5:34 - 5:36 UTC. This happened due to a significant spike in traffic (161x traffic the minute before), and the system not scaling fast enough to catch up. This affected customers routed to the same nodes that experienced this load.

    Resolved

  5. AmplitudeAmplitude Platform Unavailability

    We have resolved the issue affecting the Amplitude application, and services are operating normally again. We do not expect any data loss as a result of this incident. Our team will continue to monitor the system to ensure stability. Thank you for your patience.

    Resolved

  6. BunnyInvestigating Issues with Magic Containers and Databases

    Processing Delays and Intermittent Timeouts for Magic Containers On June 1, Magic Containers experienced degraded service for approximately one hour due to a network connectivity issue in our hosting provider's environment. Customers running workloads may have seen increased processing delays, intermittent timeouts, temporary disruption, or reduced availability as some workloads were automatically rescheduled. The issue was resolved after the underlying network conditions stabilized, allowing scheduling activity to resume normally. We are improving the resilience of Magic Containers so degraded connectivity can be detected and handled more effectively, not only complete outages. We are also adding safeguards to reduce unnecessary or duplicate workload rescheduling during degraded conditions, helping limit customer impact if similar infrastructure issues occur again.

    Resolved

  7. NotionPublished Notion sites not loading

    We implemented a fix for the issue causing some published Notion site homepages to fail to load and have monitored the service to confirm recovery. All affected services are now operating normally.

    Resolved

  8. SlackTrouble connecting or loading Slack

    This issue is now resolved for all users. Current status and recent actions taken: we've resolved the issue where some Slack users may have experienced message send failures and thread loading issues. We identified and addressed the root cause, and services have been fully restored. We apologize for any disruptions to your day.

    Resolved

Jun 2, 2026

  1. HootsuiteLinkedIn Video Publishing

    We can confirm that the issues affecting LinkedIn video publishing have been resolved. Any posts that failed to publish successfully can now be retried. Thanks for your patience while our team worked to resolve this.

    Resolved

  2. ZapierCode by Zapier is running into Lamda errors mentioning KMS

    This incident has been resolved. The issue that was causing some Code by Zapier steps to fail with the environment variable error has been fixed, and Code by Zapier is now operating normally. Any tasks that were affected during the disruption have been replayed, so no action is needed on your end. If you have any questions, or are running into any other issues, please reach out to our support team: https://zapier.com/app/get-help Thanks again for your patience while we working on resolving that.

    Resolved

  3. Customer.ioUI inaccessible

    The issues affecting the UI have been resolved, and the system is functioning normally.

    Resolved

  4. ClickHouse CloudNew service provisioning may fail in Azure

    Service provisioning is working, but some users may intermittently see an error message stating: “This service name is already in use.” This error is transient. If you encounter it, please refresh the page -your service should still be provisioning and will become visible shortly. We are working with Microsoft Azure to fully resolve the underlying issue.

    Resolved

  5. E2BDegraded sandbox creation

    The situation has been resolved. Please reach out if you encounter any errors going forward.

    Resolved

  6. JiraDegraded performance of Jira and JSM automations in US East

    On June 2, 2026, some Jira and Jira Service Management users in the US-East region may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers. Previously delayed automation rules are expected to be completed within 12 hours.

    Resolved

  7. DevinSessions Stuck

    Sessions were temporarily globally hanging due to session management change.

    Resolved

  8. NetlifyBlobs issues in Sydney region

    Between May 29th at 15:30 UTC till June 2 6:08 UTC, we experienced sporadic issues with Blobs in our Sydney region, affecting any Function using Blobs, including the ones that are generated by the framework runtimes. Our team has deployed a fix and the errors have subsided.

    Resolved

  9. ZapierCode by Zapier seeing errors

    We have been able to confirm that the update we previously pushed has fully resolved that error. So your Code by Zapier steps should be working as normal, and no longer running into those errors. We are also working on automatically replaying affected Zap runs that were running into this issue. If you are running into this error, please reach out to our support team: https://zapier.com/app/get-help Thanks again for your patience while we resolved that.

    Resolved

Older incidents