Anycast routing Phoenix to LA

I have a customer that is being routed via LAX while they are located on Cox within Phoenix. I was able to get a MTR from them:

  1. AS???    172.24.128.1                                                   0.0%    20    0.2   0.2   0.2   0.4   0.0
  2. AS???    192.168.1.1                                                    0.0%    20    0.6   0.7   0.6   2.5   0.4
  3. AS22773  ip98-171-91-129.ph.ph.cox.net (98.171.91.129)                  0.0%    20    4.4   4.7   2.1  23.8   4.7
  4. AS22773  184.185.66.166                                                 0.0%    20    4.6   3.9   1.9   7.4   1.5
  5. AS22773  wsip-184-178-207-128.ph.ph.cox.net (184.178.207.128)           0.0%    20    1.6   2.7   1.2   4.2   0.9
  6. AS???    100.120.101.8                                                  0.0%    20    2.4   4.1   1.9  16.5   3.1
  7. AS???    100.120.100.12                                                 0.0%    20    3.3   3.2   1.8   6.3   1.1
  8. AS???    ???                                                           100.0    20    0.0   0.0   0.0   0.0   0.0
  9. AS7922   be-200-pe11.600wseventh.ca.ibone.comcast.net (50.248.118.9)    0.0%    20   16.8  15.5  14.0  17.0   1.0
 10. AS7922   be-3412-pe12.600wseventh.ca.ibone.comcast.net (96.110.33.78)   0.0%    20   16.8  15.4  14.1  16.8   0.8
 11. AS???    ???                                                           100.0    20    0.0   0.0   0.0   0.0   0.0
 12. AS40509  ip-137-66-7-137.customer.flyio.net (137.66.7.137)              0.0%    20   13.9  14.6  13.5  16.0   0.8

It’d be much appreciated if you could take a look into tuning this route. I should be able to verify a fix either from my backend or following up with them. Thanks!

I’ve asked our upstream to take a look, they said it’s unfortunately a known issue with Cox but they’ll see if there’s anything they can do about it.

1 Like

Thanks for taking a look!

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