Compute
We are investigating elevated errors from our API & Configuration Management services.
Fastly engineers have identified the cause of this disruption to our Fastly API & Configuration Management services.
Our network availability is not affected by this incident.
Engineering has confirmed the impact to API & Configuration Management has been mitigated.
Engineering has confirmed that our API and Configuration Management services and access to our Fastly Application has been fully restored. Customers may have experienced elevated errors when attempting to access manage.fastly.com and failed Configuration propagation and API services during this incident from 14:08 to 15:37 UTC.
Our network availability and all other services were unaffected by this incident.
This incident is resolved.
We are investigating elevated errors to our Fastly API.
Update: We have updated this status post to reflect the actual start time of 18:02 UTC for this incident.
Our engineers have identified the contributing factor and are applying a fix to Fastly API services.
Customers may experience increased periods of latency in accessing our secret store for NGWAF console services. In addition, manage.fastly.com Website and API authentication may timeout as a result of this incident.
Our network availability and all other services are unaffected by this incident.
Engineering has confirmed the impact to Fastly API services has been mitigated.
Engineering has confirmed that Fastly API services has been fully restored. Customers would have experienced intermittent periods of latency in accessing our secret store for NGWAF console services.
In addition, our manage.fastly.com Website and API authentication may have resulted in varying degrees of timeout and/or increased latency as a result of this incident from 18:02 to 18:33 UTC. (~31 minutes)
This incident is resolved.
Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.
We are investigating elevated errors to our Fastly Application and the Fastly API.
Update: Our retrospective investigation has identified the initial onset of errors to have started at approximately 15:40 UTC.
Our engineers have identified the contributing factor and are applying a fix to Fastly API, Fastly Application.
Engineering has confirmed the impact to Fastly API, Fastly Application has been mitigated.
Engineering has confirmed that Fastly API, Fastly Application has been fully restored. Customers may have experienced elevated errors when attempting to access manage.fastly.com and failed API services during this incident from 15:40 to 16:01 UTC.
Our network availability and all other services were unaffected by this incident.
This incident is resolved.
We are investigating elevated errors to our KV Store within our Compute Services.
Our engineers have identified the contributing factor and are applying a fix to Compute Services.
Engineering has confirmed the impact to Compute Services has been mitigated.
Engineering has confirmed that the KV Store within our Compute Services has been fully restored. Customers may have experienced 5xx errors accessing the KV Store from 20:05 to 20:33 UTC.
This incident is resolved.
What's Changing?
We will be conducting planned maintenance on the Fastly Control Panel to modernize it for current web-standards and to embrace its own latest product-offerings. The manage.fastly.com site will be moving from from VCL to Compute and will be allowing HTTP-3, TLS v1.3 with 0-RTT. All these changes should result in a more performant and secure web experience.
Our remaining maintenance activity will start on the 1st of April 2024 and our estimated duration is ~5 minutes.
When this maintenance is completed, access to the Fastly Control Panel will be stabilized, have better security features, and will be more performant.
No data will be lost and we do not anticipate any impact to API services as a result of this maintenance. There are no actions required by our customers.
What's next, what do I need to do to prepare?
If you are using browsers older than Chrome 66 or Firefox v60, you'll need to upgrade your browsers. Current Safari and Edge browsers support these standards as well.
The scheduled maintenance has been completed.
Fastly is extending our launch of a unified login experience across Fastly and Signal Sciences consoles. This launch makes it simpler and easier for you to access Fastly products and services using a single set of login credentials. Continuing from today, 28th of March 2024 to the 30th of April 2024, we will gradually rollout our new web interface as part of the upgraded login experience. A summary of the main changes appears below.
What's changing?
Single set of credentials to login to Fastly and Signal Sciences console. Simplified login will allow you to use a single set of login credentials to access all products and features across Fastly's suite of offerings. If you have both Fastly and Signal Sciences accounts that use the same email address and use password and 2FA for authentication, you can use Fastly credentials to log in to both Fastly and Signal Science console.
Log in once and access both accounts. You have to sign-in only once and can switch between Fastly or Signal Sciences console seamlessly without having to log in again if you use the same email address.
Password and 2FA management in one place. You'll be able to change passwords and set up two-factor authentication directly in the Fastly console for both Fastly and Signal Sciences accounts.
Service Provider initiated SSO is now supported. You can log in directly at either Fastly or Signal Sciences console login page using SSO without going to your IdP page.
Password reset got simpler. You can reset your passwords without having to create a temporary password.
Account linking will no longer be required. Customers with both Fastly and Signal Sciences accounts will no longer need to manually link those accounts. Already have linked accounts? You won't need to do anything and can start using your Fastly credentials immediately.
New passwords will be required to conform to NIST guidelines. The complexity for new and changed passwords will be required to conform to digital identity guidelines from the National Institute of Standards and Technology (specifically, the NIST800-63B guidelines). Existing passwords won't be affected until you choose to update them.
Session timeouts will be standardized and more secure. We added additional measures to increase your security posture on the Fastly platform. You will be logged out after 30 minutes of inactivity. Session timeouts will also have a default maximum of 12 hours for any organization that hasn't set up single sign-on.
What's next? What do I have to do?
That's it!. The transition will be seamless and you are not required to take additional steps. You will see a new login experience when we enable this feature for you.
Please refer to documentation for additional information.
Still have questions? Feel free to contact your account manager or customer support for additional details.
We are currently investigating performance issues affecting the availability of manage.fastly.com. CDN delivery, stats aggregation, and all other data plane services are unaffected.
Our engineers have identified the contributing factor and are applying a fix to Fastly Application.
Engineering has confirmed the impact to Fastly Application has been mitigated.
Engineering has confirmed that Fastly Application has been fully restored. Customers may have experienced issues with login to the Fastly App from 20:14 to 20:36 UTC.
This incident is resolved.
Fastly engineers are currently investigating into intermittent WebSocket Connections. Customers attempting to connect to WebSocket services may experience intermittent periods of elevated errors.
All other Fastly products and services are unaffected.
Our engineers have identified the issue and are applying a fix to WebSocket Connection services.
All other Fastly products and services are unaffected.
Engineering has deployed a fix and have confirmed a gradual recovery for WebSocket Connection services. We will continue to monitor until we’ve confirmed that the service has been fully restored.
All other Fastly products and services remain unaffected by this incident.
Engineering has confirmed that WebSocket Connection services has been fully restored. Customers may have experienced intermittent periods of elevated errors from the 6th of March 10:00 to the 9th of March 04:49 UTC.
This incident is resolved.
We are investigating elevated errors to our Geolocation Data.
Engineering has confirmed the impact to Geolocation Data has been mitigated.
Our engineers have confirmed that the impact to our Geolocation services has been restored to pre-incident levels. There will be a scheduled deployment to further reduce the risk of future impact, and we will continue to monitor the service with a high priority until this updated configuration has been deployed.
Once our deployment has been confirmed, we will resolve this status post.
Engineering has confirmed that Geolocation Data has been fully restored. Customers may have experienced failing Geolocation lookups in Compute from 11:00 to 20:00 UTC.
This incident is resolved.
We are investigating elevated errors to our Fastly Application services.
Our network availability and all other services are unaffected by this incident.
Our engineers have identified the contributing factor and are applying a fix to Fastly Application services.
All other services are unaffected by this incident.
Engineering has confirmed the impact to Fastly Application services has been mitigated.
Engineering has confirmed that Fastly Application services has been fully restored. Customers may have experienced missing chart data with manage.fastly.com from the 28th of February at 22:44 to the 29th February at 08:42 UTC.
This incident is resolved. We have confirmed that there was no data lost as a result of this incident.
Our network availability and all other services were unaffected.