Hi! I am receiving abnormally high response times to my Fly hosted applications again. Was wondering if this could be looked in to?
Here’s the traceroute:
traceroute to foundry-staging-trpc-web.fly.dev (66.241.124.45), 64 hops max, 40 byte packets
1 dsldevice (192.168.1.254) 24.548 ms 1.219 ms 1.098 ms
2 172-8-144-1.lightspeed.irvnca.sbcglobal.net (172.8.144.1) 2.068 ms 2.303 ms 2.089 ms
3 64.148.105.112 (64.148.105.112) 1.918 ms 2.342 ms 2.089 ms
4 12.243.128.102 (12.243.128.102) 9.073 ms 7.625 ms 7.731 ms
5 ggr2.la2ca.ip.att.net (12.122.128.101) 4.624 ms 4.662 ms 6.456 ms
6 192.205.37.26 (192.205.37.26) 4.428 ms 4.690 ms 3.994 ms
7 be-3202-cs02.losangeles.ca.ibone.comcast.net (96.110.44.149) 3.135 ms
be-3102-cs01.losangeles.ca.ibone.comcast.net (96.110.44.145) 3.760 ms
be-3402-cs04.losangeles.ca.ibone.comcast.net (96.110.44.157) 4.011 ms
8 be-3312-pe12.600wseventh.ca.ibone.comcast.net (96.110.33.74) 4.138 ms
be-3212-pe12.600wseventh.ca.ibone.comcast.net (96.110.33.70) 3.289 ms
be-3112-pe12.600wseventh.ca.ibone.comcast.net (96.110.33.66) 3.744 ms
9 75.149.231.130 (75.149.231.130) 3.571 ms 4.550 ms 3.364 ms
10 * * *
11 * * *
12 * * *
traceroute6 to foundry-staging-trpc-web.fly.dev (2a09:8280:1::24:d816) from 2600:1700:4641:21e0:745b:45b7:ccfd:7c04, 64 hops max, 28 byte packets
1 * * *
2 2001:506:6000:131:69:235:127:184 25.592 ms 2.586 ms 2.183 ms
3 2001:506:6000:131:71:156:220:238 25.496 ms 2.293 ms 2.198 ms
4 la2ca402igs.ipv6.att.net 27.891 ms 4.853 ms 5.008 ms
5 att-gw.la2ca.comcast.net 27.217 ms 4.345 ms 4.886 ms
6 be-3402-cs04.losangeles.ca.ibone.comcast.net 27.502 ms
be-3202-cs02.losangeles.ca.ibone.comcast.net 27.192 ms
be-3302-cs03.losangeles.ca.ibone.comcast.net 27.531 ms
7 be-3112-pe12.600wseventh.ca.ibone.comcast.net 29.029 ms
be-3212-pe12.600wseventh.ca.ibone.comcast.net 27.995 ms
be-3412-pe12.600wseventh.ca.ibone.comcast.net 28.219 ms
8 2001:559:0:9::3a 27.987 ms 15.540 ms 3.753 ms
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
The traceroute you posted is showing 3ms round-trip times (super fast), so it looks like the issue you’re experiencing must be somewhere else in your application stack this time.
Thanks @wjordan for the quick response! Which row are you identifying as the 3ms total roundtrip time? The traceroute times look pretty similar to the last time this has happened? Check out the post from last month and compare those times and to what PeterCxy discovered
Then (when the issue originally surfaced)
traceroute to foundry-staging-trpc-web.fly.dev (66.241.124.45), 64 hops max, 40 byte packets
1 192.168.1.254 (192.168.1.254) 1.331 ms 1.111 ms 0.970 ms
2 172.8.144.1 (172.8.144.1) 1.939 ms 2.179 ms 1.965 ms
3 64.148.105.112 (64.148.105.112) 2.011 ms 3.690 ms 2.422 ms
4 12.243.128.102 (12.243.128.102) 10.878 ms 8.497 ms 7.964 ms
5 12.122.128.101 (12.122.128.101) 12.017 ms 6.073 ms 3.879 ms
6 192.205.37.26 (192.205.37.26) 10.925 ms 4.808 ms 4.303 ms
7 96.110.44.157 (96.110.44.157) 12.777 ms
96.110.44.153 (96.110.44.153) 11.958 ms
96.110.44.149 (96.110.44.149) 11.770 ms
8 96.110.33.66 (96.110.33.66) 11.479 ms
96.110.33.78 (96.110.33.78) 12.501 ms
96.110.33.74 (96.110.33.74) 12.422 ms
9 75.149.231.130 (75.149.231.130) 11.240 ms 4.684 ms 3.536 ms
10 * * *
11 * * *
12 * * *
13 * * *
To now
traceroute to foundry-staging-trpc-web.fly.dev (66.241.124.45), 64 hops max, 40 byte packets
1 dsldevice (192.168.1.254) 24.548 ms 1.219 ms 1.098 ms
2 172-8-144-1.lightspeed.irvnca.sbcglobal.net (172.8.144.1) 2.068 ms 2.303 ms 2.089 ms
3 64.148.105.112 (64.148.105.112) 1.918 ms 2.342 ms 2.089 ms
4 12.243.128.102 (12.243.128.102) 9.073 ms 7.625 ms 7.731 ms
5 ggr2.la2ca.ip.att.net (12.122.128.101) 4.624 ms 4.662 ms 6.456 ms
6 192.205.37.26 (192.205.37.26) 4.428 ms 4.690 ms 3.994 ms
7 be-3202-cs02.losangeles.ca.ibone.comcast.net (96.110.44.149) 3.135 ms
be-3102-cs01.losangeles.ca.ibone.comcast.net (96.110.44.145) 3.760 ms
be-3402-cs04.losangeles.ca.ibone.comcast.net (96.110.44.157) 4.011 ms
8 be-3312-pe12.600wseventh.ca.ibone.comcast.net (96.110.33.74) 4.138 ms
be-3212-pe12.600wseventh.ca.ibone.comcast.net (96.110.33.70) 3.289 ms
be-3112-pe12.600wseventh.ca.ibone.comcast.net (96.110.33.66) 3.744 ms
9 75.149.231.130 (75.149.231.130) 3.571 ms 4.550 ms 3.364 ms
10 * * *
11 * * *
12 * * *
Neither of those traceroute outputs are showing any problems, your previous issue was on an ipv6 route and was fixed before you ran traceroute6 to capture it.
Traceroute output shows round-trip times (x ms) for 3 packets sent to each server along the way to the destination address, the last line at the bottom is the server just before your destination. It shows 11.240 ms 4.684 ms 3.536 ms (3-11ms) for the old traceroute and 3.571 ms 4.550 ms 3.364 ms (3-4ms) for the current one.
(traceroute sends UDP packets by default which our server doesn’t reply to which is why you see * * * afterwards; you can get more complete results using traceroute -T to send TCP or -I to send ICMP ECHO instead, or alternatively use mtr which sends ICMP ECHO by default.)
Appreciate your time