Real-time Analytics

Fastly Network Services Compute Observability Domain Management Alerts Fastly Compute Customer Services Edge Observer Domain Inspector Fastly Application Historical Stats Web Delivery Log Explorer & Insights Origin Inspector Real-time Log Streaming Third Party Service Provider Real-time Analytics API & Configuration Management Image Optimization TLS Provisioning Fastly Web Pages Notification Center KV Store Support Systems Billing System API Services Configuration Management Services Support Chat System https://docs.fastly.com/ https://developer.fastly.com
 
12 June 2025, 17:55 UTC

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. 

 
12 June 2025, 19:08 UTC

As our engineers determine the scope of impact our Customer Escalation Management team will be updating the impacted components on this status post. 

 
12 June 2025, 19:19 UTC

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:

Google Cloud Status Page

 
12 June 2025, 19:35 UTC

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.

 
12 June 2025, 20:17 UTC

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.



 
13 June 2025, 16:30 UTC

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.

07 October 2024, 23:12 UTC
Fastly Observability Fastly Application Historical Stats Real-time Analytics API & Configuration Management Notification Center API Services Configuration Management Services
 
07 October 2024, 23:12 UTC

We are investigating elevated errors to our Fastly Application, Historical Stats, and Real-time Analytics services.

All other products and services are unaffected by this incident.


 
08 October 2024, 00:05 UTC

Our engineers are continuing to investigate elevated errors to our Fastly Application, Historical Stats, Real-time Analytics services.

 
08 October 2024, 00:54 UTC

Our engineers have identified the contributing factor and are applying a fix to our Fastly Application, Historical Stats, Real-time Analytics services.

All other locations and services are unaffected.

 
08 October 2024, 01:04 UTC

Engineering has confirmed the impact to our Fastly Application, Historical Stats, Real-time Analytics services have been mitigated.

 
08 October 2024, 01:18 UTC

Engineering has confirmed that our Fastly Application, Historical Stats, Real-time Analytics services have been fully restored. Customers may have experienced elevated errors and issues when attempting access these services from 23:12 on the 7th of October to 00:55 UTC on the 8th of October .

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

Status Post, Created Date/Time: 2024-10-07 23:26:03 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.


Platform Observability North America Historical Stats Real-time Analytics Columbus (CMH)
 
29 December 2023, 03:00 UTC

We're currently investigating performance issues with our Real Time Analytics and Historical Stats services at our Columbus (CMH) Point of Presence (POP).

All other services are unaffected.

 
29 December 2023, 04:03 UTC

Our engineers have identified the contributing factor and are applying a fix to Real Time Analytics and Historical Stats services at our Columbus (CMH) Point of Presence (POP).

All other locations and services are unaffected.

 
29 December 2023, 04:28 UTC

Engineering has confirmed the impact to Real Time Analytics and Historical Stats services at our Columbus (CMH) Point of Presence (POP) has been mitigated.

 
29 December 2023, 04:40 UTC

Engineering has confirmed that Real Time Analytics and Historical Stats services at our Columbus (CMH) Point of Presence (POP) has been fully restored. Customers may have experienced a delay or dropped observability product data from. 01:15 to 04:05 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

Platform Observability Europe Historical Stats Real-time Analytics Lisbon (LIS)
 
03 December 2023, 17:53 UTC

We're currently investigating performance issues with our Real Time Analytics and Historical Stats services only in our Lisbon (LIS) data center.

All other services and data centers are unaffected.

 
03 December 2023, 22:51 UTC

This event has been resolved.

09 November 2022, 15:03 UTC
Observability Real-time Analytics
 
09 November 2022, 15:03 UTC

We're currently investigating performance issues with our Real Time Analytics service. All other services are unaffected.

 
09 November 2022, 15:18 UTC

A fix has been implemented and we are monitoring the results.

 
09 November 2022, 18:34 UTC

This incident has been resolved.

05 November 2022, 17:20 UTC
Observability Real-time Analytics
 
05 November 2022, 17:20 UTC

Retrospective Post | Fastly Engineers detected a performance impacting event affecting the availability of our Real Time Analytics service from approximately 2022-11-05 17:20 UTC to 2022-11-05 18:40 UTC.

CDN delivery and all other data plane services were unaffected.


 
05 November 2022, 18:40 UTC

The issue has been resolved since 2022-11-05 at 18:40 UTC and we are monitoring performance closely.

Observability Historical Stats Real-time Analytics
 
02 September 2022, 03:38 UTC
We're currently investigating performance issues with our Real Time Analytics and Historical Stats services. All other services are unaffected.
 
02 September 2022, 04:13 UTC
The issue has been identified and a fix is being implemented.
 
02 September 2022, 04:30 UTC
A fix has been implemented and we are monitoring the results.
 
02 September 2022, 04:50 UTC
This incident has been resolved.
Observability Historical Stats Real-time Analytics
 
02 September 2022, 03:38 UTC


We're currently investigating performance issues with our Real Time Analytics and Historical Stats services. All other services are unaffected.

 
02 September 2022, 04:13 UTC

The issue has been identified and a fix is being implemented.

 
02 September 2022, 04:30 UTC

A fix has been implemented and we are monitoring the results.

Real-time Analytics
 
21 June 2022, 17:51 UTC
We're currently investigating performance issues with our Real Time Analytics service. All other services are unaffected.
 
21 June 2022, 18:19 UTC
A fix has been implemented and we are monitoring the results.
 
21 June 2022, 18:39 UTC
This incident has been resolved.
Historical Stats Real-time Analytics
 
27 April 2022, 23:41 UTC
We're currently investigating performance issues with our Compute@Edge Real Time Analytics and Historical Stats services. All other services are unaffected.
 
28 April 2022, 00:14 UTC
The issue has been identified and a fix is being implemented.
 
28 April 2022, 08:37 UTC
This incident has been resolved.