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
We've resolved the incident and the affected service is now operational.
Resolved
Snowflake Engineering has completed the postmortem of this service incident. A detailed Root Cause Analysis \(RCA\) is available on the Snowflake Community site: [https://community.snowflake.com/s/article/INC20000139](https://community.snowflake.com/s/article/INC20000139)
Resolved
This incident has been resolved.
Resolved
While Google Cloud has not yet provided an update, error rates have remained at normal levels. We therefore consider this incident resolved.
Resolved
On 2026-08-13 at 7:45 PM PT (2:45 AM UTC on 2026-08-14), we experienced a data ingestion latency. The issue was fully resolved at 8:35 PM PT (3:35 AM UTC on 2026-08-14), and all data has since been recovered. There was no data loss, and no customer action is required.
Resolved
A fix has been deployed and Mintlify documentation updates, Automations, and the Slack agent are now operating normally. Any incorrect billing emails sent during the incident can be disregarded, no changes were made to your billing or credit balance. We will be reaching out directly to customers who received one of these emails.
Resolved
## Summary Customers on Prod1, Prod2, and Prod3 \(US\) clusters experienced failures when loading SEI 2.0 dashboards on August 6, 2026, from 7:22 AM PDT to 9:03 AM PDT. Customers calling the SEI 2.0 API also experienced similar failures. No customer data was lost, and ingestion of all integration data continued to work uninterrupted. SEI customers using 1.0 were not impacted. ## Root Cause The incident was caused by resource exhaustion on the nodes serving queries. This resource degradation developed in a pattern that did not cross our existing alerting thresholds early enough to provide sufficient warning or allow mitigation before customer impact occurred. ## Impact Customers on Prod1, Prod2, and Prod3 \(US\) clusters were unable to load SEI 2.0 dashboards during the incident window. **Duration:** August 6, 2026, 7:22 AM PDT – 9:03 AM PDT \(~1 hour 41 minutes\) ### What was not impacted? * Data ingestion and processing * SEI 1.0 customers * Integrations and metadata flows No customer data was lost. ## Remediation Upon identifying the root cause, our team took immediate corrective action by adding capacity to restore the affected systems. Services were fully recovered, and all dashboards resumed normal operation at 9:03 AM PDT. ## Action Items To prevent from such issues happening again, Harness is/has Proactively added capacity updates have been applied to prevent this issue from recurring #### Enhanced Monitoring and Alerting Additional monitoring and alerting have been put in place to detect anomalies early, focused on a leading indicator, which in this case was thread pool exhaustion, before they can impact dashboard availability and data rendering. #### System Patch in Progress We are working with our vendor to apply a patch to remediate this and similar issues completely.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved and the affected services have been restored.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
The issue is now resolved.
Resolved
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
The issue has been resolved and the SLA feature is now running smoothly. Thank you for your patience.
Resolved
Matchmaking and partying up are returned to normal.
Resolved
We have resolved the incident as session load times have returned to baseline.
Resolved
All impacted services have now fully recovered.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
All backlogs have been processed.
Resolved
All impacted services have now fully recovered.
Resolved
Between 02:05 PM EDT (UTC -04:00) and 05:47 PM EDT (UTC -04:00), some customers experienced issues with marketing tools related to Form Submissions that trigger Workflow enrollment. This was caused by resource exhaustion. As of 05:47 PM EDT (UTC -04:00), our marketing tools are working properly and the incident has been fully resolved. HubSpot conducts a thorough review after each incident to understand the cause and prevent it from happening again. Learn more about HubSpot's commitment to reliability at www.HubSpot.com/reliability. The information on this page reflects our understanding of the incident and impact at the time of the update.
Resolved
We are no longer seeing issues with Logs Collection, Metrics Collection and Tracing Collection and normal operation has been restored at this time.
Resolved
The incident is resolved and the site is operational
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Our Engineering team has resolved the issue. We released the Terraform AWS Provider v6.60.0 with a fix. Affected 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
The queue of pending jobs on the affected runners has returned to normal and has stayed at that level. This incident is now resolved. Please open a ticket with support if you are still seeing job delays. Details: gitlab.com/gitlab-com/gl-infra/production/-/work_items/22702
Resolved
We've resolved the issue and the service is back to normal.
Resolved
This incident has been resolved.
Resolved
Granola services should now be up and running again - let us know at hey@granola.so "hey@granola.so": mailto:hey@granola.so if you're still having issues. Any notes that you took during the outage should be safe - you may need to hit retry on any notes to generate them fully. We're really sorry for any disruption.
Resolved
This incident has been resolved.
Resolved
We think the impact from the issue is over.
Resolved