New Member
•
2 Messages
Internet Routing Issue
Our core business utilizes a comcast PoP on what is called Comcast legacy network. Comcast has provided us IP addresses in the 72.55.65.x range. One of our business partners utilizes a Comcast business connection at their office (located 6 miles away), we have a VPN tunnel which connects them to our network. Recently we have had several issues with this site including varying levels of latency on the link.
During trroubleshooting this link we noticed a significant routing difference between traffic destined for this remote site and traffic destined for us from the remote site. This is best illustrated by the following traceroutes.
Trace from remote partner site (50.240.123.137) to our Core site (72.55.65.6):
1 886 ms 1ms <1 ms 192.168.22.2
2 2 ms 2ms 1 ms 50.240.123.142-static.hfc.comcastbusiness.net[50.240.123.142]
3 26 ms 27ms 40ms 50.159.229.1
4 30 ms 27ms 28ms te-0-6-0-1-sur01.deerwood.fl.jacksvil.comcast.net [68.86.171.213]
5 13 ms 11ms 19ms te-0-4-0-13-ar02.southside.fl.jacksvil.comcast.net [68.87.164.193]
6 7 ms 12ms 16ms te-0-2-0-1-sur03.southside.fl.jacksvil.comcast.net [162.151.18.94]
7 244ms 199ms 204ms 69.241.106.194
8 88ms 83ms 88ms 72-55-65-6-static.hfc.comcastbusiness.net [72.55.65.6]
Trace Complete
Trace from our Core site (72.55.65.6) to the remote partner(50.240.123.137):
Comcast_Jon
Administrator
•
1.5K Messages
10 years ago
Hello Jeff,
Welcome to the forum.
Sorry for the late reply to your question.
Technically this is "normal" in network routing as it is built to take the "closes" route between source and destination.
Most (not all) connectivity issue normally stems from signal level issue.
Based on your post this appears to be a "recent" issue with our service on its regard can you clarify a few item for us?
1. When did this issue started?
2. Does the latency issue occur intermittently or consistently?
3. Do you see this issue with connectivity or just VPN?
Thank you
0
0
dcps-jeff
New Member
•
2 Messages
10 years ago
1. This began sometime prior to last summer (July 2014) as that is when it was first reported.
2. The latency is pretty consistant as the paths between the sites do not vary much.
3. All connectivity.
Our organization is east coast (florida based) and has been using this circuit for years. We have never had to route all the way to Los Angeles before branching out to the internet. All of our outbound traffic is being routed to and through Los Angeles for some reason. Usually it was Tampa or Atlanta, but never the west coast.
It is odd that local business traffic in-bound to us comes straight to us but anything outbound takes this long path. I am sure if a Network engineer looked at the routing on the 2nd or 3rd hop out from our network (on the trace provided) it would probably get resolved pretty quickly.
Due to this issue being outstanding for so long, and no real help from comcast, keeps getting referred to NOC in Jersey and then we hear nothing back, our management has asked for quotes from AT&T for circuits to replace this one.
0
0