The problem seems to be resolved automatically. My best guess is somewhere in the process there is something passing Fastly servers, and Fastly mistakenly throws an error. I’m not sure if Fastly resolved the problem after a while (which seems likely to me) or it was just me that did something that fixed the problem (i changed some stuff due to other problems, the code is the same though and hasn’t changed).