EntireDelayed commit and checkpoint processing
This issue has been resolved and new commits are being processed promptly. We are backfilling old messages, and will continue improving the reliability of this process over the coming days.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This issue has been resolved and new commits are being processed promptly. We are backfilling old messages, and will continue improving the reliability of this process over the coming days.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. Please refer to GitHub's status page post for more details: https://www.githubstatus.com/incidents/k5z4d1v1tqmt
Resolved
The system has recovered and functionality has returned to normal.
Resolved
The intermittent issues affecting repository scans, project imports, and Pull Request status checks have been fully resolved. The root cause was an upstream degradation with GitHub Cloud app installation token authentication, which has now been mitigated on the GitHub side (ref: GitHub Incident k5z4d1v1tqmt). If you continue to experience issues with your PRs, imports, or repository scans, please reach out to our support team for further assistance.
Resolved
This incident has been resolved.
Resolved
We have been monitoring the clusters for the past 16 hours and have not found any further disruptions.
Resolved
Normal service has been restored. Payins and Payouts in Poland are no longer experiencing settlement delays. Impact start time: 23/05/2026, 10:32 BST Impact end time: 23/05/2026, 15:35 BST Client actions: None
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
The issue has been fixed and our metrics are looking normal again
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The data plane node log download has recovered.
Resolved
The issue has been resolved. All impacted systems are now operating normally.
Resolved
Systems are back to normal.
Resolved
The issue with TikTok posts has been fully resolved, and all systems are now operational. We appreciate your understanding and apologise for any disruption this may have caused.
Resolved
The issue has finally been resolved.
Resolved
This incident has been resolved.
Resolved
We recently addressed issues affecting folder and collection browsing, and related APIs. We would like to take the opportunity to further explain these issues and the steps we have taken to keep them from happening in the future. Between 05:22 PM PDT and 07:04 PM PDT on May 6, 2026, some users may have experienced difficulties while working in Box. During this time, users reported failures and elevated errors when loading folders and collections, intermittent service errors, and degraded AI-related functionality. The issue was caused by runtime saturation in a backend API service that had been gradually approaching its capacity limits over several weeks. During peak traffic hours, multiple service instances simultaneously became unable to respond to internal health checks within the configured timeout. As those instances were restarted, traffic shifted to the remaining instances, increasing load on them and creating a cascading failure. We mitigated the issue by stopping the restart cycle, routing traffic to alternate paths, and increasing service capacity. **Analysis** This incident revealed several contributing causes: * Insufficient scaling signals — autoscaling was primarily configured around CPU utilization. For this service, CPU utilization did not accurately reflect runtime saturation, so the fleet did not scale early enough in response to the actual bottleneck. * Health check sensitivity under load — health checks were configured with timeouts that did not account for the service’s behavior under sustained runtime saturation. Once instances became slow to respond, restarts amplified the problem by shifting more traffic to the remaining instances. * Gradual capacity erosion without alerting — the service had shown intermittent health check failures during prior peak traffic periods. Those earlier events were narrow enough to self-recover, but they were not surfaced as a clear trend requiring action. * Retry amplification — as service instances became unavailable, upstream retry behavior added additional load to the remaining healthy instances, accelerating the cascade. This incident highlighted opportunities for improvement in how we detect and respond to runtime saturation that is not always visible from CPU metrics alone. It also reinforced the need for stronger end-to-end observability, clearer health-check visibility, and validated mitigation paths for service instability. **Corrective Actions** Box has initiated the following corrective actions: * Improved runtime monitoring and alerting — we added alerts for runtime saturation metrics that detect this class of failure independently of CPU utilization, providing earlier warning before customer impact occurs. * Revised autoscaling strategy — we reconfigured autoscaling to trigger on signals that reflect actual service capacity and validate that the fleet scales correctly under realistic load conditions. * Health check and resilience tuning — we are reviewing health check configurations and retry behavior to reduce the risk that transient runtime saturation can turn into cascading restarts. * Capacity validation and load testing — we are establishing load testing against production-representative traffic patterns and maintaining capacity headroom until the service's efficiency improvements are validated. * Runtime performance improvements — we identified and are implementing changes to the service framework that significantly reduce per-request overhead, providing more headroom against future saturation. 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 we have provided some clarity here and we would be happy to answer any questions you may still have regarding this matter. Sincerely, The Box Team
Resolved
Some API requests may have experienced elevated error rates for approximately 2-3 minutes starting at 16:43 UTC on May 22, 2026. The issue has been resolved now.
Resolved
We've detected the same error happening again today. Some MCP connections would not connect between 19:29 and 20:39 UTC. We've rolled back to a known good version as soon as we detected the incident. Due to elevated and extensive usage from our customers, we're actively migrating our MCP to a new architecture in the upcoming days, which should resolve both the existing problems and improve our downtime detection capabilities.
Resolved
The necessary mitigations have been applied and all systems are now operating normally.
Resolved
We have confirmed Slack notifications are now coming through for segment approvals again.
Resolved
This issue is now resolved.
Resolved
Snyk engineers have rolled out a fix across all environments. Our engineers will continue to monitor the situation. The Snyk Incident Response has been stood down.
Resolved
This incident has been resolved.
Resolved
Latency and error rates have remained at normal levels across all services following the implementation of our fix. This incident is resolved.
Resolved
This has been resolved.
Resolved
The issue has been resolved, and we are closely monitoring the situation to ensure continued stability.
Resolved
Resolved
Resolved
This incident has been resolved.
Resolved
Affected instances have been corrected in the AWS us-east-1 region. We apologize for the disruption this issue caused. We are committed to the reliability of all ClickHouse Cloud services and appreciate your understanding as we continue to improve our systems and operations. If you have questions or need information on a specific ClickHouse service, please contact support "contact support": https://clickhouse.cloud/support.
Resolved
This is an administrative update, marking the incident as Resolved. There has been no further impact since 23:20UTC on May 21 2026.
Resolved
The project dashboard, hosting dashboard and "eas deploy" are operational again. For more information about the incident and timelines, see https://www.cloudflarestatus.com/incidents/znll7lfnd35h
Resolved
Build failures have been resolved The build failure issue that began at 17:28 CEST has been fully resolved as of 18:13 CEST. The failure rate, which peaked at approximately 40%, has returned to normal levels.
Resolved