Skip to main content

    Support

    Offers

walkersc's profile
walkersc
1st Topic
1st Reply
1st Like

Visitor

 • 

5 Messages

Thursday, March 24th, 2022 3:17 AM

Closed

IPv4 Pings no longer working

A little over a day ago, pings to IPv4 addresses stopped working (8.8.8.8 or xfinity.com).  I am able to ping my Xfinity assigned IP4 WAN address but no further.  IPv6 pings are working (google.com resolved to an IPv6 address).   This happened shortly after Comcast announced an enhancement in my area.  I contacted the standard support group but the higher support tier group has left for the day.  Will try to get into the higher tier support tomorrow. 

Question

 • 

Updated 

3 years ago

 • Edited

1.1K

5

0

Accepted Solution

walkersc

Visitor

 • 

5 Messages

3 years ago

Looks like Pings and Traceroute to IPv4 are working again.  4 days to fix is a bit extreme, but I'm happy to be running again.

2

user_ede1f6

Visitor

 • 

3 Messages

@walkersc​ Same here, looks good!

3 years ago

0

XfinityArmand

Official Employee

 • 

2.1K Messages

Hello there @user_ede1f6!  Thanks so much for taking the time to reach out to Xfinity Support with Digital Care here on our Community Forum to voice your service concerns.  We are so glad to hear from you and want to assist in any way that we can to get this taken care of for you.  You have reached out to a team of experts and we are going to get things squared away,  Please feel free to shoot us a private message so that we can take a closer look at things for you.  

 

To send a "direct message" / "private message" message to Xfinity Support:

 • Click "Sign In" if necessary

 • Click the "Direct Message" icon or https://comca.st/3LahAMO 

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

 • The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there

 •  - As you are typing a drop-down list appears. Select "Xfinity Support" from that list

 •  - An "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

3 years ago

0

walkersc

Visitor

 • 

5 Messages

3 years ago

The next morning and still trying to get to the next support tier which is very time consuming.   I am running a UDMPro as my main router and no changes there.  SIP phones, my solar system, games and other things that rely on an IPv4 ping are failing,

0

0

walkersc

Visitor

 • 

5 Messages

3 years ago

Another day has passed.  Yesterday it was determined that it is the node in our area since multiple homes are having similar issues.  First guess is this is related to new amplifiers being installed in this area.  Since the local tech was able to ping and traceroute via his scanner attached to the cable the thought is it is an account issue wrapped up with the new hardware. 

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

  1    <1 ms    <1 ms    <1 ms  (my router)
  2    29 ms    62 ms    18 ms  10.61.161.195
  3    10 ms    15 ms    11 ms  24.124.156.213
  4    11 ms    18 ms    16 ms  68.86.103.9
  5    15 ms    11 ms    11 ms  68.85.89.213
  6    12 ms    10 ms    11 ms  24.124.155.129
  7    13 ms    17 ms    13 ms  ae-501-ar01.denver.co.denver.comcast.net [96.216.22.130]
  8    16 ms    14 ms    21 ms  be-36041-cs04.1601milehigh.co.ibone.comcast.net [96.110.43.253]
  9    12 ms    15 ms    14 ms  be-3402-pe02.910fifteenth.co.ibone.comcast.net [96.110.38.126]
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

 

But a tracert to IPv6 completes.  (this is google DNS also)

Tracing route to dns.google [2001:4860:4860::8888]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  (My router)
  2   113 ms    30 ms    14 ms  2001:558:1028:6b::3
  3    11 ms     9 ms    11 ms  2001:558:1c2:262::1
  4    12 ms    10 ms    10 ms  2001:558:1c0:20::1
  5    43 ms    11 ms    11 ms  2001:558:1c0:1007::1
  6    12 ms     *       10 ms  2001:558:1c0:183::1
  7    13 ms    10 ms    11 ms  2001:558:1c0:1058::2
  8     *        *        *     Request timed out.
  9    11 ms    13 ms    10 ms  be-3302-pe02.910fifteenth.co.ibone.comcast.net [2001:558:3:19e::2]
 10    12 ms    12 ms    10 ms  as15133-2-c.nota.fl.ibone.comcast.net [2001:559::632]
 11    11 ms    11 ms    12 ms  2001:4860:0:134d::1
 12     9 ms    11 ms    10 ms  2001:4860:0:1::5839
 13    12 ms    12 ms    12 ms  dns.google [2001:4860:4860::8888]

Trace complete.

Seems like a routing issue  just past be-3202-pe02.910fifteenth.co.ibone.comcast.net but getting someone to look at that is really hard. 

We had 3 Comcast vehicles in the area but it is obvious that it is a network operations issue, not a user premise device issue or cabling or signal strength issue.

(edited)

0

0

EG

Expert

 • 

110.1K Messages

3 years ago

I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. You should get a reply here in your topic. Good luck !

0

user_ede1f6

Visitor

 • 

3 Messages

3 years ago

We must live around the same area, been having the same exact problem since the beginning of the week. 

All IPv4 ping tests end in 100% packet loss, all traceroutes star out at the same range (my last test reads be-3202-pe02.910fifteenth.co.ibone.comcast.net (96.110.38.118)). 

All IPv6 pings and traceroutes are successful though.

Spent days making sure it wasn't any of our equipment, these IPv4 packets just seem to never make it past the Denver area. 

2

walkersc

Visitor

 • 

5 Messages

@user_ede1f6​ I live in Golden and also spent one day looking at my hardware making sure it was not on my end.  I like what Xfinity/Comcast is trying to do with their "Network Enhancements" it just might not have been ready for a full production roll out.  

3 years ago

user_ede1f6

Visitor

 • 

3 Messages

@walkersc​ We live in S Denver/Lakewood, that's a good 13 miles away. That means there must be a huge number of Xfinity customers effected by this, I would assume most of whom can't as easily articulate why their Iot devices have suddenly been acting odd all week. 

3 years ago

0

forum icon

New to the Community?

Start Here