Performance Impact Issuing TLS Certificates with a Third Party Service Provider
Performance Impact Issuing TLS Certificates with a Third Party Service Provider
10 September 2025, 19:50 UTC
10 September 2025, 19:50 UTC
Fastly Engineering has identified a performance impact with issuing TLS certificates through one of our third-party service providers that is currently experiencing an outage.
Customers may experience a failure obtaining a TLS certificate as a result of this outage. Customers who need assistance with obtaining a TLS certificate can engage with our Support team through https://support.fastly.com . We apologize for this inconvenience and remain readily available to resolve any impact experienced as a result of this event.
10 September 2025, 21:31 UTC
10 September 2025, 21:31 UTC
Our Engineering team has confirmed an issue with our third-party provider, Globalsign, which is impacting Fastly-managed subscriptions.
As a result, the addition of new domains is currently blocked for both brand new subscriptions and modifications to existing ones.
No other services are impacted.
24 September 2025, 19:04 UTC
24 September 2025, 19:04 UTC
Our Engineering team has confirmed that our third-party provider, Globalsign, has identified the contributing factor to the issue impacting Fastly-managed subscriptions and are developing a mitigation strategy.
No other services are impacted.
07 October 2025, 17:25 UTC
07 October 2025, 17:25 UTC
Engineering has confirmed that our third-party provider, Globalsign has resolved the issue that impacted Fastly-managed subscriptions. Domains for new subscriptions and modifying existing ones has been fully restored. Customers may have experienced the inability to obtain new Fastly-managed certificates from 19:50 on the 10th of September 2025 to 16:31 on the 7th of October 2025 UTC.
This incident is resolved.
To offer feedback on our status page, click "Give Feedback"
Status Post, Created Date/Time: 2025-09-10 19:52:36 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.