CircleCIInsights service data is lagging
The upstream issue has been resolved, and the insights data from the last 24 hours has caught up. Thank you for your patience.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
The upstream issue has been resolved, and the insights data from the last 24 hours has caught up. Thank you for your patience.
Resolved
Etcd is stable. Services are back to normal.
Resolved
This incident has been resolved, and service is operating normally again. Thanks for your patience.
Resolved
🎉 The issue has been resolved and we are back to normal.
Resolved
This issue has been resolved.
Resolved
This incident has been resolved.
Resolved
All impacted services have now fully recovered.
Resolved
This issue is now resolved.
Resolved
Following an extended period of monitoring, the team has confirmed that the cluster remains healthy and stable.
Resolved
A lentidão e os erros 500 durante a navegação na funcionalidade de navegação do RD Station Marketing e RD Station CRM foram resolvidos com sucesso. Caso você note que sua conta ainda contém alguma inconsistência, por favor, entre em contato com nosso Time de Suporte através da nossa Central de Ajuda "através da nossa Central de Ajuda": http://ajuda.rdstation.com/..
Resolved
This was an issue with our internal telemetry - there is no customer impact. Sorry for the false alarm.
Resolved
No further impact to API or Web applications outside of the 1 minute window
Resolved
This incident has been resolved.
Resolved
Between approximately 13:40 and 15:05 UTC today, a subset of cloud test runs were unexpectedly terminated and marked Aborted (by system). This affected runs that were in progress during three short windows in that period; test results and metrics for completed runs were not impacted. We have identified the cause and no further occurrences have been observed since 15:05 UTC. A fix is in place. The platform is currently operating normally and test runs are executing as expected
Resolved
The email subscription and campaign features affected by this incident remain stable and are operating normally. Double opt-in confirmation emails, preview emails, and estimated recipient counts have returned to normal operation. Confirmation emails that failed to send during the incident are being resent. This incident has been resolved.
Resolved
Between 11:30 ET and 12:55 ET, some customers experienced elevated error rates. Braze engineers identified the issue and resolved it by rolling back a recent change and applying database optimizations. Error rates returned to normal shortly after each fix was applied, and they have remained stable for the past hour. This incident is now resolved.
Resolved
On July 31, 2026, at approximately 10:00 UTC, Akamai observed intermittent network losses affecting compute users accessing US locations from our India sites \(MAA and BOM\). Customers’ services in North America, particularly the Miami data center region, experienced increased latency, intermittent connectivity issues, slower data transfers, and difficulty reaching certain applications or services. Performance was unstable, with periods of normal operation followed by disruptions. To address the issue, Akamai applied a deny-all policy to the impacted upstream provider transit link, redirecting traffic around the impacted routes. Despite this mitigation, ongoing IPv6 losses occurred due to congestion between two alternative upstream providers, impacting some users. One provider acknowledged a bottleneck in the Asia region, and the alternate provider worked to reroute traffic away from affected links. The initial impacted service provider confirmed that two fiber cuts in Mexico caused congestion on the impacted routes. One of these fiber cuts was resolved at 23:43 UTC on July 31, 2026, and no further issues were observed following this mitigation. This summary provides an overview of our current understanding of the incident given the information available. Our investigation is ongoing and any information herein is subject to change.
Resolved
We are pleased to inform you that the incident affecting our Compute - Instance offering has been resolved. <b>Start time :</b> 05/08/2026 14:18 UTC <b>End time :</b> 05/08/2026 15:14 UTC <b>Root Cause :</b> A service disruption occurred due to an unexpected infrastructure failure. We apologize for any inconvenience caused and appreciate your understanding.
Resolved
Project upgrades have remained stable, we are resolving this incident.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
This issue has been resolved. The Optimize management experience for non-Webflow sites is loading normally. Live optimizations running on customer sites were not affected at any point. Thank you for your patience.
Resolved
This incident has been resolved.
Resolved
We have completed initial scaling and optimizations to enable more traffic through on the flux-3-video api. The BFL team are excited to see what everyone creates!
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
We had an incident on Storage offer which has now been resolved. Here are some supplementary details : <b>Start time :</b> 05/08/2026 11:46 UTC <b>End time :</b> 05/08/2026 13:35 UTC <b>Impacted Service(s) :</b> Some CEPH volumes were not available in this region <b>Customers Impact :</b> Customers might have experienced performance degradation and deterioration in their data redundancy <b>Root Cause :</b> A service disruption occurred due to an unexpected underlying infrastructure malfunction. We thank you for your understanding and patience throughout this incident.
Resolved
Webhook delivery failures have subsided in logs, and customer reports indicate no further errors. This incident is considered resolved.
Resolved
We can confirm that the issue was mitigated at 00:20 UTC on August 4, 2026, 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/0D5a700001M2nELCAZ 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
The issue has been resolved.
Resolved
No further issues have been observed during our monitoring period. The Snyk Incident Response has now been stood down.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved. The service disruption lasted approximately nine minutes, during which some Artifactory services were temporarily unavailable. All affected services have fully recovered and are operating normally. The environment is healthy, and our monitoring confirms continued stability.
Resolved
We believe the symptoms of this have largely subsided, looking at both customer cases and our internal metrics. We will share any more information as we get it, but for now resolving this incident as Atlas is fully operational.
Resolved
This incident has been resolved.
Resolved
The issue affecting some JFrog Cloud Platform customers in the Azure EU West region has been resolved. During the incident, some customers may have experienced a brief service interruption. Our team investigated the issue, validated service stability and continues to monitor the environment to ensure normal operation.
Resolved
This incident has been resolved.
Resolved
This issue has been resolved.
Resolved
We are aware that earlier today, Wednesday 5th August, at roughly 9am UTC, there was a temporary issue that impacted the publishing success rates of Pinterest. It does appear that this was an issue directly with Pinterest's API, and it was a transient issue that recovered by 9:50am UTC. Publishing success for posts from Buffer to Pinterest are back to normal levels now. If you noticed any of your posts from earlier today to Pinterest have failed, retrying them again in Buffer should allow them to post normally. We're very sorry for any inconvenience caused by this incident.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
The backlog of delayed settlement webhooks has now been fully cleared and settlement notifications are back to being processed in real time. Normal service has been restored. Impact Start Time: 05/08/2026, 00:17 UTC Impact End Time: 05/08/2026, 09:03 UTC Client actions: None
Resolved
We are no longer seeing issues with Cloud SIEM Processing and Data Indexing and normal operation has been restored at this time.
Resolved