Fireworks AIService Degradation for one of our models on Serverless
We've resolved the incident and the affected service is now operational.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
We've resolved the incident and the affected service is now operational.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This issue is now resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
Our Engineering team has resolved the issue. These systems should now be operating normally. If you continue to experience any problems, please open a ticket with our support team.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We are observing a continued period of stability and at this point, we are marking the incident resolved.
Resolved
The issue affecting volume content access outside of sandboxes has been resolved. A domain configuration mismatch was causing authorization errors when customers attempted to read or write files directly through our volume API without using a sandbox. We apologize for the disruption this caused. If you continue to experience any issues accessing your volumes, please contact our support team.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
We've resolved the issue with our upstream provider.
Resolved
Queue times for Android and Windows jobs have reduced significantly over the last hour. You may still notice brief, isolated queuing at times, but this is no longer at incident-level impact. This was related to capacity constraints with a third-party infrastructure provider. We thank you for your patience while we monitored the situation. If you have any issues, please reach out to our Support team.
Resolved
We recently addressed issues affecting Open With integrations within Box. We would like to take this opportunity to further explain these issues and the steps we have taken to prevent them from reoccurring. Between 1:00 PM PDT and 2:40 PM PDT on July 16, 2026, some customers may have been unable to open or edit files using any Open With integration in the Box web application. During this period, affected files may have appeared unavailable or grayed out, and users may have encountered permission-related errors when launching an integration. Microsoft Office workflows, including Office Online in the browser and desktop editing through Box Edit, were among those impacted. The issue occurred after a recent service update unintentionally changed how integration workflows were handled, causing the product to return an empty set of available integration actions for affected files. We resolved the issue by reverting the service to the previously deployed version, after which service metrics and customer confirmations recovered. In addition, we are taking steps to reduce reoccurrence by improving testing, monitoring, and release practices for integration paths. # Analysis This incident highlighted opportunities to improve end-to-end testing for integration workflows and our automated detection process. The failure mode returned an empty action list rather than hard errors, which kept broad service-level signals near baseline and made the impact visible primarily through customer reports. # Corrective Actions Box has initiated the following corrective actions: * Expanded lower-environment end-to-end tests to validate Open With / Office Online behaviors after changes to integration-related code. * Added targeted monitoring and alerting for integration action and permission-check failures so regressions surface automatically. * Documented and formalized release and rollback runbooks for integration-related changes, including clear validation and rollback steps to reduce time-to-recovery. 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
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
As of 21:06 UTC, our Engineering team has resolved the issue affecting Spaces Cold Storage billing. An error in our billing processing system caused incorrect values to be reflected in daily usage and current invoices for customers with cold storage buckets. Our team identified and corrected an issue with the billing data sync, ensuring accurate usage reporting. If you continue to experience any issues, please open a ticket with our Support team. We apologize for any inconvenience this may have caused.
Resolved
The fix for this issue has been deployed to production and PayPal vaulting is working as expected.
Resolved
Normal service has been restored. Settlement delays have now been resolved. All funds have now reached end-user accounts as expected. Regular processing timings have resumed. Impact start time: 04/08/2026, 20:45 UTC Impact end time: 04/08/2026, 21:05 UTC Client actions: None
Resolved
This incident is resolved. Android builds are completing normally. Some Android builds and Linux workflow jobs failed early with the error "We've lost connection to the worker". Builds and jobs that failed with this error were automatically excluded from billing and can be retried.
Resolved
We have resolved the issue.
Resolved
This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
After monitoring, we have confirmed that issues affecting Management API performance have been resolved.
Resolved
The issue has been resolved. All impacted systems are now operating normally.
Resolved
Users experienced a delay in accessing paid features after a successful checkout or upgrade. We have resolved the issue.
Resolved
The publishing feature is down on Replit. We have identified the issue and working on the fix.
Resolved
This incident has been resolved.
Resolved
This issue is resolved now. Apologies for any disruption!
Resolved
We have narrowed our investigation and found the root cause of today's service outage. We are currently working on hardening this mechanism at our load-balancer level to prevent future occurrences.
Resolved
Duo Code Review sessions on GitLab.com have returned to normal operation. This issue is now resolved.
Resolved
Destination deliveries and workflow runs are caught up and processing normally again.
Resolved
Ubuntu package archive has recovered, and template builds and apt installs are working normally again. If you hit failures during the outage, please retry now or contact our support at support@e2b.dev. Thanks for your patience
Resolved
On July 30, 2026, the Claude Fable 5 model in GitHub Copilot experienced degraded availability for approximately 73 minutes, from 08:33 to 09:46 UTC. During this time, requests to Claude Fable 5 in Copilot chat and IDE surfaces frequently failed or timed out. This was caused by an issue with an upstream model provider. Other Copilot models were not affected, and users could continue working by selecting another model or 'Auto'. Availability for Claude Fable 5 fully recovered once the provider resolved their outage at 09:46 UTC, and we confirmed resolution at 10:12 UTC.
Resolved
The issue is now resolved, builds from a Git push to a Bitbucket repository are now succesfully triggered.
Resolved
All impacted services have now fully recovered.
Resolved
We became aware of an issue with Web Security Analytics related to Empty HTTP Accept Language and Content Length header values being logged. The issue lasted between 11:30 UTC on August 3, 2026, and 14:00 UTC on August 4, 2026. We can confirm that the issue is now resolved, 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/0D5a700001M5NvWCAV 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