Fireworks AIService Degradation for one of our Serverless models
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 incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
On 2026-08-19 at 10:41:25 AM PT, some customers who had not explicitly enabled AI through the AI Controls page were placed in “Admin preview,” and non-admin users could not access AI features. The issue was fully resolved at 12:41 PM PT on 2026-08-19. No data was impacted, and no customer action is required. Following the fix, customers should now be able to access Global Chat and see the Global Chat interface instead of the “No access” message.
Resolved
Full capacity restored to api.eu.bfl.ai
Resolved
This incident has been resolved. Between 19:20 and 00:10 UTC, session data and observability ingestion was delayed by 45-60 min. The root cause has been addressed and data ingestion returned to normal by 00:10 UTC. No data was lost during this window.
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:team@fin.aiai if you have any further questions or if you’re still seeing any unexpected behaviour.
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:team@fin.aiai if you have any further questions or if you’re still seeing any unexpected behaviour.
Resolved
This issue should now be resolved and all services are restored to normal functionality. Please don’t hesitate to reach out to team@fin.: mailto:team@fin.aiai if you have any further questions or if you’re still seeing any unexpected behaviour.
Resolved
The upstream APT package mirror in AWS us-east-1 has recovered and we're no longer seeing impact when starting new brainstore instances.
Resolved
We’re investigating elevated API error rates impacting parts of the application.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
Some users may have seen an error or a blank preview when opening or editing apps built with Retool's AI app builder. The issue has now been resolved.
Resolved
Errors related to Pipedrive invalid IDs are resolved. If you have any further questions, please reach out to us: https://zapier.com/app/get-help
Resolved
Snyk engineers have deployed a fix and have confirmed the GitHub Cloud App installation is working as expected. The incident is now resolved.
Resolved
Our Engineering team has confirmed the regional control plane is healthy and CPU Droplets, Managed databases, Load balancers, Block storage, Kubernetes (DOKS) and Spaces are operating normally. GPU Droplets continue to be impacted and our teams are working to restore all nodes. We will communicate with GPU Droplet customers separately via Slack and email with more information and regular updates. Thank you for your patience throughout this incident. If you continue to experience any issues, please open a support ticket from within your account.
Resolved
The incident is resolved
Resolved
FLUX.2 [flex] restored - vendor mitigation in place with full recover observed
Resolved
We observed Cosmos agent MCP calls failing with 401 errors.
Resolved
We have resolved the issue.
Resolved
Profile property updates are now being reflected in real-time segments at normal speed. Any profile property changes made during the incident window have been reflected in segment membership as expected, and no action is required on your part. This incident has been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
After monitoring traffic, we're seeing forms respond as expected. We now consider the issue resolved. Thank you for your patience as we worked to resolve the issue.
Resolved
We are no longer seeing issues with Cloud SIEM Processing and normal operation has been restored at this time.
Resolved
On August 18 from 23:59 to 00:03 UTC (August 19), a subset of API requests (primarily AuthKit authentication endpoints) returned HTTP 500 errors. Automatic maintenance of a large, seldom-used internal index caused brief write-ahead-log contention on a primary database that exhausted connection capacity; service recovered automatically within four minutes. We identified the root cause and removed the index from production at 03:53 UTC on August 19 to prevent recurrence.
Resolved
This incident has been resolved.
Resolved
We have identified an issue that caused a subset of customer jobs to fail or process more slowly in Batch SaaS EU1, US1 and US2 between 15:38 to 16:34 BST. This issue has been resolved and we have restored the service to normal performance levels. We apologise for any inconvenience.
Resolved
All pension rates rendered by content blocks are now correctly showing a single £ symbol.
Resolved
We have confirmed that the fix has been effective and are marking this incident as resolved.
Resolved
Automated actions, including Loop automations and Linear Agent responses, are now processing normally. We’re taking steps to help prevent this from recurring.
Resolved
LiveRamp Connect UI is now fully available again. Thank you for your patience.
Resolved
This incident has been resolved
Resolved
Issue was resolved
Resolved
Back to normal propagation delay
Resolved
Billing records are being processed normally
Resolved
This has been resolved since 2026-07-15
Resolved
This incident has been resolved. If you are still experiencing an issue, please let us know in our Etsy Forums (https://community.etsy.com/t5/Technical-Issues/bd-p/bugs).
Resolved
This incident has been resolved. From 13:00–13:12 UTC, users creating new streaming sessions using the EU endpoint were receiving a 3005 close code.
Resolved