Fastly incident

Elevated Errors for TLS Provisioning

Resolved after 1 hour 9 minutes, affecting Domain Management and TLS Provisioning and 1 more, on May 13, 2026.

resolved May 13, 2026, 07:15 AM UTC

Engineering has confirmed that our TLS Provisioning service has been fully restored. Customers may have experienced errors and timeouts when using the TLS provisioning API from 06:06 to 07:12 UTC. This incident is resolved. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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. Status Post, Created Date/Time: 2026-05-13 06:55:15 UTC

Started
May 13, 2026, 06:06 AM UTC
Resolved
May 13, 2026, 07:15 AM UTC
Duration
1h 9m
Detected by Pingoru
May 13, 2026, 06:06 AM UTC

Affected components

Domain ManagementTLS ProvisioningNetwork ServicesDomain ManagementTLS Provisioning

Update timeline

  1. investigating May 13, 2026, 06:54 AM UTC

    We are investigating elevated errors to our TLS Provisioning feature.

  2. investigating May 13, 2026, 07:01 AM UTC

    Our engineers believe they have identified contributing factor causing the issue impacting the TLS Provisioning 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.

  3. monitoring May 13, 2026, 07:12 AM UTC

    Engineering has confirmed the impact to TLS Provisioning service has been mitigated.

  4. resolved May 13, 2026, 07:15 AM UTC

    Engineering has confirmed that our TLS Provisioning service has been fully restored. Customers may have experienced errors and timeouts when using the TLS provisioning API from 06:06 to 07:12 UTC. This incident is resolved. Affected customers may have experienced impact to varying degrees and to a shorter duration than as set forth above. 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. Status Post, Created Date/Time: 2026-05-13 06:55:15 UTC

Your product runs on more than Fastly

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →