Elevated Errors for Support Ticketing System

Incident
16 January 2026, 16:11 UTC

Elevated Errors for Support Ticketing System

Status: closed
Start: 10 January 2026, 00:38 UTC
End: 16 January 2026, 16:11 UTC
Duration: 6 days 15 hours 33 minutes
Affected Components:
Fastly Customer Services Support Systems Support Ticketing System
Investigating

10 January 2026, 00:38 UTC

10 January 2026, 00:38 UTC

We are investigating elevated errors when users attempt to access our Support Ticketing System.  This does not impact Fastly's ability to provide support our customers.

Our core delivery services and network are fully operational.

All other products and services are unaffected by this incident.

Identified

15 January 2026, 19:02 UTC

15 January 2026, 19:02 UTC

Our engineers believe they have identified contributing factor causing the issue impacting the Support Ticketing System status page component.

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.

Monitoring

15 January 2026, 19:03 UTC

15 January 2026, 19:03 UTC

Engineering has confirmed the impact to our Support Ticketing System has been mitigated.

Identified

15 January 2026, 21:29 UTC

15 January 2026, 21:29 UTC

Our engineers have identified an additional contributing factor and are developing an adjusted mitigation strategy to our Support Ticketing System.

All other locations and services are unaffected.

Resolved

16 January 2026, 16:11 UTC

16 January 2026, 16:11 UTC

Engineering has confirmed that our Support Ticketing System has been fully restored. Customers may have experienced issues logging into the Fastly Support Portal from January 10th, 2026, 00:38 to January 15th, 2026, 18:27 UTC.

This incident is resolved.

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

Status Post, Created Date/Time: 2026-01-15 19:02:00 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.