no, it's just that the incident has just been fixed by fastly https://status.fastly.com/incidents/vpk0ssybt3bj