fly.io down?

https://status.flyio.net/ says All Systems Operational

mw@Michaels-MacBook-Air ~ % dig fly.io

; <<>> DiG 9.10.6 <<>> fly.io
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61430
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;fly.io.				IN	A

;; ANSWER SECTION:
fly.io.			234	IN	A	37.16.18.81

;; Query time: 22 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Thu Oct 20 12:28:58 CEST 2022
;; MSG SIZE  rcvd: 51

mw@Michaels-MacBook-Air ~ % ping fly.io
PING fly.io (37.16.18.81): 56 data bytes
64 bytes from 37.16.18.81: icmp_seq=0 ttl=52 time=27.335 ms
64 bytes from 37.16.18.81: icmp_seq=1 ttl=52 time=25.307 ms
64 bytes from 37.16.18.81: icmp_seq=2 ttl=52 time=22.341 ms
^C
--- fly.io ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 22.341/24.994/27.335/2.051 ms
mw@Michaels-MacBook-Air ~ % curl fly.io
curl: (56) Recv failure: Connection reset by peer
mw@Michaels-MacBook-Air ~ %

saw that too.
Also deployments are failing

1 Like

Fly.io should be back up now. Can you post details about deployment failures? These two issues should be unrelated.

1 Like

Not OP but our Gitlab deployments were failing like this:

$ curl -L https://fly.io/install.sh | sh
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:08 --:--:--     0
curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to fly.io:443 
Cleaning up project directory and file based variables 00:01
ERROR: Job failed: exit code 35

Ah, OK, that makes sense, as downloading flyctl does require access to fly.io. Thanks for the info.

1 Like

Not sure if related but all my deploy commands end up this way:

➜ ffg-crops git:(main) flyctl deploy --verbose --no-cache --remote-only
==> Verifying app config
→ Verified app config
==> Building image
Remote builder fly-builder-winter-forest-8592 ready
==> Creating build context
→ Creating build context done

Error failed to fetch an image or build from source: error fetching docker server info: Get “http://[fdaa:0:bf1e:a7b:5adc:8ffa:bd8a:2]:2375/v1.41/info”: context deadline exceeded

Any tips? Anyone sees that one?

We have been pondering should we always download flyctl on deploy.

Now we do and it has been working flawlessly so we just probably continue using it like this :slight_smile:

1 Like

Hi,
We are also encountering a problem since yesterday. It looks like if flyio had some network latency issues…
flyctl deploy --dockerfile ./Dockerfile.fly --config ./fly.toml --remote-only -a ******** [...] Error: request to https://binaries.prisma.sh/all_commits/461d6a05159055555eb7dfb337c9fb271cbd4d7e/linux-musl/libquery_engine.so.node.gz.sha256 failed, reason: connect ETIMEDOUT 10***.156.224.54:443
Do you think this could be related?