Sāo Paulo (CGH)
Fastly will be expanding Sāo Paulo (CGH) into a Metro POP. End-users may observe connection resets as traffic is migrated onto new hardware.
As part of this expansion, customers utilizing shielding in the neighboring Sāo Paulo (CGH) will be migrated to the new Metro POP. Once this maintenance window closes, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf after 14 days.
When this change is applied, customers may observe additional origin traffic as new cache nodes retrieve content from origin.
Action for Fastly Customers:
- Please verify that all origins allow the full range of Fastly IP addresses (https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges), as this list is updated periodically. Failure to verify origin access lists will result in origin connection disruption.
- Customers with any questions or concerns should contact their dedicated technical account team or Fastly’s Support team at (support@fastly.com).
For more information on Metro POPs: https://developer.fastly.com/learning/concepts/pop/#metro-pops
Fastly will be migrating customers shielding in Sāo Paulo (CGH) to Sāo Paulo (GRU).
As part of this expansion, customers utilizing shielding in the neighboring Edge Cloud Platform will be migrated to the new Metro POP. Once this maintenance window closes, customers can either apply a new config version at a time of their choosing, or their shielding configuration will be updated on their behalf after July 9th, 2023.
When this change is applied, customers may observe additional origin traffic as cache nodes retrieve content from origin.
Action for Fastly Customers:
- Please be sure to check that your origin access lists allow the full range of Fastly IP addresses: https://docs.fastly.com/en/guides/accessing-fastlys-ip-ranges. Failure to verify origin access lists will result in origin connection disruption.
- Access the Fastly App and modify your service's shield: https://docs.fastly.com/en/guides/shielding#enabling-shielding.
- Customers with any questions or concerns should contact their dedicated technical account team or Fastly’s Support team at (support@fastly.com).
The scheduled maintenance has been completed.
We're investigating elevated errors in South America.
All other locations and services are unaffected
Fastly Engineering has observed elevated errors across multiple Points of Presence (POPs) in the region of South America.
This has been identified as an issue with a third party service provider unrelated to Fastly's Edge Cloud Platform, and a fix is being implemented.
All other locations and services are unaffected.
Traffic in Lima(LIM) has been temporarily rerouted.
All other locations and services are unaffected.
Fastly Engineering has applied our standard acute incident response practices and restored our LIM POP.
Customer services have returned to pre-incident performance levels.
We will continue to monitor the third party service provider issue for recovery. All locations and other services remain unaffected.
This incident has been resolved.
We're investigating elevated errors in Sāo Paulo (CGH).
All other locations and services are unaffected
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
This incident has been resolved.
We're currently investigating potential impact to performance with our CDN services.
A fix has been implemented and we are monitoring the results.
Fastly is aware of an expected critical vulnerability the OpenSSL project is expected to disclose in the near future. We are studying the currently available information surrounding this vulnerability and do not currently believe that Fastly is vulnerable. We will continue to monitor as additional information is released and will provide our customers with more information as available.
Fastly has reviewed the initial notification from OpenSSL regarding CVE-2022-3786 and CVE-2022-3602. We have analyzed the versions of OpenSSL in use at Fastly, and verified that we do not use OpenSSL 3.x. Fastly and customer usage of Fastly services are not vulnerable to CVE-2022-3786 or CVE-2022-3602.
We're currently investigating potential impact to performance with our CDN services.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.