[3-30-19] Physical Machine -> Dallas PoP Routing Issue

[Roy 10,832 / 0]

Hello,

 

Our physical machine to the Anycast Dallas PoP is routing all the way to NYC AGAIN!

 

This started happening again last night. I have contacted our physical hosting provider.

 

Thank you.

[Roy 10,832 / 0]

I am contacting our physical hosting (Nexril) provider's peer that has this issue directly. In a live chat with them now because I'm sick and tired of going through two parties to get this ridiculous routing issue fixed.

 

Thanks.

[Roy 10,832 / 0]

Contacted their peer (Hivelocity) directly via live chat. I got a ticket opened with the networking team.

 

Chat transcript is below:

 

Quote

Hello Christian Deacon,

 

Please find your requested chat transcript:

 

Chat started on Mar 30, 2019 05:06 PM
Christian Deacon      12:06 PM
Hi Support,

 

My name is Christian Deacon. I have an Anycast network setup which forwards traffic to a physical hosting provider in Dallas, TX. We use Vultr (AS20473) to host our PoP servers (Point Of Presence) and use Nexril (AS13830) as our physical hosting provider. We are having a routing issue from Nexril to our Dallas PoP server (they are both in the same location). Nexril peers with Hivelocity as well and goes through them. Hivelocity is routing all the way out to NYC. We had the same issue last week and Nexril contacted you and had this issue corrected. However, it is back and it adds ~60ms latency overhead to our network which is not acceptable for the service we host right now. I would rather contact you directly about this issue so I am not waiting for anybody else (e.g. Nexril).

 

Here is the current MTR from Nexril to our Anycast PoP server in Dallas:

 

1. x.x.x.x                                                 0.0%     2    0.7   4.1   0.7   7.5   4.7
 2. x.x.x.x                                                         0.0%     2    0.8   0.8   0.7   0.8   0.0
 3. 66-206-18-73.static.hvvc.us                                                       0.0%     2   14.7  17.3  14.7  19.9   3.6
 4. ???
 5. ???
 6. ???
 7. ???
 8. ???
 9. nyk-b5-link.telia.net                                                             0.0%     2   45.8  45.7  45.7  45.8   0.0
10. dls-b22-link.telia.net                                                            0.0%     2   32.3  32.3  32.3  32.3   0.0
11. vultr-ic-318447-dls-b22.c.telia.net                                               0.0%     2   32.8  32.8  32.8  32.8   0.0
12. ???

 

It is going from Dallas all the way to NYC, back to Dallas. When this is corrected, it stays in Dallas and results in only ~1ms latency overhead.

 

This is getting frustrating since this is the second time it has occurred and we've only had this Anycast network setup for a week now.

 

Can we please get this fixed?

 

Thank you.

 

Branden Tomski      12:06 PM
Hello, How may I assist you today?

 

Christian Deacon      12:06 PM
Hey Branden, I've submitted a long message above with our current issue.

 

Branden Tomski      12:09 PM
Could I have the ip of your server please?

 

Christian Deacon      12:10 PM
The physical hosting provider or our Anycast setup?

 

Christian Deacon      12:10 PM
Physical hosting provider - xxx.xxx.xxx.xxx

 

Christian Deacon      12:10 PM
Anycast IP - 92.119.148.5 (92.119.148.0/24)

 

Branden Tomski      12:11 PM
Thank you for that. I will need to open a ticket for you regarding this and get it over to networking so they may correct it for you

 

Christian Deacon      12:12 PM
Alright, thank you!

 

Christian Deacon      12:12 PM
Do you know if the networking team works during the weekends?

 

Branden Tomski      12:12 PM
okay I have created Ticket #xxxxxx

 

Branden Tomski      12:12 PM
and got it over to networking for you

 

Christian Deacon      12:13 PM
Alright, thank you again!

 

Branden Tomski      12:13 PM
Not a problem have a great day Christian

 

Chat ended on on Mar 30, 2019 05:13 PM
Visitor Details
Christian Deacon     Christian Deacon
[email protected]
Department: Support

 

Hivelocity's support was quick and very helpful  

 

Now to wait for the networking team.

 

Thanks!

[Roy 10,832 / 0]

The issue appears to have been fixed.

 

New route (lower latency than before):

 

 1. x.x.x.x.static.nexril.net                                                0.0%  3985    0.6   0.5   0.4  63.9   1.1
 2. be-20.cr01.dal.nexril.net                                                        0.0%  3985    0.9   0.5   0.4   2.1   0.0
 3. 66-206-18-73.static.hvvc.us                                                      0.1%  3985   21.9  18.7   1.2 1261.  38.0
 4. ???
 5. ???
 6. ???
 7. ???
 8. ae-34.a02.dllstx09.us.bb.gin.ntt.net                                             0.1%  3985    0.4   1.1   0.4  36.3   4.2
 9. ae-4.r10.dllstx09.us.bb.gin.ntt.net                                              0.1%  3985    0.7   0.6   0.6   1.3   0.0
10. ae-0.a01.dllstx09.us.bb.gin.ntt.net                                             33.8%  3985    1.5   2.0   0.4  52.9   5.2
11. ae-0.choopa.dllstx09.us.bb.gin.ntt.net                                          26.5%  3985    1.0   0.6   0.6  81.8   2.8
12. ???
13. ???
14. server15.us.gflclan.com                                                          0.0%  3984    0.6   0.6   0.5   1.1   0.0

 

Still yet to hear anything from Hivelocity. I'll wait a bit to see if I receive an update stating it's fixed from them.

 

Thank you.