Yes, we were affected by this: https://status.fastly.com/incidents/3j0pnly3gvqb

Fastly was on top of it and routed around the issue quickly.