[closed]

We're currently investigating performance issues with our TLS provisioning system.

All other services are unaffected.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

[closed]

We're currently investigating performance issues with our TLS provisioning system.

All other services are unaffected.

A fix has been implemented and we are monitoring the results.

[closed] We're currently investigating performance issues with our TLS provisioning system in the APAC region. All other services are unaffected.

We are continuing to investigate this issue.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

[closed] We're currently investigating performance issues with our TLS Edge Provisioning system. All other services are unaffected.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.

[closed] On January 11, 2022 from 10:30-11:00 UTC GlobalSign will rotate their Atlas TLS CAs intermediate certificates. Starting in 2022, GlobalSign Atlas TLS CAs will be updated every quarter, on the second Tuesday of the quarter at 10:30-11:00 UTC For customers who are using Fastly TLS managed certificates issued by GlobalSign, also known as Fastly TLS Commercial CA, this change will require action on your part if you are using certificate or public key pinning to avoid any impact to your traffic. For more information on the update from GlobalSign, please refer to the following links: https://support.globalsign.com/atlas/atlas-tls/atlas-tls-ica-rotations-2021

Maintenance will begin as scheduled in 60 minutes.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The scheduled maintenance has been completed.

[closed] We're currently investigating performance issues with our TLS provisioning system. All other services are unaffected.

This incident has been resolved.

[closed] On May 4th, 2021, Let's Encrypt began issuing certificates with a trust chain that includes its ISRG Root X1 certificate cross-signed by IdenTrust's DST Root CA X3 certificate. On September 30th, 2021, the DST Root CA X3 certificate will expire. Most devices trust the ISRG Root X1 certificate directly and will be unaffected by this expiration. This certificate chain allows us to extend the compatibility for Android devices supporting versions prior to 7.1.1 for an additional three (3) years. For customers who require support for Android devices older than Android 7.1 and who provide their own Let’s Encrypt certificates with our Platform TLS, Legacy Customer-Provided TLS Certificate Hosting Service, or Fastly TLS products, the change to Let's Encrypt's certificate chain will not require action on your part to avoid any impact on your traffic. For customers using OpenSSL versions prior to 1.1, this certificate expiration will reject the Android-compatible chain, regardless of whether you have ISRG Root X1 in their trust store. For more information on Let's Encrypt's certificate changes, their expiration, and actions you may need to take, refer to their posted details on the subject: - https://letsencrypt.org/2020/12/21/extending-android-compatibility.html - https://community.letsencrypt.org/t/production-chain-changes/150739 - https://community.letsencrypt.org/t/openssl-client-compatibility-changes-for-let-s-encrypt-certificates/143816 For general questions about this announcement, contact our customer support team at fastlytlsupdates@fastly.com.

Maintenance will begin as scheduled in 60 minutes.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The scheduled maintenance has been completed.

[closed] On August 24, 2021 GlobalSign will rotate their Atlas TLS CAs intermediate certificates. Beginning 2022, GlobalSign will start rotating their intermediate certificates on a quarterly basis, on the second Monday of every quarter. For customers who are using Fastly TLS managed certificates issued by GlobalSign, also known as Fastly TLS Commercial CA, this change will require action on your part if you are using certificate or public key pinning to avoid any impact to your traffic. For more information on the update from GlobalSign, please refer to the following links: https://www.globalsign.com/en/blog/upcoming-changes-publicly-trusted-tls-certificates https://support.globalsign.com/atlas/atlas-tls/atlas-tls-ica-rotations-2021

Please be advised that the time of this maintenance event has changed from Aug 24, entire day to Aug 24, 10:30 - 11:00 UTC.

The time for this to take place is: 9:30-10:00 UTC.

Maintenance will begin as scheduled in 60 minutes.

The scheduled maintenance has been completed.

[closed] Fastly engineering teams will be performing maintenance as part of the retirement of Shared and Shared Wildcards TLS certificates, as well as Certificate Procurement, Management, and Hosting beginning June 28th at 12:00 UTC. After this date, TLS management systems for certificate lifecycle management (including ordering, reissuing, and renewal) for Shared and Procured TLS certificates will be unavailable. All certificate and TLS domain management will now be in the Fastly TLS web interface for your TLS domains and certificates, including domains migrated from Shared and Procured TLC certificates. Fastly has been migrating TLS domains actively since November 2020 and most customers have already completed this process. If you have not already self-migrated or worked with Fastly support to migrate your domains, you will need to complete this before the maintenance begins on June 28th to prevent TLS traffic interruptions. Update: Start date moved from June 14th, 2021 to June 28th, 2021

Maintenance will begin as scheduled in 60 minutes.

Scheduled maintenance is currently in progress. We will provide updates as necessary.

The scheduled maintenance has been completed.

[closed] We're currently investigating performance issues with our TLS provisioning system. All other services are unaffected.

The issue has been identified and a fix is being implemented.

A fix has been implemented and we are monitoring the results.

This incident has been resolved.