atsak
Guru
- Joined
- Sep 7, 2009
- Messages
- 2,473
- Reaction score
- 487
Yeah - that clearly shows your problem is not voip.ms, but vtl.net.
As I said, one of the carriers between you...
You should open a ticket with your ISP, as they have the most weight with their upstream provider. Voip.ms doesn't have any control over how that traffic gets to their site, until the final hop normally.
This is not entirely true. VOIP.ms can use BGP if they use it to exclude a specific peer if they know what they're doing; issues like this can in fact be caused by BGP flapping (that's not the right term - I forget the right one). However, I expect they're not handling their own peering, likely their ISP is. They should in fact open a case with their colo provider. They can actually locate teh choke point and route around it in most cases, though it may not be least cost and thus might explain things.
Further, packet loss showing at VTL.net (or anywhere) isn't actually meaning that the packet is getting lost there necessarily. It could be anywhere in the chain between yourself and where you see the packet loss occuring. Also, routers now are often programmed to discard ping either all the time or when under load to maximize performance. So you can not infer definitively this is the case. You would need to sample a tracert at various times serveral times to confirm the loss is occuring at a given point.
It's also an over simplificaiton to say that "providers can route around issues before you even know of them". Most BGP or equivalent sessions specifically have a set of circumstances which decide when a link is poor enough ot reqeust a reroute. And sometimes peering isn't adequate to support that at a given ISP (for example in Canada Bell Canada has horrible peering because they're so arrogant they won't peer with tier 2 and 3 providers without charging them in most cases, so most stuff goes through the US).
While generally these automated session protocols and monitoring do catch these problems, the fact that some people are seeing an issue suggest that there's a couple ISP's needing to pay attention in a different way.