CircleCIUsage API data delayed for 8/5
The Usage API issue has been resolved. Data has been loaded for yesterday, 8/5/2026. We appreciate your patience.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The Usage API issue has been resolved. Data has been loaded for yesterday, 8/5/2026. We appreciate your patience.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved. Log drain delivery has recovered and remaining delayed deliveries have been processed.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
On 2026-08-06 between 0900 - 1200 UTC, customers in GCP asia-south1 may have experienced high latency when communicating with their Elasticsearch deployments during this window. The cause has been identified and mitigated.
Resolved
Engineers have confirmed queues have drained and Reports behavior is stable across the board, so we're closing this out. Thank you for your patience while we worked on this one!
Resolved
From 2026-08-04 15:25 UTC until 2026-08-06 03:51 UTC, Asana failed to send some events to registered webhooks and to return them in the event streams API. Apps which rely on this should refetch the underlying data from the Asana API. Existing webhooks and event streams will continue to function, but events from the incident window will not be sent. Most events with type `task` and action `changed` were dropped during this period. Other events are not affected. The root cause of the incident was traced to a code change which unintentionally dropped change events for most fields on the task type, and the change was reverted.
Resolved
This incident has been resolved, and full performance has been restored to the Dashboard, Workflow Operations, and Terminus Operations. Live hosted sites and uptime remained fully operational throughout this event. Thank you for your patience while we worked to resolve this. If you encounter any further issues, please contact our Support team.
Resolved
# Executive Summary On August 4, 2026, between approximately 3:36 PM and 9:00 PM IST, customers using Infrastructure as Code Management \(IaCM\) on Prod0 and Prod1 were unable to access the Variable Sets settings page. The page rendered blank with no error message, and customers with Variable Sets attached to their workspaces could not view or manage them for the duration of the incident. Prod2, Prod3, and EU1 were not affected. Separately, during the same window, a scheduled maintenance action caused the IaCM settings tab to temporarily disappear across all environments. This was identified and reversed within the incident bridge call before significant customer impact occurred. We deployed a hotfix that restored full access to the Variable Sets page on Prod0 and Prod1 the same evening, and we are implementing permanent safeguards described below to prevent this class of issue from recurring. # Impact * Customers with the Variable Sets feature enabled on Prod0 and Prod1 were unable to view or manage Variable Sets for approximately 5–6 hours. * No data was lost or corrupted, this was a UI routing failure only; underlying Variable Sets data and configuration were not affected. * Prod2, Prod3, and EU1 were not affected by this issue. * A secondary issue, a scheduled feature flag operation caused the IaCM settings tab to temporarily disappear across all environments during the incident bridge call. This was identified and reversed within minutes. External customer exposure for this secondary issue is still being confirmed. # Root Cause A platform routing change released on July 18, 2026 updated how IaCM settings pages are resolved in the user interface. As part of that change, any settings page that had not been explicitly re-registered in the new routing structure became unreachable. The Variable Sets page had not been re-registered under the new routing structure, making it inaccessible in the environments where the routing change had been deployed — Prod0 and Prod1. Because the failure occurred at the routing layer rather than within the page itself, the page rendered blank with no visible error rather than showing a clear failure message. # Remediation ## Immediate We deployed a hotfix that re-registered the Variable Sets page in the updated routing structure, restoring access for all affected customers on Prod0 and Prod1. ## Permanent We are adding automated end-to-end tests that navigate to settings pages with relevant feature flags enabled, configured as a required gate in our release pipeline. We are also documenting and enforcing the routing constraint through static analysis so that settings pages are never inadvertently left out of the routing structure during future platform changes. # Action Items To prevent such issues from happening again, 1. Enhance automated tests, that navigate to settings pages with relevant feature flags enabled, configured as a blocking gate in the release pipeline, so this class of regression is caught before it reaches production. 2. Establish an explicit checklist step for future platform-wide architectural changes that verifies all existing settings pages remain accessible in the updated routing structure before the change is promoted to production.
Resolved
Between Aug 6, 06:42 UTC and 09:08 UTC, customers experienced failures with write operations across multiple DigitalOcean services, including Managed Databases, DOKS, Cloud Firewalls, DNS, Spaces, Block Storage Volumes, and event processing. Customers attempting to update Cloud Firewall rules, modify DNS records, manage object storage operations, provision or scale DOKS clusters and node pools, and make other infrastructure configuration changes experienced failures. These operations returned errors, preventing customers from managing their resources. Additionally, event processing was delayed or failed during this window, which may have impacted the timeliness of resource status updates and notifications. The services have recovered and are now operating normally. Customers should no longer experience issues with write operations, configuration changes, or event processing. We apologize for any inconvenience this may have caused. If you continue to experience issues with any of these services, please don't hesitate to open a support ticket. Our team will be happy to assist you.
Resolved
From 13:45 UTC to approximately 16:20 UTC, we experienced elevated errors retrieving balance transactions for automatic payouts. The issue is now resolved.
Resolved
We're seeing consistent background job and webhook delivery. The issue is now resolved.
Resolved
Between 10:40 AM PDT and 12:33 PM PDT on June 25, 2026, some users may have experienced difficulties while working in Box. During this time, users routed through one particular US region may have seen failures or delays when attempting to download folders as ZIP files. The issue occurred after a recent network component update impacted a backend service in that region. We restored the feature availability by reverting the change. In addition, we are updating configuration and monitoring practices for such changes to reduce the likelihood of recurrence. # Analysis As part of our continuous and ongoing service improvement efforts, we recently rolled out a change to our internal compute platform. In one of our US regions, this change resulted in a resource problem within our service mesh layers. This incident highlighted opportunities to improve how platform updates and service configuration changes are propogated across Box compute regions. # Corrective Actions Box has initiated the following corrective actions: * Improved our multi-region roll out monitoring and alerting * Audited resource configurations for multi-region services * Improved ongoing monitoring and alerting of multi-region services 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. All services are operating normally
Resolved
On August 5, 2026, between 11:02 and 11:54 UTC, the GitHub Copilot cloud agent service was degraded and new cloud agent jobs were delayed from starting. During this period 100% of newly submitted agent jobs were affected. The incident was limited to delay of cloud agent jobs. No jobs were lost and the queued backlog was processed by 13:00 UTC. This was due to an internal rate limit used to protect service availability that was enabled more broadly than intended delaying more traffic than expected. <br /> <br />The service recovered when the rate limit window expired. We then tuned the control so it no longer affected unrelated coding agent traffic. <br /> <br />We are working to improve the control's scoping and our monitoring and alerting to reduce our time to detection and mitigation of similar issues in the future.
Resolved
Scope has been determined to be non-production only, so the incident is marked as non-impacting.
Resolved
This incident has been resolved.
Resolved
We are pleased to inform you that the incident affecting our Storage offering has been resolved. <b>Start time :</b> 05/08/2026 17:00 UTC <b>End time :</b> 06/08/2026 13:05 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
Between approximately 09:25 and 09:45 UTC on August 6, some requests to api.sanity.io and apicdn.sanity.io returned errors or timed out for a small subset of customers. The issue has been resolved and API services have returned to normal operation.
Resolved
We have successfully resolved the Salesforce connection issues that affected some of our customers earlier today. What Happened A recent update to our Salesforce integration caused authentication failures for users who were automatically migrated to the new version. Customers attempting to connect or reconnect their Salesforce accounts received an error message. What We Did Our team quickly identified the root cause, stopped further migrations, and rolled back all affected users to a previous working version. We then systematically reactivated all affected Salesforce connections and replayed any impacted Zap runs to ensure no data was lost. Resolution All Salesforce connections have been restored and are now working normally. Your Zaps should resume processing automatically. If you experienced any issues earlier today, your connections are now active and ready to use. Thank You We sincerely apologize for this disruption and appreciate your patience as we worked to resolve this issue. If you have any questions or continue to experience problems, please contact our support team at https://zapier.com/app/get-help. Thank you for your continued trust in Zapier.
Resolved
The systems are stable and all services are functioning normally again. Our apologies for the inconvenience caused.
Resolved
This incident has been resolved.
Resolved
We have implemented a mitigation for the issue affecting new Disaster Recovery (DR) cluster creation. Initial validation has been successful, and new DR cluster creation is functioning as expected. We are continuing to monitor the service to ensure stability before considering the incident fully resolved.
Resolved
We've processed all backlogged events and have fully recovered.
Resolved
We are happy to report that in-app notifications are now functioning as expected. Thank you for your patience while our teams investigated and resolved the matter.
Resolved
We identified and mitigated a capacity issue in the backend service that manages telephony tokens and client SDK credentials. This caused intermittent HTTP 503 responses for some credential-related API requests. After increasing service capacity and resource allocation, the service remained stable throughout the monitoring period. We will continue reviewing capacity settings to help prevent recurrence.
Resolved
This issue has been resolved.
Resolved
The issue has been resolved
Resolved
This issue is resolved.
Resolved
We've applied mitigations that have stabilized the job queue. The issue is now resolved. Details in https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22654.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has been resolved.
Resolved
Between 22:03 - 22:16 UTC customers experienced delayed job dispatch, build processing and notifications. Additionally there were errors receiving webhooks during this period.
Resolved
Matchmaking in Fortnite Reload has returned to normal. We'll continue to monitor services to ensure everything remains stable.
Resolved
All impacted services have now fully recovered.
Resolved
Resolved – SSO Login Issues August 5, 2026 | 06:53 UTC – 08:44 UTC We have resolved an issue that affected SSO-based login for some Udemy Business users. During this window, a subset of users experienced login failures when attempting to authenticate via SSO. The issue was caused by a degradation in a third-party identity service and has been fully resolved. We apologize for the inconvenience and are taking steps to improve our detection and response for similar third-party disruptions in the future.
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
Resolved. Fix is now deployed that skips an unsupported tool schema and logs a warning instead of failing the request.
Resolved
The incident has been resolved.
Resolved