Origin Inspector
We are seeing increased errors across multiple Fastly services that utilize a common third party service provider, unrelated to Fastly's Edge Cloud Network.
Fastly has launched acute incident response practices to investigate into this issue further in an effort to reduce the impact to our customers.
As our engineers determine the scope of impact our Customer Escalation Management team will be updating the impacted components on this status post.
We're aware of an ongoing Google Cloud incident, detailed on their status page, which is affecting several Fastly services. Customers may be experiencing increased latency due to impact to our KV Store.
Specifically, those trying to access their control plane via manage.fastly.com might notice that several key Observability features are not loading, including Billing, Historical Stats, Log Explorer & Insights, Origin Inspector, Real-Time Log Streaming, and Real-time Analytics. You may also find it difficult to engage with API endpoints. Additionally, customers might see elevated errors when accessing Fastly webpages and documented resources.
Our engineers are working to restore these services as a high priority and we will provide more information shortly.
You can monitor the Google Cloud incident here:
We've confirmed that customers won't receive status post notifications through their Support Slack channels during this incident.
However, we want to assure you that your ability to request a support case through our Support Slack services remains unaffected. You can still open new support cases as needed.
Google Cloud has communicated that they have successfully deployed mitigations to the majority of their services. We are now observing a gradual recovery of Fastly services.
We will continue to monitor this situation with the highest priority until all Fastly and customer services are fully restored.
We have continued to monitor the Google Cloud Status Page for the latest information by the third party service provider.
Incident Update: Full Recovery and Root Cause Identified
Current Status: Resolved
We're confirming that all services impacted during yesterday's incident have fully recovered. Our teams continuously monitored the situation and verified the stability of all affected systems.
Root Cause Analysis
Our investigation has confirmed that the increased errors and latency across our KV Store, control plane, and certain Observability features were a direct result of the Google Cloud disruption on the 12th of June 2025.
Google has publicly shared a post-mortem regarding the incident. It includes specific information about the root cause—an invalid automated quota update to their API management system—along with their mitigation strategies and steps they're taking for future prevention.
Next Steps
For a comprehensive understanding of the incident's origin, mitigation, and Google's preventative measures, we encourage customers to review the official Google Cloud Status Page. This provides a full breakdown from their perspective.
Additionally, our Product and Engineering teams will thoroughly review all Google Cloud Platform (GCP) reports to determine mitigation strategies and ensure they are adopted as part of our long-term preventive measures to ensure our systems are more resilient to third-party outages of this kind in the future.
We appreciate your patience and understanding as we worked through this third-party event. Our focus remains on providing reliable and high-performance services.
We're currently investigating performance issues with our Origin Inspector service.
All other services are unaffected.
Our engineers have identified the contributing factor and are applying a fix to our Origin Inspector service.
Engineering has deployed a fix and have confirmed a gradual recovery to our Origin Inspector service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
Engineering has confirmed that our Origin Inspector service has been fully restored. Customers may have experienced increased latency of Origin Inspector data being visible in the Historical Stats API from 21:50 to 23:15 UTC.
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
We are investigating elevated errors for evaluating Fastly Alerts configured on Domain Inspector and Origin Inspector metrics.
Our engineers have identified the contributing factor and are applying a fix our Domain Inspector, Origin Inspector.
Engineering has confirmed the impact to Domain Inspector, Origin Inspector has been mitigated.
Engineering has confirmed that impact to the Domain Inspector and Origin Inspector metrics has been fully restored. Customers may have experienced degraded service for Fastly Alerts from 21:42 to 23:05 UTC.
This incident is resolved.
We're currently investigating performance issues with our Origin Inspector service.
All other services are unaffected.
Our engineers have identified the contributing factor and are applying a fix to Origin Inspector
Engineering has deployed a fix and have confirmed a gradual recovery to Origin Inspector. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
Engineering has confirmed that our Origin Inspector service has been fully restored. Customers may have experienced missing historical Origin Inspector metrics in both the APIs and web interface from the 14th December 2023 at 00:00 to the 20th of December 2023 at 03:18 UTC.
This incident is resolved.