CircleCIIssues publishing orbs
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
Incident is mitigated so users should not see any further issues with Anyscale jobs
Resolved
All services are now healthy.
Resolved
We've resolved an issue that could cause incorrect email address tokens to appear when users pasted multiple email addresses into the member invite flow. In some cases, pasted email addresses were incorrectly matched to existing members with similar email addresses, requiring users to manually correct the entries before proceeding. We identified the cause of the issue and deployed a fix to ensure email addresses are now matched correctly when pasted into the invite flow. The issue is resolved for all affected users. If you're still experiencing any trouble, please reload Slack using Command + Shift + R (Mac) or Ctrl + Shift + R (Windows/Linux). We apologize for the disruption and appreciate your patience.
Resolved
We've confirmed search is stable and have re-ran any failed search ingestion(s) in this period for affected customers. No action is required by any customers. We thank our customers for our patience, and we're taking action to ensure that outages of this nature occur less frequently.
Resolved
This issue is now resolved.
Resolved
This incident has been resolved.
Resolved
Customers should no longer see any errors when selecting a template while creating or editing a campaign. This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Between 18:30 UTC and 18:41 UTC, some stores experienced elevated HTTP 500 errors on the storefront and API.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved
Resolved
This incident has been resolved.
Resolved
On June 5, 2026, between 15:35 UTC and 16:45 UTC, 0.11% of authenticated REST API requests incorrectly returned “not found” responses. Impact was concentrated among - and significantly higher for - users authenticating with user-to-server tokens to access organization-owned repositories.<br /><br />Some users of our GitHub for Slack and GitHub for Microsoft Teams integrations saw their channel subscriptions removed as those systems interpreted the transient "not found" response as durable loss of access. Roughly 12% of organizations with active channel subscriptions were impacted, with ~2% of all channel subscriptions being removed.<br /><br />These issues were triggered by a change to an internal authorization component that did not correctly resolve access for user-to-server tokens against organization-owned repositories. We mitigated the incident by disabling the accompanying feature flag at 16:45 UTC, after which API responses returned to normal. We then restored all impacted Slack and Microsoft Teams channel subscriptions, with restoration completed at 22:21 UTC.<br /><br />We are working to add retry and grace-period logic in the chat integrations so transient errors no longer trigger subscription deletions. In parallel, we are improving observability and gating of authorization changes so downstream impact is detected during scoped, gradual rollouts.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Open browser tabs with old logins to the Intercom app may be causing ongoing login/logout churn - closing old tabs or restarting web browser will prevent this from happening.
Resolved
Open browser tabs with old logins to the Intercom app may be causing ongoing login/logout churn - closing old tabs or restarting web browser will prevent this from happening.
Resolved
Open browser tabs with old logins to the Intercom app may be causing ongoing login/logout churn - closing old tabs or restarting web browser will prevent this from happening.
Resolved
We scaled our ingestion and are processing data in time.
Resolved
This incident has been resolved.
Resolved
The rollback is complete, and our latency readings are back to nominal levels.
Resolved
Our Engineering team has verified that all platform services are fully restored and stable. The Pantheon Dashboard is performing normally, and all background workflows are processing successfully without any lingering delays. The underlying issue has been completely mitigated, and we have concluded our monitoring period. Thank you for your patience while we worked to resolve this. If you encounter any further issues, please open a ticket with us at helpdesk@pantheon.io.
Resolved
This incident has been resolved.
Resolved
Our auth systems are back operational
Resolved
Our team has resolved the issue causing customers to experience errors in Xero. We apologise for any inconvenience this has caused. This was related to a recent configuration change which was rolled back.
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
Between 04:16 – 07:06 UTC, we saw elevated declines with some card transactions in Mexico due to an issuing bank being temporarily unavailable. This is now resolved.
Resolved
We've confirmed that the issue has been resolved with our upstream provider and error rates have remained stable at zero.
Resolved
We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.
Resolved
We are now confident that any of the tasks that were impacted by this incident and were delayed should now be operating as expected. We apologize for any inconvenience that this issue may have caused.
Resolved
Services have remained unaffected during our monitoring period. The Snyk Incident Response has been stood down.
Resolved
The service degradation affecting Artifactory uploads and downloads in the GCP US regions has been resolved. JFrog Engineers are continuing to monitor the service health closely.
Resolved
This issue has been resolved and service is operating normally. All checkpoint processing is now up to date and processing normally. A post-incident review will be conducted.
Resolved
This incident has been resolved.
Resolved
On Saturday, June 6th, the Codecov gpg public key located at keybase.io/codecovsecurity was absent. This caused widespread outages for users uploading with the Codecov - GitHub Action - CircleCI Orb - Bitrise Step In order to quickly move and prevent further outages, the Codecov team deleted the `codecovsecurity` account and created `codecovsecops` with the same public gpg key. This key can be verified against any pre-existing CLI to prove it is the same key and also at about.codecov.io/security. The key location was updated in all of the above uploaders on the latest versions.
Resolved
This incident has been resolved.
Resolved
We have determined that the issue impacting the Planner Calendar's month view is limited to slower-than-expected load times. Publishing functionality is not affected. We will be closing this active incident, and our team will continue to investigate the root cause through our normal bug resolution process. If you are experiencing slow load times in Planner, please contact our Customer Support team. We appreciate your patience.
Resolved