Skip to content
LCG_Rockford's profile

New Member

 • 

1 Message

Monday, August 10th, 2015 1:00 PM

Issues with traffic/routing in Chicago today?

Noticing problems with our VoIP service, which is hosted in our data center in Chicago.

 

Connection locally seems fine, traceroutes have some interesting info for hops 5 and 6 between our office and Chicago:

 

4  te-0-7-0-19-sur01.rockford.il.chicago.comcast.net (162.151.32.61)  40.121 ms  85.213 ms  156.322 ms

5  te-0-7-0-1-sur02.rockford.il.chicago.comcast.net (68.87.233.110)  15.900 ms

    te-0-7-0-5-sur02.rockford.il.chicago.comcast.net (68.87.233.54)  9.150 ms

    te-0-7-0-6-sur02.rockford.il.chicago.comcast.net (68.87.233.58)  42.713 ms

6  te-2-10-0-3-ar01.area4.il.chicago.comcast.net (68.86.188.233)  111.038 ms

    te-0-2-0-4-ar01.area4.il.chicago.comcast.net (68.86.197.205)  34.164 ms

    te-2-10-0-0-ar01.area4.il.chicago.comcast.net (68.85.176.173)  140.148 ms

7  * * *

8  nozone-inc.ear2.chicago2.level3.net (4.71.248.202)  12.131 ms  20.113 ms  11.645 ms

 

Noticing very erratic latency (20ms to 200ms) if I leave a ping running for several minutes.  VoIP calls are choppy.  All of our equipment appears to be in good order at both ends of this connection.

Problem solver

 • 

305 Messages

9 years ago

The end result there looks actually looks good, which is what is important. Though, from the traceroute itself it's possible you may be seeing some type of issue. What does an inbound/outbound MTR look like? 

New Member

 • 

2 Messages

9 years ago

We have been having more internet issues than usual at our location in Oak Brook IL.  Poor VOIP phone call quality. Speeds otherwise ok. Traceroutes consistently show high latency (in the hundreds) & high packet loss at ar01.area4.il.chicago.comcast.net.  This happens on most trace routes and MTR's done recently, the worst and most consisent being the past 2 days.  Seems to improve after calling and pleading my case to reps & tech support, supervisors all day to no avail.  Tech support said, "I see and I'm in "agreence"  with you that the issue is not at your premisis, and should be fixed by internet maintenance.  He further clarified that, "a ticket can't be written to maintenance, even though they should handle this issue,  until we roll a truck to your premisis and the tech writes the ticket.   I asked why spend the money sending at tech, and delay working on the issue so a un need truck can come out.  He & others repeated this answer, "because that's the way it's done, no exceptions".  No wonder bills are so high if they pay a tech to drive a truck out, even when they and the customer know the issue isn't on the premisis.  I lost several hours of my work day with these absurd arguements getting everything but help until someone in the "we're on it team" finally by passed the "truck roll" requirement and filed a ticket with dispatch & maintenance.  Problem seems to be better today. It would seem comcast is possibly using traffic management to slow competing VOIP service.  Sad and illegal.