Billing System

Fastly Customer Services Billing System General Updates
 
28 August 2025, 16:00 UTC

Due to the recent implementation of a new billing system, you may experience a delay in receiving your invoice for August 2025. We are committed to prompt and accurate billing and apologize for any inconvenience this may cause. 

What’s next? What do I have to do?

Fastly's support team will contact affected customers with more details during North America business hours on Thursday, 4th of September 2025.

On the 5th of September, if you have not yet received your invoice and have not been contacted by us through the notifications center in the Fastly User Interface (UI), please email us at billing@fastly.com. We will work with you to resolve any issues.

For other questions or concerns, please contact our Support team at https://support.fastly.com or reach out to your designated account team members.

 
28 August 2025, 20:00 UTC

To offer feedback on our status page, click "Give Feedback

Fastly Customer Services Billing System General Updates
 
29 July 2025, 16:00 UTC

Due to the recent implementation of a new billing system, you may experience a delay in receiving your invoice for July 2025. We are committed to prompt and accurate billing and apologize for any inconvenience this may cause. 

What’s next? What do I have to do?

Fastly's support team will contact affected customers with more details during North America business hours on Monday, the 4th of August.

On the 5th of August, if you have not yet received your invoice and have not been contacted by us through the notifications center in the Fastly User Interface (UI), please email us at billing@fastly.com. We will work with you to resolve any issues.

For other questions or concerns, please contact our Support team at https://support.fastly.com or reach out to your designated account team members.

 
29 July 2025, 20:00 UTC

To offer feedback on our status page, click "Give Feedback

Status Post, Created Date/Time: 0001-01-01 00:00:00 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.


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 Fastly Web Pages Image Optimization TLS Provisioning Support Systems Notification Center KV Store 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.

Fastly Customer Services Billing System General Updates
 
04 June 2025, 20:14 UTC

From Tuesday, April 29th through Monday, May 5th, 2025, Fastly shared a status post about a series of updates performed to enhance the billing platform within the Fastly Control Panel.

As part of our continued commitment to ensure the accuracy of invoices billed for the month of May 2025, our billing team has extended our period of manual review and validation until Friday, June 6th 2025. As a result, some customers have and may continue to experience a delay when receiving their invoices.

What’s next? What do I have to do?

Please continue to reach out to billing@fastly.com if you receive your invoice and identify a discrepancy. We will work with you to resolve the issue.

Customers with any questions or concerns may engage with our Support team through https://support.fastly.com or by contacting your designated account management team members.

Fastly Customer Services Billing System General Updates
 
04 June 2025, 14:22 UTC

On the 31st of May 2025, the Customer Escalation Management team shared a notification to all customers of a recent billing system error that may have caused an additional invoice statement to be distributed to customer inboxes. This notification was sent using customer outreach tooling within our Fastly Application, accessible through manage.fastly.com, and our customers could read about this error within their Message Portal.

On the 3rd of June 2025, we found a bug within our outreach tooling. This bug would have caused the email to users with Superuser permissions to fail. Our engineering teams have identified the bug and email alerts to account Superusers will be restored for all future customer outreaches performed by the Customer Escalation Management team.

Out of an abundance of caution, to help ensure that customers do not action the duplicative invoice and double pay - we are sharing this message again on our status page.

Fastly Customer Services Billing System
 
21 April 2025, 12:23 UTC

From Monday, April 21 through Thursday, April 24, 2025, Fastly will be performing a series of updates to enhance the billing platform within the Fastly Control Panel. 

During this effort customers may not be able to retrieve the latest month-to-date billing information. You may contact the Fastly Support team at support@fastly.com for assistance if this error is encountered.

The ability to access your Fastly Control Panel, update configurations, and leverage our API services will not be impacted as a result of these updates.  

What’s next? What do I have to do?

Nothing. During the updates, no immediate actions are required by customers. However, certain observable impacts or changes should be noted in advance of the update implementation, these will include:

The Month-to-Date (MTD) billing page may experience temporary unavailability, potentially lasting up to 48 hours.

The ‘Pay Now’ functionality will be removed from the Invoices page and will instead be available in future invoice PDF documents.

Customers with any questions or concerns may engage with our Support team through at https://support.fastly.com or by contacting your designated account management team members.

 
24 April 2025, 22:18 UTC

This maintenance has been extended to Monday, April 28th 2025.

 
28 April 2025, 23:30 UTC

The scheduled maintenance has been completed.

To offer feedback on our status page, click " Give Feedback

Customer Services Billing System
 
13 March 2023, 17:03 UTC

With the recently announced news that Silicon Valley Bank (SVB) has been taken over by the FDIC, Fastly would like to reassure that while we do have a relationship with SVB, our financial exposure is not material. There should be no disruption to the normal operations of our services. 


We are transitioning our banking relationship from SVB to another financial institution.  Fastly has updated our payment instructions and customers will receive a message containing directions about how to process upcoming payments. 


Customers may verify this request by contacting us at support@fastly.com.  


Fastly products and all other services are unaffected. 

01 August 2022, 20:08 UTC
Customer Services Billing System
 
01 August 2022, 20:08 UTC
Fastly Billing is currently performing a series of routine checks on our billing process to ensure optimal accuracy for our August 1st billing cycle. As a result of these checks customers may experience a delay receiving their invoice. There is no impact to production services or traffic.
 
05 August 2022, 17:11 UTC
Fastly Billing has completed our routine checks. As a result of these checks, customers who did not have charges in the month of July may have received an additional email notification confirming a $0.00 balance. There are no further actions to take in response to this notification.
28 July 2022, 17:23 UTC
Billing System
 
28 July 2022, 17:23 UTC
Fastly is currently investigating an issue with the billing system, including the billing portions of the Fastly configuration application and API. Edge delivery, stats aggregation, and all other services are unaffected.
 
28 July 2022, 19:48 UTC
This incident has been resolved.
Customer Services Billing System
 
01 July 2022, 22:02 UTC
Fastly is currently investigating an issue with our billing processor impacting developer and open source accounts only. We are auditing impacted invoices and will be issuing corrections within four business days. Impacted developers and open source customers will receive an email with a Fastly Service Advisory (FSA) providing additional detail. There is no impact to production services or traffic.
 
02 July 2022, 00:01 UTC
We have identified the impacted developer and open source customers, and a fix is being implemented. Corrections will begin in the next 24 hours.