AmplitudeWe are actively investigating bigquery exports taking a long time to complete
This incident has been resolved.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
This incident has been resolved.
Resolved
Between July 23, 2026 at 18:45 UTC and July 24, 2026 at 11:19 UTC, an abuse mitigation update caused some legitimate customers whose traffic was routed through our Central Europe and South America edge locations to be incorrectly blocked from GitHub.com. We estimate that approximately 0.25% of GitHub.com requests were affected during this period. This was caused by an abuse mitigation configuration that incorrectly classified legitimate traffic. We mitigated the incident by reverting the update. We are adding validation and safeguards to prevent similar incorrect blocking in the future.
Resolved
Stock replenished to healthy levels.
Resolved
All delayed messages have been processed. Systems are operating normally
Resolved
This incident has been resolved.
Resolved
This incident has now been resolved.
Resolved
Our notification provider has identified the root of the issue that is causing voice call failures to some India-based mobile numbers. We understand the inconvenience this may cause and appreciate your patience while our provider works on restoring the service. If you have experienced any issues with voice notifications, please contact our Support for assistance.
Resolved
This issue has been resolved.
Resolved
This issue has been resolved.
Resolved
Between 07:46 UTC & 10:24 UTC today, some users in India accessing resources in the NYC region may have experienced connectivity issues. The impact was limited to users using Airtel as their ISP. Our investigation determined that the issue was caused by an internal network issue within Airtel and was not related to DigitalOcean network. The connectivity issue now appears to be resolved, and users should no longer experience problems accessing their resources. We apologize for any inconvenience this may have caused. However, if you continue to experience any connectivity issues, please don't hesitate to open a support ticket for further investigation; we'll be happy to assist you further.
Resolved
It has been resolved and Notion is back to normal.
Resolved
This incident has been resolved.
Resolved
From 10:56 - 12:00 UTC, we saw elevated error rates and response times with the API. This is now resolved.
Resolved
This incident has been resolved.
Resolved
Cloudflare has stabilized. We will continue to monitor this throughout the day and weekend.
Resolved
This incident has been resolved.
Resolved
We’ve completed the revert of the recent change and have validated that this has brought customers out of impact and can now successfully send a message to a channel using Workflows that include 'refer to a message link'. We apologize for how this incident may have affected you and your business.
Resolved
No further errors have been observed during our monitoring period. The Snyk Incident Response has now been stood down.
Resolved
Commerce Engineers identified that additional remediation was required during the monitoring period. The issue affecting Catalog Import/Export for a subset of stores has now been fully resolved, and the system is operating normally.
Resolved
The issue has been resolved.
Resolved
This incident is now resolved. The underlying issue has been fully mitigated, and all delayed default update webhooks have now been delivered. New item connections and their initial and historical transaction webhooks are firing normally, and new transaction updates, including default update webhooks, are being processed normally.
Resolved
All impacted services have now fully recovered.
Resolved
This incident has now been resolved.
Resolved
We've resolved the incident and the affected service is now operational.
Resolved
We identified and recovered affected data. No customer operation impacted.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
Earlier login problems have been resolved and logins are working normally again. This incident is now considered closed. Details: https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/22551
Resolved
After a period of monitoring, we can see that reminders are now working as expected following the fix deployment. This issue has been resolved as of 03:00 UTC, July 24. We apologize for any inconvenience this issue has caused you.
Resolved
Mitigated issue
Resolved
Our team has resolved the issue impacting customers trying to navigate and use Xero. We apologise for any inconvenience this has caused. A product release caused some features in Xero to become unavailable, and a rollback has restored service.
Resolved
All impacted services have now fully recovered.
Resolved
🎉 The issue affecting Dashboard login has been resolved. All Cohere services are operating normally. Thank you for your patience while we worked through this.
Resolved
## Summary On July 14, 2026, certain Harness Feature Flag \(FF\) Classic customers on the Prod1 and Prod2 production environments were unable to view Feature Flags in the Harness platform. Affected requests returned an authorization error \(HTTP 403\), so Feature Flags were not visible for those users until access was restored. The behaviour was caused by a planned security update that began requiring an additional Feature Flags permission for related read operations. Users whose roles did not yet include that permission were correctly denied access, which appeared as a product failure. Harness temporarily rolled back the Feature Flags service change to restore access, updated the required permissions for affected users and roles, and confirmed that Feature Flag visibility returned to normal. The stronger permission checks remain in place going forward. ## Impact During the customer-reported incident window on July 14, 2026 \(status page approximately 11:25 UTC to 11:57 UTC\): * Certain Feature Flag Classic customers on **Prod1** and **Prod2** were impacted. * Affected users could not view Feature Flags in the Harness UI / API and received **403 Forbidden** responses. * Impact was limited to users and roles that did not yet have the updated Feature Flags permission required by the security change. * A public status page update was posted for Prod1 and Prod2 Feature Flags. There was **no data loss**, no change to stored feature flag configurations, and no impact to Feature Flag evaluation for applications whose SDK credentials and permissions were unaffected. Customers and users with the required permission continued to operate normally. ## Root Cause Harness deployed a planned Feature Flags authorization update that enforces the `ff_targetgroup_view` permission on target-related read paths used when viewing Feature Flags. This enforcement is intentional and remains the expected behaviour. Users and roles that had not yet been granted `ff_targetgroup_view` received 403 responses and could not see Feature Flags. From the customer’s perspective this looked like an outage; it was an authorization denial due to missing required permissions after the security update. ## Mitigation Harness completed the following mitigation steps: * Temporarily rolled back the Feature Flags service in Prod2 and Prod1 \(and aligned Prod0\) to restore access quickly while permissions were corrected. * Updated / granted the required `ff_targetgroup_view` permission for affected users and roles. * Verified that Feature Flag visibility returned to normal and closed the status page incident. These actions restored customer access. The permission enforcement introduced by the security update **remains in effect** going forward; the lasting fix is correct permission assignment, not removal of the check. ## Preventive Actions To avoid a recurrence of this issue, Harness is taking the following actions: * Keeping the stronger Feature Flags permission checks in place as the permanent security posture. * Ensuring role and permission updates for `ff_targetgroup_view` are applied with \(or before\) similar authorization changes in production.
Resolved
All impacted ACH and Same-day ACH transfers's status have been updated to posted. They will be marked as settled later today.
Resolved
We have resolved the issue that prevented users from logging into Calendly.
Resolved
## Summary On July 20, 2026 from 00:22 to 01:45 UTC, CircleCI customers using our GitHub integrations experienced failures running pipelines and experienced workflows getting stuck. During this incident, some pipelines triggered by users using GitHub failed to start or ran as error pipelines. Customers whose pipelines failed or ran as error pipelines during this window should re-run them. This was caused by an [upstream API degradation at GitHub](https://www.githubstatus.com/incidents/ph5nns5y4gxj), which impacted many GitHub APIs that CircleCI uses to trigger and run pipelines. By 01:45 UTC, GitHub APIs recovered, and customer pipelines ran normally. The original CircleCI status page can be found [here](https://status.circleci.com/incidents/9lvbbbs9l87b). ## What Happened \(all times UTC\) Beginning 00:22 on July 20, 2026, GitHub began returning elevated errors for the following API requests: * `applications/*/token` * `repos/*/commits` * `repos/*/*/contents/*` * `repos/*/*/hooks` * `repos/*/*/hooks/*` * `repos/*/*/keys` * `repos/*/*/pulls` * `repos/*/*/statuses/*` CircleCI relies on these requests to correctly trigger and run pipelines. At 00:22, our internal monitoring alerted us to the problem. Our team began investigating, and found that a small number of pipelines belonging to GitHub projects either failed to start or ran as error pipelines. This included scheduled pipelines and workflows. In addition, a small number of customer workflows experienced stuck jobs and required a re-run of the workflow to fix. At 01:45, GitHub recovered and pipeline processing returned to normal operating levels. Only pipelines triggered during the incident window were affected, and customers should re-run those pipelines. ## Future Prevention and Process Improvement We are actively working to improve the resilience of pipeline processing during GitHub service disruptions to reduce the customer impact of similar incidents in the future. We are scoping features that will help customers recover with reduced manual steps after incidents resolve. Customer experience is our top priority, and we commit to continually improving the reliability of our systems to match the trust that our customers place in us. Please reach out to our support team with any questions or concerns.
Resolved
All impacted services have now fully recovered.
Resolved
Codex conversations are fully operational now.
Resolved
This incident has been resolved.
Resolved