Strange routing from Seattle

Questions / Help
1

I’m on residential fiber internet in Seattle, but sometimes fly seems to route my traffic through Santiago, Chile. But only sometimes, and it can flip back and forth in seconds. For example, when I repeatedly curl debug.fly.dev:

> curl -s debug.fly.dev | grep -i region
Fly-Region: sea

> curl -s debug.fly.dev | grep -i region
Fly-Region: scl

> curl -s debug.fly.dev | grep -i region
Fly-Region: sea

I first noticed the issue because sometimes my connections to my own deployed app (in SEA) are very slow, and other times, very fast.

Is this an issue on the fly.io side? Or something else? Thanks!

2

hi, we’re aware of this and are looking into it. this sometimes happens with anycast and we work with our network providers to talk to other network providers to fix routing :slight_smile:

1 Like
3

@pg938 this should be fixed now, could you check again?

(debug.fly.dev has multiple IPs, dig it and try each one individually)

4

I’m still getting it from one of the IPs:

> curl -s 37.16.21.10 | grep -i region
Fly-Region: sea

> curl -s 77.83.140.164 | grep -i region
Fly-Region: scl

> curl -s 37.16.16.7 | grep -i region
Fly-Region: sea
5

could you share a traceroute to that IP? mtr --report -bzo "LSD NABVW" 77.83.140.164

6 
  1. AS???    192.168.1.1          0.0%    10    0    4.1   7.5   3.5   9.0  32.7
  2. AS???    192.168.0.1          0.0%    10    0    5.4   6.2   3.8   2.9  14.0
  3. AS209    tukw-dsl-gw77.tukw.  0.0%    10    0    6.7   8.5   6.4   1.6  12.3
  4. AS209    63-226-198-97.tukw.  0.0%    10    0   17.2  10.3   6.5   4.5  19.7
  5. AS???    ???                 100.0    10   10    0.0   0.0   0.0   0.0   0.0
  6. AS3549   ae2.3601.edge1.sgo1  0.0%    10    0  168.9 171.4 168.9   2.9 177.3
  7. AS3356   8.243.188.18         0.0%    10    0  183.3 171.4 168.3   4.3 183.3
  8. AS7195   ae1021.0.edge2.scl2  0.0%    10    0  172.4 171.3 169.7   1.5 174.7
  9. AS7195   200.25.88.201        0.0%    10    0  190.4 210.9 189.4  43.8 334.4
 10. AS40509  77.83.140.164        0.0%    10    0  171.1 170.2 167.9   2.4 174.5
7

It seems to be working properly now:

> curl -s 77.83.140.164 | grep -i region
Fly-Region: sea
 
> mtr --report -bzo "LSD NABVW" 77.83.140.164
  1. AS???    192.168.1.1          0.0%    10    0    5.5   6.8   4.3   3.3  15.9
  2. AS???    192.168.0.1          0.0%    10    0    8.1   7.9   4.5   3.6  16.2
  3. AS209    tukw-dsl-gw77.tukw.  0.0%    10    0   12.4  20.9   7.6  22.5  79.3
  4. AS209    tukw-agw1.inet.qwes  0.0%    10    0    8.5   9.9   6.8   2.0  13.5
  5. AS???    ???                 100.0    10   10    0.0   0.0   0.0   0.0   0.0
  6. AS3257   ae17.cr4-sea2.ip4.g  0.0%    10    0   15.5  12.5   8.6   5.4  26.6
  7. AS3257   ip4.gtt.net (72.29.  0.0%    10    0    8.8  11.4   8.2   3.3  17.9
  8. AS40509  77.83.140.164        0.0%    10    0   16.0  11.1   7.3   3.6  17.2
8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.