On the 9th of December 2024 at 21:00 UTC, Fastly will release a change in the way dictionary items are ordered for VCL services. Previously, the dictionary items were not sorted alphabetically. The change will now explicitly sort by items key alphabetically. Our Engineers have identified that these changes may show a difference in the User Interface (UI) between versions whereas the actual content is unchanged.

All options will be available and are not impacted by this change. 

If you have any questions about this change or require further assistance, please contact Fastly Support at https://support.fastly.com.

We are investigating elevated errors to our API & Configuration Management service.

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our API & Configuration Management service.

All other locations and services are unaffected.

Engineering has confirmed the impact to API & Configuration Management service has been mitigated.

Engineering has confirmed that API & Configuration Management service has been fully restored. Customers may have experienced 4xx errors from 16:14 to 17:26 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

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

Status Post, Created Date/Time: 2024-11-26 16:35:47 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 Engineers detected a performance impacting event affecting our Fastly Application service.

The issue has been resolved and we are monitoring performance closely.

We are investigating elevated errors to our Fastly Application service.

All other products and services are unaffected by this incident.

Our engineers are continuing to investigate elevated errors to our Fastly Application service.

Our engineers have identified the contributing factor and are applying a fix to our Fastly Application service.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Fastly Application service has been mitigated.

Engineering has confirmed that our Fastly Application service has been fully restored. Customers may have experienced elevated errors and latency when attempting to access the Fastly Application from 19:52 to 20:56 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

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

Status Post, Created Date/Time: 2024-10-29 20:19:39 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.

Reminder 2 of 2, previously communicated on: Status Post - 376874 & Status Post -376877

Our engineers will deprecate our Billing API v.2 on the 14th of November 2024. This endpoint will be deprecated and replaced with an optimized Billing API v.3. 

Fastly Super-users who have used v.2 throughout this year, 2024, have received an email in an effort to proactively notify our customers of the upcoming deprecation.

• Subject Line: [Action Required] Billing API V2 deprecation and V3 Release Notification

Customers who would like to begin using Billing API v.3 prior to the deprecation date shared above, may do so immediately. 

After the 14th of November 2024, billing API V2 will no longer be available. 

Customers with any questions or concerns may engage with our Support team through our Support Portal or by contacting your designated account management team members.

We are investigating elevated errors to our Fastly Application.

All other products and services are unaffected by this incident.

Our engineers have identified the contributing factor and are applying a fix to our Fastly Application.

All other locations and services are unaffected.

Engineering has confirmed the impact to Fastly Application has been mitigated.

Engineering has confirmed that our Fastly Application has been fully restored. Customers may have experienced 404 errors within the user interface, errors when attempting to login to manage.fastly.com including with single sign-on (SSO), and delayed VCL deployments from 19:58 to 20:10 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2024-10-22 20:20:48 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 will be performing maintenance on the Fastly Application (https://manage.fastly.com) on Tuesday, the 22nd of October 2024 from 18:00 to 19:00 UTC (1 hour).

We are not anticipating any customer impact as a result of this maintenance activity.

Should you experience any impact while interacting with the Fastly Application or its' services during this maintenance window, please reach out to our Support team at https://support.fastly.com. Our network services, stats aggregation, and all other services will be unaffected by this maintenance.

The scheduled maintenance has been completed.

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

We are investigating elevated errors to our Fastly Application, Historical Stats, and Real-time Analytics services.

All other products and services are unaffected by this incident.

Our engineers are continuing to investigate elevated errors to our Fastly Application, Historical Stats, Real-time Analytics services.

Our engineers have identified the contributing factor and are applying a fix to our Fastly Application, Historical Stats, Real-time Analytics services.

All other locations and services are unaffected.

Engineering has confirmed the impact to our Fastly Application, Historical Stats, Real-time Analytics services have been mitigated.

Engineering has confirmed that our Fastly Application, Historical Stats, Real-time Analytics services have been fully restored. Customers may have experienced elevated errors and issues when attempting access these services from 23:12 on the 7th of October to 00:55 UTC on the 8th of October .

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

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

Status Post, Created Date/Time: 2024-10-07 23:26:03 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.

We are investigating elevated errors during login to our Fastly Application affecting new user account creations. 

Current user accounts along with all other products and services are unaffected by this incident.

Our engineers are continuing to investigate elevated errors during login to our Fastly Application. 

Our engineers have identified the contributing factor and are applying a fix to our Fastly Application. 

All other locations and services are unaffected.

Our engineers have identified an additional contributing factor and are applying an adjusted mitigation strategy to our Fastly Application.

All other locations and services are unaffected.

Engineering has confirmed the impact to Fastly Application service has been mitigated.

Engineering has confirmed that Fastly Application service has been fully restored. Customers with new user account creations may have experienced the inability to login to the new account from 21:00 UTC on the 7th of October 2024 to 12:38 UTC on the 8th of October 2024 UTC.

This incident is resolved.

Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above.

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

Status Post, Created Date/Time: 2024-10-08 08:01:45 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.

Reminder 1 of 2, previously communicated on: Status Post - 376874

Our engineers will deprecate our Billing API v.2 on the 14th of November 2024. This endpoint will be deprecated and replaced with an optimized Billing API v.3. 

Fastly Super-users who have used v.2 throughout this year, 2024, have received an email in an effort to proactively notify our customers of the upcoming deprecation.

• Subject Line: [Action Required] Billing API V2 deprecation and V3 Release Notification

Customers who would like to begin using Billing API v.3 prior to the deprecation date shared above, may do so immediately. 

After the 14th of November 2024, billing API V2 will no longer be available. We will email and post a final reminder notifications 30 days from today’s notification for additional awareness, schedule is set for:

• 28th of October 2024
  

Customers with any questions or concerns may engage with our Support team through our Support Portal or by contacting your designated account management team members.