SentryDelayed ingestion on us region
We've burned through our spans backlog. Latency across span consumers are normal.
Resolved
Outages and recoveries from the services you depend on.
40 incidents
We've burned through our spans backlog. Latency across span consumers are normal.
Resolved
This incident has been resolved.
Resolved
GitHub has completed remediation of the SSH deploy key incident. Terraform runs using GitHub-hosted modules/sources over SSH have recovered, clone operations are functioning normally, and no further authentication failures are being observed.
Resolved
Earlier today, some Translate by Zapier requests failed with 403 “User Rate Limit Exceeded” errors due to a Google Integrations Production Google Cloud billing configuration issue. This has been resolved and we’re seeing successful translations again with no ongoing errors. If you had Zap runs fail during the incident window, you may need to replay those runs to complete processing. If you experience any ongoing issues, contact Support: https://zapier.com/app/get-help Thank you for your patience.
Resolved
Resolved – This incident is resolved. Between Jul 18 02:40 UTC and Jul 20 14:00 UTC, a subset of Elastic Agents were unable to report metrics to AutoOps across all regions. The underlying issue has been corrected and data is flowing normally. Impacted deployments may notice some gaps in their AutoOps monitoring data during this timeframe.
Resolved
The recent issue impacting the Cloudinary MCP Connector has been successfully resolved. We can confirm that all services are now back to normal operation.
Resolved
This incident has been resolved.
Resolved
From 09:59 UTC to 10:13 UTC on July 21, 2026, we saw elevated error rates on BLIK payments affecting multiple customers. This issue is now resolved. We confirmed that the issue was upstream and was restored without Stripe actions.
Resolved
On July 16, 2026, between 08:50 UTC and 09:50 UTC, the GitHub MCP Server’s web_search tool experienced elevated failures. The average error rate was 42% and peaked at 82% of requests to the tool. Other GitHub MCP Server tools were unaffected. This was caused by degradation at a downstream web search provider.<br /><br />The incident was mitigated when the downstream provider recovered, after which we confirmed that the tool’s success rate had returned to normal.<br /><br />We are improving the tool’s resilience and failure handling to reduce the customer impact and duration of similar incidents.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
# Summary On July 9, 2026, some customers in the Harness Prod3 cluster experienced pipeline failures over a ~2.5-hour window, despite making no changes in their pipelines. Shell Script steps failed when fetching scripts from the Harness File Store, and Kubernetes deployment steps failed when retrieving secret encryption details. # Impact 1. **Affected users**: Some customers using the Harness Prod3 cluster reported pipeline execution failures. 2. **User impact:** Customers experienced failures in Shell Script and Kubernetes deployment steps. Impacted pipelines required manual retries after the incident was resolved. 3. **Scope:** This was not a platform-wide outage. The issue was isolated to specific APIs in our internal service within the Prod3 cluster. # Root Cause The incident was caused by degraded performance in a downstream service. This led to a storm of timeout errors in our internal service, which caused these failures. # Mitigation Engineering identified the change that caused this issue in the downstream dependency service and deployed a patch to restore it. Once deployed, pipeline executions returned to normal success rates. # Preventive Measures & Next Steps 1. Added additional monitoring and alerting on the downstream service to detect performance degradation earlier. 2. Reviewing timeout and retry logic in the internal service to improve resilience against downstream latency spikes. 3. Evaluating circuit breaker patterns to prevent cascading failures from downstream dependencies.
Resolved
The fix resolved the issue and asset creation back to operational.
Resolved
We're seeing elevated delays when publishing apps. Some apps are getting stuck in the 'Security Scanner' stage. We're investigating.
Resolved
We resolved issues related to the earlier degradations of Replit performance.
Resolved
This incident has been resolved and all backlogs have been processed.
Resolved
This incident has been resolved.
Resolved
From 19:40 to 22:10 UTC, we saw elevated errors for Blik payment method payments. This is now resolved.
Resolved
We have continued to see normal activity in this region with latencies holding at pre-incident levels. This incident is now resolved.
Resolved
An internal system had an issue which made the bubble editor temporarily become unavailable.
Resolved
The fix has been successfully implemented and service has now been restored. Following monitoring and validation, client connectivity and associated platform services are operating normally. We will continue to monitor the environment closely to ensure ongoing stability, but no further customer impact is expected at this time. Thank you for your patience while we worked to resolve this issue
Resolved
This incident has been resolved.
Resolved
We're seeing recovery on our end and errors and latencies on Visibility APIs have dropped. We will continue to monitor this but the incident is mitigated and resolved.
Resolved
This incident has been resolved.
Resolved
This incident has been resolved.
Resolved
The issue has been resolved. All impacted systems are now operating normally.
Resolved
This incident has been resolved.
Resolved
On July 20, 2026, some Jira and Jira Service Management users may have experienced performance degradation of automation rule executions. The issue has now been resolved, and the service is operating normally for all affected customers.
Resolved
This incident has been resolved.
Resolved
We have fully burned the backlog of EU error events ingested during the incident. Latency is normal across all event types.
Resolved
We can confirm that the issue was mitigated at 04:10 UTC on July 19, 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/0D5a700001JVmHpCAL 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
Some customers may have experienced lag in Temporal Cloud metrics (OpenMetrics - v1), starting from 12:45 UTC to 13:25 UTC. Metrics lag have since recovered back to nominal.
Resolved
We experienced intermittent API request timeouts in the US region between 12:38 UTC and 12:43 UTC. The issue has since been resolved, and services are operating normally.
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
This incident has been resolved.
Resolved
The issue has been resolved at 10:00 CEST.
Resolved
Starting around 00:33 UTC on July 20, 2026, some hosts in the Milan, Italy data center became unavailable, impacting customer access to Linodes. The investigation identified that this issue occurred during scheduled router firmware updates. While we follow a phased upgrade process to prevent service disruption, an unexpected intersection of concurrent maintenance activities led to a temporary loss of network connectivity for the affected hosts. Service was fully restored by 02:16 UTC on July 20, 2026, and all systems are now operating as expected. Internally, we are reviewing our change management and maintenance scheduling procedures to ensure better coordination and prevent similar issues in the future. 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 recurrence. 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
The GitHub incident has been resolved upstream.
Resolved
All impacted services have now fully recovered.
Resolved