I can’t access my app nor any of any fly.io site except for this one. I tried with different providers (just in case mine was the issue, but still the same result)
flyctl is also returning timeout
λ flyctl apps list
Error: Post “GraphQL Playground ”: dial tcp 77.83.143.220:443
1 Like
Same here.
I can’t access my app and flyctl is returning timeout.
I can’t see anything in the status.fly.io page.
in case it makes any difference, I’m connecting from latam.
I tried using a vpn with an US server and it works fine, so it may be some issue with the load balancer redirecting to a non working server
1 Like
Thanks for the comment. It helps.
We are connecting from Latam too.
Hey there!
@NoMachine @nicanorperera can you provide a traceroute to fly.io ? This will help us determine if it’s a routing issue.
1 Like
hope this helps
Tracing route to fly.io [37.16.18.81]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.0.1
2 14 ms 11 ms 15 ms XXXXXXXXXXX.fibertel.com.ar [XXXXXXXXXX]
3 * * * Request timed out.
4 20 ms 12 ms 14 ms host188.181-96-62.telecom.net.ar [181.96.62.188]
5 * * * Request timed out.
6 * 15 ms 13 ms host39.181-89-51.telecom.net.ar [181.89.51.39]
7 13 ms 17 ms 14 ms ae4.0.edge2.eze2.as7195.net [200.25.50.80]
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
Trace complete.
More information:
I’m trying to connect from Argentina.
➜ traceroute fly.io
traceroute to fly.io (37.16.18.81), 64 hops max, 52 byte packets
1 docsis-gateway (192.168.0.1) 20.606 ms 3.916 ms 3.825 ms
2 * * *
3 * * *
4 * * *
5 * * *
6 host39.181-89-51.telecom.net.ar (181.89.51.39) 34.727 ms
host234.181-96-113.telecom.net.ar (181.96.113.234) 23.187 ms *
7 * ae4.0.edge2.eze2.as7195.net (200.25.50.80) 14.973 ms 17.079 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
(still going)
Any updates on this?
I still can’t access to fly or use flyctl.
kwaw
July 4, 2023, 3:47pm
9
We’ve reported it to our infra providers, awaiting a response.
In the meantime, can you use a VPN?
2 Likes
system
Closed
July 11, 2023, 4:32pm
12
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.