Customer Services

Fastly Customer Services General Updates
 
01 December 2026, 09:00 UTC
[upcoming]

On December 1, 2026, at 09:00 UTC, our geolocation data vendor will be releasing an update. This update will result in US metro_code values changing.

What’s changing?

Customers who use client.geo.metro_code in Varnish Configuration Language (VCL) or metro_code in the Compute Software Development Kits (SDKs) will see three-digit Designated Market Area (DMA) codes become five-digit Census Core Based Statistical Area (CBSA) codes. Locations with no CBSA match will return a value of 0.

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

Customers who have hard-coded logic based on metro code values should revise that logic to use the new CBSA codes, and make sure their systems can handle five-digit US metro_code values and a value of 0 where no CBSA match exists. Customers should also review any workflows that rely on DMA-based groupings. We don't recommend building load-bearing logic on metro_code values.

To learn more about CBSA codes, please read FIPS Metropolitan Area (CBSA) Codes and United States Census Bureau.

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 Fastly Control Panel API & Configuration Management Fastly Web Pages API Services www.fastlystatus.com Configuration Management Services
 
05 November 2026, 18:43 UTC

Fastly Engineers detected a performance impacting event affecting the API & Configuration Management, www.fastlystatus.com data center.

All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.

Fastly Customer Services Fastly Web Pages https://www.fastly.com/
 
02 November 2026, 15:13 UTC

We're currently investigating performance issues with https://www.fastly.com/. Customers may be experiencing intermittent slow page loads on our homepage. Our engineers are investigating, w e will follow up when we know more.

All edge cloud products and services are unaffected.

 
02 November 2026, 22:29 UTC

Our engineers believe they have identified contributing factor causing intermittent slow page loads on https://www.fastly.com/.

We are now developing a fix, and will post a new update once it has been fully implemented and we see signs of recovery.

All other products and services are unaffected by this incident.

Fastly Customer Services General Updates
 
21 October 2026, 19:26 UTC
[in progress]

A security disclosure regarding php2shell vulnerabilities (CVE-2026-109618 and CVE-2026-109619) was published on October 21, 2026. In addition to implementing certain mitigations, we published a blog post about this disclosure for all customers. The post explains how we responded and shares steps you can take to protect your services. Additionally, we have published a second deep dive blog post to help you navigate and implement your own fixes.

What happened?

A set of critical vulnerabilities affecting all maintained PHP versions (php2shell) was disclosed, involving how the PHP engine handles fatal errors like memory exhaustion, timeouts, and dropped connections. To help protect customer environments, Fastly’s Security Research team, in collaboration with OpenAI and community partners, has developed a Virtual Patch for CVE-2026-109618 and CVE-2026-109619. To learn more about this vulnerability and our proactive protections, please read the blog posts linked in the reference section below.

What you can do

We strongly advise taking the following recommended actions:

  • Apply Virtual Patching: Fastly Next-Gen WAF customers are strongly encouraged to apply the Virtual Patch for CVE-2026-109618 and CVE-2026-109619 across all vulnerable Edge and on-prem services. Opting in ensures you automatically receive updates as the rule is refined.

  • Audit Application Servers: Identify all application servers running mod_php or php-fpm and treat all PHP applications as potentially vulnerable.

  • Patch PHP Upstream: Apply official upstream patches. Patches are available in PHP versions 8.5.12, 8.4.27, 8.3.36, and 8.2.35 . For PHP 7.4, 8.0, and 8.1, or older versions, verify available patches with your Linux/package distributor.


Fastly is actively monitoring for exploitation and new variants. Please stay aware of any further updates as this situation develops.   

Customers with any questions, requiring emergency WAF onboarding, or needing support may engage with our Support team through support@fastly.com or by contacting your designated account management team members.


Reference:

Fastly Customer Services General Updates
 
22 September 2026, 15:02 UTC

Fastly is announcing General Availability on September 29, 2026 of Controlled Support Access (CSA). CSA gives customers more control and visibility over Fastly employee access by requiring customer approval for Fastly write/enforcing access. Approved access is time-bound, auditable, and customer-revocable. Read-only troubleshooting remains available so Fastly can continue diagnosing issues efficiently.

CSA is default OFF at General Availability (GA). Customers who want to enable CSA can opt in directly from the Fastly Control Panel. 

What’s Changing?

To learn more, see the Controlled support access documentation.

The documentation explains standard CSA requests/grants, customer approval and revocation, audit visibility, and Breakglass emergency access.

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

CSA is disabled by default at GA, meaning no action is required unless you wish to use it. Superusers can enable the feature directly within the Fastly Control Panel.

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 Support Systems https://support.fastly.com Support Ticketing System Chatbot Feature New Support Case
 
16 September 2026, 07:50 UTC

We are investigating an issue caused by a third-party service provider, which is affecting availability of the Support Portal, including the ability to view or create support tickets.

Our engineers are actively monitoring the situation and working with the provider to diagnose and resolve the issue.

We will provide another update as more information becomes available or within the next hour.

 
16 September 2026, 10:35 UTC

Our engineers are continuing to investigate the issue impacting the Support Portal, including the ability to view or create support tickets. This has been caused by a third-party service provider outage.

We have not yet confirmed the contributing factor has been fully resolved. We'll provide another update as soon as we have more information.

 
16 September 2026, 13:00 UTC

A fix has been validated by our third-party service provider and is currently being rolled out across all impacted systems. We will post a new update once it has been fully implemented and we see signs of recovery.

All other products and services remain unaffected by this incident.

 
16 September 2026, 17:13 UTC

The third party provider issue affecting availability of the Support Portal has been fully resolved.

All Fastly Customer Support services systems have been restored and are operating normally. Ticket processing and standard communication channels are fully functional.

We apologize for the inconvenience and appreciate your patience during this interruption to our support channels.

10 September 2026, 00:00 UTC
Fastly Customer Services Support Systems https://support.fastly.com New Support Case
 
10 September 2026, 00:00 UTC

Fastly will perform maintenance on the Fastly Support Portal and artificial intelligence (AI) chatbot on September 10, 2026 from 12:00 AM to 4:00 AM UTC (240 minutes).

What’s changing?

Fastly is updating the infrastructure behind the Fastly Support Portal and AI chatbot by migrating from our ticketing provider's default content delivery network (CDN) to our own in-house Fastly CDN and Fastly Next-Gen WAF (NGWAF) layer.

This change improves system resilience and adds protection against automated bot traffic and distributed denial of service (DDoS) threats.

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

Nothing. Fastly is handling every action for this planned maintenance. During the 240-minute window, the AI chatbot and the Fastly Support Portal will be temporarily unavailable. 

Case submission via support@fastly.com and all dedicated enterprise Slack channels will remain unaffected and fully operational during this maintenance.

 
10 September 2026, 04:00 UTC
This scheduled maintenance has been completed.
Fastly Customer Services General Updates
 
02 September 2026, 17:05 UTC

Fastly is updating how a subset of client disconnects are reported for Delivery (Varnish) Services. Previously, these disconnects returned a 503 (Service Unavailable) response code. As part of a fix for an issue affecting our ERROR-WAIT handling, we changed this behavior so a subset of these disconnects now return a 499 (Client Closed Request) and will have an ERROR-DISCONNECT state.

This change will be rolling out gradually over the next few weeks. 

What you may notice:

You may see an increase in 499 response codes and a corresponding decrease in 503 response codes for waitlist disconnects in your logs and dashboards. This is expected and does not indicate a new issue with your service.

What you need to do:

If you have monitoring, alerting, or automation that treats 503s and 499s differently, review your configuration to confirm it accounts for this change. If you have questions, contact your Fastly support team.


 
15 September 2026, 17:00 UTC

This event has been resolved.



24 August 2026, 16:00 UTC
Fastly Customer Services Fastly Web Pages www.fastlystatus.com
 
24 August 2026, 16:00 UTC

On August 24, 2026 at 16:00 UTC, we'll perform scheduled maintenance on our Status Page to update the design of our header, footer, and other formatting options. 

The maintenance is expected to take about 2 hours, with no downtime. It won't affect your notifications or preferences, and no action is needed on your part.

 
24 August 2026, 18:00 UTC

The scheduled maintenance has been completed.


Fastly Customer Services Support Systems Support Ticketing System
 
18 June 2026, 16:48 UTC

Our engineers have been informed that our Customer Relationship Management (CRM) provider is currently experiencing an incident. As a result, you may experience slightly delayed responses from our Support team while we implement an internal workaround and monitor this provider's incident updates.

All other Fastly services remain fully operational. Our network and security products continue to deliver without disruption.

We will provide an update if the situation changes.

 
18 June 2026, 18:49 UTC

We have an update regarding the ongoing Informational affecting Support Ticketing System.

Our provider has reported that a contributing factor has been identified and they are working on a fix.

As a reminder, Fastly's core edge network and security services remain unaffected. Please continue to email support@fastly.com for any assistance while our standard support and CRM channels remain impacted.

Updated on 18 June 2026 at 18:49 UTC