Outsiders's profile

Visitor

 • 

16 Messages

Saturday, December 9th, 2023 10:36 PM

Closed

Chicago, Illinois Servers Showing High Packet Losses After Area Maintenance

I checked an online game and three sites and I'm getting high packet losses from mainly these two Comcast servers.

be-312-arsc1.area4.il.chicago.comcast.net
be-32211-cs21.350ecermak.il.ibone.comcast.net

These packet losses started Friday morning after maintenance was done Thursday night in the Chicago, Illinois area.  These losses are causing connection and loading problems.

EVE Online (Game)
be-312-arsc1.area4.il.chicago.comcast.net
be-32211-cs21.350ecermak.il.ibone.comcast.net

Twitch.com
be-312-arsc1.area4.il.chicago.comcast.net
be-32211-cs21.350ecermak.il.ibone.comcast.net
be-1121-cr21.350ecermak.il.ibone.comcast.net
be-1313-cr13.1601milehigh.co.ibone.comcast.net
be-304-cr13.champa.co.ibone.comcast.net

Google.com
be-312-arsc1.area4.il.chicago.comcast.net
be-502-ar01.area4.il.chicago.comcast.net

Twitter.com
be-312-arsc1.area4.il.chicago.comcast.net

If needed, I can rerun the tests and provide images of the packet losses.

Visitor

 • 

8 Messages

1 year ago

Ok so it wasn't just me getting the same issues with the Chicago servers, some days the packet loss through some of their hops gets to 14%. I'm guessing it's due to heavy congestion some days. I'm in northern Indie and really wish they kept the Hammond node up, never had any issues through that one.

8 Messages

1 year ago

This is a constant on going problem.. I tried calling to report the issue  but they only want to dispatch to my home...

be-32211-cs21.350ecermak.il.ibone.comcast.net    is the current problem..    this is completely on the comcast network... 

PLEASE FIX YOUR WHOLELY OWNED BACKBONE!!!!!

Official Employee

 • 

1.4K Messages

Thanks for reaching out, user_04tqn5! I'm so sorry you've been having issues like this. I'd be more than happy to help if this is ongoing. In order to get started can you, please send us a direct chat message with your full name and complete service address to “Xfinity Support”. To do so, click on the chat icon located at the top right of this forums page.

--

• Click "Sign In" if necessary

• Click the "direct messaging" icon or https://comca.st/3lv0gXz

• Click the "New message" (pencil and paper) icon

• Type "Xfinity Support" in the "To:" line and select "Xfinity Support" from the drop-down list which appears. The "Xfinity Support" graphic replaces the "To:" line

• Type your message in the text area near the bottom of the window

• Press Enter to send it

 

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

New Poster

 • 

3 Messages

@user_04tqn5​ Any resolve on your issue?

New Poster

 • 

3 Messages

1 year ago

 Is hit or miss: be-310-arsc1.area4.il.chicago.comcast.net [68.86.188.93] 

this is concerning too: po-100-xar02.mtprospect.il.chicago.comcast.net [162.151.47.217]

C:\Users\user>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Linksys [192.168.x.x]
  2     9 ms    10 ms     9 ms  96.120.25.73
  3    12 ms     9 ms    10 ms  be-302-1360-rur02.mtprospect.il.chicago.comcast.net [96.110.165.113]
  4     8 ms    14 ms    16 ms  po-100-xar02.mtprospect.il.chicago.comcast.net [162.151.47.217]
  5     *       13 ms    12 ms  be-310-arsc1.area4.il.chicago.comcast.net [68.86.188.93]
  6    13 ms    13 ms    10 ms  be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
  7    15 ms    16 ms    15 ms  c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
  8    14 ms    17 ms    15 ms  142.250.209.145
  9    11 ms    21 ms    16 ms  142.251.60.1
 10    11 ms    11 ms    16 ms  dns.google [8.8.8.8]

Trace complete.

C:\Users\user>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms Linksys [192.168.x.x]
  2    12 ms     9 ms    16 ms xx.xx.2x.7x
  3    14 ms    16 ms    14 ms  be-302-1360-rur02.mtprospect.il.chicago.comcast.net [96.110.165.113]
  4    16 ms    15 ms    10 ms  po-100-xar02.mtprospect.il.chicago.comcast.net [162.151.47.217]
  5     *       56 ms     *     be-310-arsc1.area4.il.chicago.comcast.net [68.86.188.93]
  6    13 ms    11 ms    17 ms  be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
  7    12 ms    12 ms    13 ms  c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
  8    14 ms    17 ms    17 ms  142.250.209.145
  9    13 ms    16 ms    16 ms  142.251.60.1
 10    16 ms    15 ms    18 ms  dns.google [8.8.8.8]

Trace complete.

C:\Users\user>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms Linksys [192.168.x.x]
  2     9 ms     9 ms    10 ms xx.xx.2x.7x
  3    10 ms    10 ms     9 ms  be-302-1360-rur02.mtprospect.il.chicago.comcast.net [96.110.165.113]
  4    12 ms     8 ms    14 ms  po-100-xar02.mtprospect.il.chicago.comcast.net [162.151.47.217]
  5     *        *        *     Request timed out.
  6    75 ms     7 ms    11 ms  be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
  7    14 ms    17 ms    12 ms  c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
  8    15 ms    12 ms    12 ms  142.250.209.145
  9    15 ms    12 ms    11 ms  142.251.60.1
 10    14 ms    14 ms    15 ms  dns.google [8.8.8.8]

Trace complete.

C:\Users\user>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms Linksys [192.168.x.x]
  2    10 ms    11 ms     9 ms xx.xx.2x.7x
  3    14 ms    13 ms    11 ms  be-302-1360-rur02.mtprospect.il.chicago.comcast.net [96.110.165.113]
  4   129 ms    15 ms    13 ms  po-100-xar02.mtprospect.il.chicago.comcast.net [162.151.47.217]
  5    20 ms    29 ms     *     be-310-arsc1.area4.il.chicago.comcast.net [68.86.188.93]
  6    15 ms    10 ms    10 ms  be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
  7    25 ms    11 ms    12 ms  c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
  8    13 ms    16 ms    13 ms  142.250.209.145
  9    18 ms    16 ms    16 ms  142.251.60.1
 10    20 ms    15 ms    12 ms  dns.google [8.8.8.8]

Trace complete.

C:\Users\user>tracert 8.8.8.8

Tracing route to dns.google [8.8.8.8]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms Linksys [192.168.x.x]
  2    68 ms    12 ms    10 ms  xx.xx.2x.7x
  3    37 ms    11 ms     9 ms  be-302-1360-rur02.mtprospect.il.chicago.comcast.net [96.110.165.113]
  4    13 ms    11 ms     8 ms  po-100-xar02.mtprospect.il.chicago.comcast.net [162.151.47.217]
  5     *        *        *     Request timed out.
  6    67 ms    10 ms    10 ms  be-502-ar01.area4.il.chicago.comcast.net [96.216.150.118]
  7    15 ms    10 ms    15 ms  c-50-171-101-230.unallocated.comcastbusiness.net [50.171.101.230]
  8    13 ms    12 ms    16 ms  142.250.209.145
  9    11 ms    14 ms    11 ms  142.251.60.1
 10    11 ms    10 ms    11 ms  dns.google [8.8.8.8]

Trace complete.

(edited)

Official Employee

 • 

915 Messages

Hey there, @brkfrnr03. Our team can definitely understand how stressful and irritating it is to have issues with your internet connection. We all work from home on this end of the screen so we can completely relate to how it causes you to make arrangements that you didn't expect. If you could please send me a DM with your first and last name along with your full-service address, we can get started looking into the traceroute with your connection.

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick
forum icon

New to the Community?

Start Here