Still getting extremely high latencies to all servers in the Western US and Canada regions
particularly during the free night time unlimited time. Latencies during day time fluctuate between 300 and 600ms, at nighttime it stays around 500-600ms.
Closer to 8am the problem because worse : 550+ms and heavy packet loss as well.
Pings to NYC seem normal but as soon as packets leave nyc something is seriously wrong with either savvis/AT&T routing or peering.
NYC:
https://www.speedtest.net
Tampa, Florida (SE US):
https://www.speedtest.net
El Paso, Texas (central US):
https://www.speedtest.net
San Fransisco (west coast):
https://www.speedtest.net
Vancouver (western Canada):
https://www.speedtest.net
As a result MANY servers are still slow and websites from the same are taking extremely long to open.
Traceroute to cnet.com:
traceroute to another central US server:
In both of the above traceroutes it's quite clear that right after reaching US routes/latency skyrockets.
Anyone know what could be going on ? The undersea seacam cables got fixed and huge lag issues are still there.
Also to be noted : this problem is happening between around 3am up to about 9am IST. So basically the entire free period + a few hours
Problem started right after 27th (the day the seacam lines got fixed).
particularly during the free night time unlimited time. Latencies during day time fluctuate between 300 and 600ms, at nighttime it stays around 500-600ms.
Closer to 8am the problem because worse : 550+ms and heavy packet loss as well.
Pings to NYC seem normal but as soon as packets leave nyc something is seriously wrong with either savvis/AT&T routing or peering.
NYC:
https://www.speedtest.net
Tampa, Florida (SE US):
https://www.speedtest.net
El Paso, Texas (central US):
https://www.speedtest.net
San Fransisco (west coast):
https://www.speedtest.net
Vancouver (western Canada):
https://www.speedtest.net
As a result MANY servers are still slow and websites from the same are taking extremely long to open.
Traceroute to cnet.com:
Code:
Tracing route to gtm-tron-xw.cnet-basic-performance.akadns.net [216.239.122.178]over a maximum of 30 hops: 1 11 ms 12 ms 12 ms 59.93.240.1 2 40 ms 39 ms 43 ms 218.248.255.90 3 50 ms 49 ms 55 ms 121.244.68.57.static-lvsb.vsnl.net.in [121.244.68.57] 4 47 ms 50 ms 49 ms if-14-0-0-101.core2.MLV-Mumbai.as6453.net [216.6.13.37] 5 191 ms 193 ms 193 ms if-14-0-0-1751.mcore3.L78-London.as6453.net [216.6.13.102] 6 273 ms 276 ms 273 ms if-15-0-0-890.core2.NTO-NewYork.as6453.net [216.6.97.97] 7 274 ms 269 ms * Vlan13.icore1.NTO-NewYork.as6453.net [216.6.97.46] 8 468 ms 469 ms 475 ms 192.205.35.13 9 536 ms 530 ms 531 ms cr2.n54ny.ip.att.net [12.122.86.10] 10 534 ms 534 ms 534 ms cr2.wswdc.ip.att.net [12.122.3.38] 11 532 ms 532 ms 531 ms cr1.attga.ip.att.net [12.122.1.173] 12 535 ms 536 ms 532 ms cr2.dlstx.ip.att.net [12.122.28.174] 13 528 ms 529 ms 534 ms gar10.dlstx.ip.att.net [12.122.138.121] 14 538 ms 541 ms 539 ms 12.87.121.22 15 530 ms 533 ms 534 ms c18-rb-gtm2-tron-xw-lb.cnet.com [216.239.122.178]Trace complete.
Code:
Tracing route to mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]over a maximum of 30 hops: 1 7 ms 11 ms 11 ms 59.93.240.1 2 38 ms 43 ms 43 ms 218.248.255.86 3 53 ms 49 ms 50 ms 218.248.248.250 4 504 ms 502 ms 500 ms 206.24.169.93 5 504 ms * * cr1-pos-0-0-3-0.londonuk1.savvis.net [204.70.192.5] 6 * 494 ms 493 ms cr2-tengig-0-15-0-0.NewYork.savvis.net [204.70.196.118] 7 508 ms 505 ms 503 ms er2-tengig-3-1.NewYork.savvis.net [204.70.198.18] 8 497 ms 505 ms 505 ms 192.205.36.185 9 541 ms 545 ms 548 ms cr2.n54ny.ip.att.net [12.122.80.238] 10 542 ms 535 ms 538 ms cr2.wswdc.ip.att.net [12.122.3.38] 11 551 ms 551 ms 549 ms cr1.attga.ip.att.net [12.122.1.173] 12 537 ms 539 ms 545 ms cr2.dlstx.ip.att.net [12.122.28.174] 13 542 ms 543 ms 538 ms gar23.dlstx.ip.att.net [12.122.138.157] 14 543 ms 546 ms 548 ms 12-122-254-154.attens.net [12.122.254.154] 15 547 ms 552 ms 551 ms mdf001c7613r0004-gig-10-1.dal1.attens.net [63.241.193.18]Trace complete.In both of the above traceroutes it's quite clear that right after reaching US routes/latency skyrockets.
Anyone know what could be going on ? The undersea seacam cables got fixed and huge lag issues are still there.
Also to be noted : this problem is happening between around 3am up to about 9am IST. So basically the entire free period + a few hours
Problem started right after 27th (the day the seacam lines got fixed).