As part of our ongoing commitment to account security and alignment with industry standard best practices, we’re strengthening our password policy across our Fastly Application and Next-Gen WAF (NGWAF) Console product offerings.
Fastly will be performing maintenance on the Fastly Control Panel on the 19th of May 2025 from 14:00 to 14:30 UTC (~30 minute duration).
What’s Changing?
Beginning on the 19th of May 2025, any user who creates a new account or resets their password in the Fastly Application will be required to choose a password that is at least 12 characters long including letters, numbers, and special characters. This change will affect the Sign Up, Create Account, and Reset Password experiences on our website.
This change will help maintain account security and provides significant benefits to our users, including:
- Longer passwords are more secure and significantly reduce the risk of brute‑force or guessing attacks
- A minimum length of 12 characters meets the current recommended industry security standard
- Safeguards your data against unauthorized access and protects user accounts
This new password requirement condition will be displayed in real time as a password is entered into any password field on the website. Users attempting to submit a password with fewer than 12 characters, including Application Programming Interface (API) or Terraform requests to Create or Reset a password, will fail.
This change will not impact existing account passwords and will only apply to new account passwords or when a password reset is requested.
What’s next? What do I have to do?
If you have an integration using our Fastly API or Terraform modules to automate account creation or password resets, you’ll need to update your code and configurations to enforce the new 12 character minimum requirement.
Remember that all passwords associated with your Fastly account are case sensitive.
Your account will continue to operate as expected and all other products and services remain unaffected by this maintenance.
Contact Information
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 will be adding capacity at our Stockholm (BMA) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on the 15th of May 2025 at 23:00 UTC.
Our estimated duration is 3h.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team (support@fastly.com).
Fastly will be adding capacity at our Bogota (BOG) POP. End-users may observe connection resets as traffic is migrated onto new hardware starting on 09 May 2025 at 07:00 UTC.
Our estimated duration is 8h.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin. Please verify that your origin access lists allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges). Customers with any questions or concerns should contact Fastly’s Support team at https://support.fastly.com.
Fastly will be performing scheduled maintenance on our Osaka (ITM) data center from 07 May 2025, 16:00 UTC - 08 May 2025 00:00 UTC.
During this time frame traffic will be redirected to neighboring POPs in the region.
The scheduled maintenance has been completed.
To offer feedback on our status page, click
"
Give Feedback
"
Fastly Engineers detected a performance impacting event affecting the Manila (MNL) data center.
All other data centers and services were unaffected. The issue has been resolved and we are monitoring performance closely.
Fastly will be performing scheduled maintenance on our Osaka (ITM) data center from 06 May 2025, 16:00 UTC - 07 May 2025 00:00 UTC.
During this time frame traffic will be redirected to neighboring POPs in the region.
The scheduled maintenance has been completed.
To offer feedback on our status page, click
"
Give Feedback
"
Fastly Engineers have confirmed a performance impacting event that affected the API Services. Customers may have experienced a 410 error code with a plan to apply changes to services in Terraform from 14:17 to 16:22 UTC.
All other services were unaffected. The issue has been resolved and we are monitoring performance closely.
Fastly will be performing maintenance on our platform system on the 6th of May 2025 from 00:00 to 01:00 UTC (~60m duration).
What’s Changing?
We're making improvements to make the Fastly platform even more resilient, secure, and reliable.
- We are introducing general security updates to our authentication infrastructure
- We are improving system availability so that future maintenance of the Authentication Platform can be performed without impacting availability.
What’s next? What do I have to do?
Nothing. All actions taken during this planned maintenance belong to Fastly. During this time, customers may experience:
- Temporary inability to log in to the Fastly App (manage.fastly.com)
- Temporary inability to log in to the Signal Science (SigSci) console (dashboard.signalsciences.net)
- Possible navigation issues in the apps due to token refresh interruptions.
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.
The scheduled maintenance has been completed.
To offer feedback on our status page, click
"
Give Feedback
"
Traffic in Ghana (ACC) has been temporarily rerouted.
All other locations and services are unaffected.
On the 3rd of May 2025 from 09:00 to 12:00 UTC, a third-party service provider in Vancouver performed maintenance on their services. As a result, Fastly temporarily redirected customer traffic typically served from our Vancouver (YVR) Point of Presence (POP) from neighboring regions.
During this temporary reroute, customers may have experienced intermittent errors and increased latency.
The traffic engineering implemented during the maintenance was reversed once the service provider completed their work, and our Network engineers confirmed that the YVR POP was no longer affected.
Our ability to deliver all other products and services was not affected by this event.