Update: The issue has been identified and a fix is being implemented. Posted Jun 08, 2021 - 10:44 UTC

Seems like this is being resolved; curious to see the details afterwards

(from https://status.fastly.com/incidents/vpk0ssybt3bj)