You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This makes me suspect that there is an issue with Fly.io proxy layer. I have been getting timeout alerts (exceeded 48s) for other workloads that are running on Fly.io, completely unrelated to this one.
We've been seeing 503 errors on https://changelog.com starting on March 29th @ 13:40:50 UTC:
We assumed that this was Erlang/OTP 26.2.3, and downgraded to 26.2.2, as captured here: #507 (comment)
Today - April 1st - the 503s re-appeared at 13:22 UTC even though nothing changed with the app:
According to Fly.io app metrics, the app did not return any 503s:
This makes me suspect that there is an issue with Fly.io proxy layer. I have been getting timeout alerts (exceeded
48s
) for other workloads that are running on Fly.io, completely unrelated to this one.Will reach out to Fly.io for more details. FWIW:
The text was updated successfully, but these errors were encountered: