My depot worker seems to be having issues pushing to the v2 registry.
I’m wondering if that’s caused by the LHR capacity issues?
=> => # error: failed to copy: failed to do request: Put "https://registry.fly.io/v2/<app>/...
...
=> => # 4ad69f741e6b33e4f": write tcp [2605:4c40:119:6f87:0:b410:73cb:1]:53224->[2a09:8280:1:f132:9b03:c39f:b404:f5d2]:443: write: broken pipe
Seeing the same problem, seems very slow:
#11 pushing layer sha256:xxx 2.8s done
#11 pushing layer sha256:xxx 14.8s done
#11 38.47 error: failed to copy: failed to do request: Put "https://registry.fly.io/v2/fitterpal/blobs/uploads/xxx?zzz": write tcp [2605:4c40:119:6d3a:0:28cf:e60b:1]:36708->[2a09:8280:1:f132:9b03:c39f:b404:f5d2]:443: write: broken pipe
#11 38.47 retrying in 1s
#11 pushing layer sha256:xxx 340.6s done
#11 pushing layer sha256:xxx 365.9s done
#11 pushing layer sha256:xxx 670.3s done
This is on Github Actions so it’s normally very fast
Having the same problem over here, takes 10+ to push a 16MB container image 
No clue what’s going on and nothing is showing up on their status page as being degraded, so I think they have no clue this is going on 
Looks like we’re finally being heard Fly.io Status - Degraded connectivity to Fly Registry
Very frustrating that just acknowledging this problem took 3hrs
Having the same issue here. Currently trying to use a different registry:
FLY_REGISTRY_HOST=registry-iad.fly.io flyctl deploy
No idea yet if that works, but just sharing what I’m trying 
Btw not sure if it’s the same thing but I already reported registry issues this morning at 11AM CET
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.
