Fastly incident

Third party service provider incident resulting possible delays for our support services

Notice Resolved View vendor source →

Fastly experienced a notice incident on June 18, 2026 affecting Customer Services and Support Systems and 1 more component, lasting 3h 5m. The incident has been resolved; the full update timeline is below.

Started
Jun 18, 2026, 04:48 PM UTC
Resolved
Jun 18, 2026, 07:53 PM UTC
Duration
3h 5m
Detected by Pingoru
Jun 18, 2026, 04:48 PM UTC

Affected components

Customer ServicesSupport SystemsSupport Ticketing SystemFastlyCustomer ServicesSupport SystemsSupport Ticketing System

Update timeline

  1. investigating Jun 18, 2026, 04:48 PM UTC

    Our engineers have been informed that our Customer Relationship Management (CRM) provider is currently experiencing an incident. As a result, you may experience slightly delayed responses from our Support team while we implement an internal workaround and monitor this provider's incident updates. All other Fastly services remain fully operational. Our network and security products continue to deliver without disruption. We will provide an update if the situation changes.

  2. investigating Jun 18, 2026, 06:49 PM UTC

    We have an update regarding the ongoing Informational affecting Support Ticketing System. Our provider has reported that a contributing factor has been identified and they are working on a fix. As a reminder, Fastly's core edge network and security services remain unaffected. Please continue to email [email protected] for any assistance while our standard support and CRM channels remain impacted. Updated on 18 June 2026 at 18:49 UTC

  3. resolved Jun 18, 2026, 07:53 PM UTC

    The third party provider issue affecting Support Ticketing System services has been fully resolved. All Fastly Customer Support services and CRM systems have been restored and are operating normally. Ticket processing and standard communication channels are fully functional. We apologize for the inconvenience and appreciate your patience during this interruption to our support channels. Resolved on 18 June 2026 at 19:53 UTC