Community Forum
FWIW; that trace shows that the packets are beyond Comcast webspace and are now into the backbone transit webspace of the level3 provider. It is they who should be contacted concerning this. The Comcast local and regional routers all have low latency.
I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
@falconeye wrote:
Just because comcast's end is fine, doesnt mean that they still cant make a tweak to fix this though via routing. As just a consumer though, if the company has the power to fix it with a minor tweak by taking an altered route, I think they should do it.
On top of that, the routing should be based on your starting point until it leads to the end server. Others are having the same issue as me who have much different starting points than me. Coincidence that comcast is pathing the same route even though we are different geo locations? Pathing ideally takes the most effective route to nodes etc, but it seems more like they take the most cost effective route compared to performance.
It's beyond the scope of this forum to discuss BGP routing metrics. Research into the subject is suggested.
Route selection has no metric for geographical distance or latency -- routes are selected purely based on the least number of carrier transitions. With BGP routing, the routing is determined pretty much by the remote reciever, not the client / sender.
Ex: Comcast (TX) -> TWTC (CA) -> CyrusOne (TX)
is a shorter route than
Comcast (TX) -> Level3 (TX) -> TWTC (TX) -> CyrusOne (TX)
That's just the way the Internet works.
Comcast pretty much only has one external route: 0.0.0.0/0
They pass everything to their upstream bandwidth provider for a given market (Level(3) and ATT are a couple of examples, and that provider works out how to forward the traffic based on a number of factors. A few years ago it was just standard BGP metrics that influenced the decision, but today nearly all backbone providers are using technology like intelligent route reflectors to engineer their traffic flows for better performance and to avoid point congestion. This can result in paths being used that are not latency-equivalent, but provide much better service in terms of capacity and packet loss.
The only thing Comcast can influence is which carrier network onto which a packet will be forwarded. After that they are unable to control any aspect of which path will be chosen. Once it's on the upstream carrier's network all routing decisions are firmly in that carrier's hands.
Routing is even way more complicated than this.
I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
