![]() So its going to give a false positive of 100% packet loss and and no latency information. What that is showing is the device before the WOT servers is not displaying the ICMP information to the pingplotter. The latency for the backbone I know about is about 70-80ms between them two locations. So whats happening here is the increase in latency between their San Jose Router to their Ashburn (washington DC) router. ![]() That test looks to be about right but that is high latency for being within the country and on the same backbone. That much latency should not be seen within their network as this traceroute originates at a Telia Route server, and this is not peak time so there is no explaination other than something wrong on the device itself. The highlighted part is the device that is on the return path. TeliaSonera Looking Glass - traceroute inet 209.170.73.34 as-number-lookupĬommand: traceroute inet 209.170.73.34 as-number-lookup I can almost say for certain that this is an issue within Telia that needs to be looked at. Either way the ticket numbers to their support staff looks bad on them if their the same problems and the issue still not fixed. 1 of 3 things will happen, They will move off telia, have telia fix the problem, or let it continue. Whether they respond back or not or give you a crappy answer just constantly do it. FYI I'm just providing some of my knownledge in this area, I do feel that the best way to solve this problem is to constantly open tickets with wargamining.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |