Real-time Log Streaming
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.
Fastly Engineers detected a performance impacting event affecting the Real-time Log Streaming service.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Due to a recent configuration change, duplicate log messages are being emitted for Compute Log Tailing and for Log Explorer & Insights. Fastly has identified the issue and is reverting the configuration change.
Remote Log Streaming services is not affected by the duplicate log messages.
We are investigating elevated errors to our Real-time Log Streaming services.
Our engineers have identified the contributing factor and are applying a fix to our Real-time Log Streaming services.
Engineering has confirmed the impact to our Real-time Log Streaming services has been mitigated.
Engineering has confirmed that our Real-time Log Streaming services have been fully restored. Customers may have experienced logs being discarded or missing in addition to potential missing data in their WAF metrics from 18:09 to 18:50 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2024-10-04 18:37:33 UTC
Note: Our Customer Escalation Management team will update the start date and time of the initial "investigating" status post upon the resolution of this incident. This update is meant to provide our customers and their end users with a potential impact window. The date and time mentioned in the message above indicates when the status post was requested by our Acute Incident Response team.
We are investigating elevated errors to our Real-time Log Streaming service.
Our engineers have identified the contributing factor and are applying a fix to our Real-time Log Streaming service.
Engineering has also confirmed that this is only impacting our Compute service and Log Tailing within our Observability service.
All other locations and services are unaffected.
Engineering has deployed a fix and have confirmed a gradual recovery to our Real-time Log Streaming service. We will continue to monitor until we’ve confirmed that the customer experience has been fully restored.
Network availability and all other services were unaffected by this incident.
Engineering has confirmed that Real-time Log Streaming service has been fully restored. Customers on our Compute service and Log Tailing within our Observability service may have experienced partial data loss from 21:00 UTC on the 18th of September 2024 to 13:19 UTC on the 20th of September 2024.
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
To offer feedback on our status page, click "Give Feedback"
We are investigating elevated errors to our Real-time Log Streaming services.
Our engineers have identified the contributing factor and are applying a fix to our Real-time Log Streaming services.
All other services are unaffected.
Engineering has confirmed the impact to Real-time Log Streaming services has been mitigated.
Engineering has confirmed that Real-time Log Streaming services has been fully restored. Customers may have experienced logs being discarded or missing from 3:10 to 5:55 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
We are investigating elevated errors to our Real-time Log Streaming service.
Our engineers have identified the contributing factor and are applying a fix to our Real-time Log Streaming service. During this time, customers may experience the log endpoint error status not being reported in the UI. Log delivery and changes to logging configurations are not impacted at this time.
Our engineers have identified the contributing factor and are continuing to apply the mitigation strategy to our Real-time Log Streaming service.
Engineering has deployed a fix and have confirmed a gradual recovery to our Real-time Log Streaming service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
Engineering has confirmed that Real-time Logging services have been fully restored.
Customers may have experienced a log endpoint error code in their UI from the 7th of August 2024 at 19:16 UTC to the 8th of August 2024 at 01:46 UTC.
Log delivery and changes to logging configurations were not impacted by this issue.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
We're currently investigating performance issues with our Streaming Logs service.
All other services are unaffected.
Our engineers have identified the contributing factor and are applying a fix to our Real-time Log Streaming service.
Engineering has deployed a fix and have confirmed a gradual recovery to Real-time Log Streaming service. We will continue to monitor until we’ve confirmed that customer experience has been fully restored.
Engineering has confirmed that our Real-time Log Streaming service has been fully restored. Customers who have a logging format of classic, Loggly, or Logplex may have experienced malformed logs from the 11th of April at 18:02 to the 7th of May at 03:23 UTC.
This incident is resolved.
Fastly Engineering detected a performance impact event affecting Streaming Logs in various POPs throughout our network. Customers may have experienced a delay or discarded log messages from 16:19 to 16:38 UTC.
This incident is resolved.
We have identified the cause of elevated errors in our Streaming Logs service and are deploying a fix.
Our network availability and all other services are unaffected by this incident
A fix has been implemented and we are monitoring the results.
Engineering has confirmed that the degraded performance for streaming log services has been fully restored. Customers may have experienced varying degrees of log loss or delays in log delivery from 20:50 UTC to 21:50 UTC as a result of this incident.
This incident has been resolved.