At 1:38 PM UTC, our monitoring triggered an internal incident after a period of an increased number of 504 errors. Production pages should not have been affected unless they were uncached and requested within this timeframe.
For a duration of 2 minutes, Fastly kept getting sporadic 504s because actions in Adobe I/O Runtime were producing invalid responses and exited unexpectedly.
The situation automatically improved within minutes, so there’s no need for immediate action, but we’ve started an investigation into the root cause.