Contributor
•
104 Messages
XB1O Yet again!!
So, after trying to chase an XB10 gateway down for a year it looks like soon I shall be able to get one here in the Twin cities of Mpls/St Paul according to what Xfinity is bombarding my Facebook account with. The sad thing is the local store all admit they have no clue on speed upgrades etc. and tell me they are lucky to see An XB8 gateway. So, if they can't help and you can't get an agent via Chat or get an agent in India :( On the phone. How does one get one of these???
And yes, my area is ready for Docsis 4 as all the Nodes are in place which is easy to see as everything is mostly above ground so all the nice new shiny equipment is easy to spot up there on the lines and you can see all the lines have been run to all the connections on the Nodes, and the Green power boxes supply power for the nodes on the poles are in place. Plus, we are having about 3 scheduled outages a week early in the morning so they can get stuff done for the last month. Which according to my logs give me uncorrectable code words.
But yet they advertise it but there is no way of finding out more as the page you get to when you click on more info just skates around how to get anything.
XfinityAirelle
Official Employee
•
2.5K Messages
8 days ago
@Aceq2jot
Hey there—first off, we really appreciate how much you've been keeping an eye on this and staying in the loop. You clearly know your stuff when it comes to the network upgrades in the Twin Cities, and honestly, it’s awesome to see how dialed-in you are with everything from DOCSIS 4.0 to spotting node installations on the poles. You’ve definitely done your homework—and we see you!
Now, let’s talk XB10—because good news: as of April 15, the XB10 Gateway is officially available for customers adding our X-Class Internet tiers starting at X-500 speeds and above. This includes X-500 and X-Gig tiers, which are now eligible for a Getting Started Kit (GSK) to be shipped directly to your door—so no need to go on a scavenger hunt at your local store. We do not recommend heading into a retail store for one because inventory there is extremely limited and primarily set aside for specific swap scenarios.
So if you're looking to make the move to X-500 or higher, you can request the XB10 with your shipped kit and do a self-install when it’s convenient for you—no need for a pro install unless you're going with X-2Gig, which still requires a technician.
What makes the XB10 so exciting is that it’s built with WiFi 7 technology. That means up to 4x faster speeds, wider channels, and way better performance when you’ve got multiple devices online. Whether you're streaming 4K, gaming, or running a smart home—it’s made to handle it all without breaking a sweat.
One thing to note: existing customers who already have X-Class Internet and the two-box solution (XB8 + XD4) aren’t being proactively swapped to the XB10 right now. But if you’re upgrading your speed tier or starting new service at X-500 or higher, you're eligible.
We hope this information helps. Please let us know if there are additional questions. We are happy to assist!
2
0
Aceq2jot
Contributor
•
104 Messages
4 days ago
So today due to internet issues i ran a trace route to google. I was just curious how the results look.
Tracing route to google.com [2607:f8b0:4009:817::200e]
over a maximum of 30 hops:
1 2 ms 4 ms 4 ms [Edited: Personal Information]
2 12 ms 11 ms 14 ms 2[Edited: Personal Information]
3 12 ms 11 ms 14 ms po-316-400-rur402.roseville.mn.minn.comcast.net [2001:558:32:8::1]
4 10 ms 13 ms 12 ms po-400-xar02.roseville.mn.minn.comcast.net [2001:558:30:2101::1]
5 * * * Request timed out.
6 * 20 ms * be-1101-ar-sp01.roseville.mn.minn.comcast.net [2001:558:30:ff::1]
7 21 ms 24 ms 26 ms be-37011-cs21.350ecermak.il.ibone.comcast.net [2001:558:3:2c0::1]
8 32 ms 23 ms 25 ms be-2113-pe13.350ecermak.il.ibone.comcast.net [2001:558:3:15::2]
9 25 ms 22 ms 20 ms 2001:559::542
10 19 ms 20 ms 20 ms 2607:f8b0:8313::1
11 * * * Request timed out.
12 25 ms 20 ms 19 ms 2001:4860:0:1::86fc
13 23 ms 28 ms 22 ms 2001:4860::c:4002:a0bf
14 39 ms 21 ms 22 ms 2001:4860::1:4000:d31c
15 * * * Request timed out.
16 22 ms 20 ms 22 ms 2001:4860:0:1::5671
17 19 ms 31 ms 20 ms ord38s28-in-x0e.1e100.net [2607:f8b0:4009:817::200e]
So, I gave it ten minutes and ran it again. And the results are below. It would appear to me that the hiccup is at the main Xfinity connection in Roseville.
Tracing route to google.com [2607:f8b0:4009:817::200e]
over a maximum of 30 hops:
1 2 ms 3 ms 1 ms [Edited: Personal Information]
2 16 ms 10 ms 10 ms [Edited: Personal Information]
3 15 ms 10 ms 11 ms po-316-400-rur402.roseville.mn.minn.comcast.net [2001:558:32:8::1]
4 16 ms 21 ms 22 ms po-400-xar02.roseville.mn.minn.comcast.net [2001:558:30:2101::1]
5 * * 18 ms be-300-ar-in01.roseville.mn.minn.comcast.net [2001:558:30:f1::1]
6 * * 15 ms be-1101-ar-sp01.roseville.mn.minn.comcast.net [2001:558:30:ff::1]
7 * 25 ms 23 ms be-37011-cs21.350ecermak.il.ibone.comcast.net [2001:558:3:2c0::1]
8 29 ms 21 ms 21 ms be-2113-pe13.350ecermak.il.ibone.comcast.net [2001:558:3:15::2]
9 * * 24 ms 2001:559::542
10 21 ms 27 ms 24 ms 2607:f8b0:8313::1
11 27 ms * 23 ms 2001:4860:0:1::572e
12 52 ms 29 ms 26 ms 2001:4860:0:1::86fc
13 21 ms 23 ms 24 ms 2001:4860::c:4002:a0bf
14 22 ms 20 ms 24 ms 2001:4860::1:4000:d31c
15 * * * Request timed out.
16 25 ms 20 ms 22 ms 2001:4860:0:1::5671
17 36 ms 26 ms 22 ms ord38s28-in-x0e.1e100.net [2607:f8b0:4009:817::200e]
Trace complete.
I ran a third for good luck.
Tracing route to google.com [2607:f8b0:4009:801::200e]
over a maximum of 30 hops:
1 4 ms 3 ms 2 ms [Edited: Personal Information]
2 16 ms 11 ms 11 ms [Edited: Personal Information]
3 18 ms 12 ms 13 ms po-316-400-rur402.roseville.mn.minn.comcast.net [2001:558:32:8::1]
4 12 ms 11 ms 15 ms po-400-xar02.roseville.mn.minn.comcast.net [2001:558:30:2101::1]
5 * * * Request timed out.
6 * * * Request timed out.
7 * 26 ms 24 ms be-37041-cs24.350ecermak.il.ibone.comcast.net [2001:558:3:2c3::1]
8 22 ms 22 ms 21 ms be-2413-pe13.350ecermak.il.ibone.comcast.net [2001:558:3:18::2]
9 26 ms * * 2001:559::542
10 26 ms 26 ms 26 ms 2607:f8b0:8320::1
11 25 ms 21 ms 22 ms 2001:4860:0:1::5686
12 27 ms 22 ms 22 ms 2001:4860:0:1::96ba
13 24 ms 22 ms 21 ms 2001:4860::c:4002:a0c1
14 * * * Request timed out.
15 24 ms * * 2001:4860:0:1::5bf7
16 20 ms 21 ms 20 ms 2001:4860:0:1::ac1
17 22 ms 20 ms 20 ms ord37s51-in-x0e.1e100.net [2607:f8b0:4009:801::200e]
Trace complete.
(edited)
0
0
Aceq2jot
Contributor
•
104 Messages
4 days ago
Also, I have to wonder if my DCHP lease times have to do anything with all of my problems as IPV4 lease time is 2 days and it seems I don't have anything for my IPV6 which is weird
.
1
0
Aceq2jot
Contributor
•
104 Messages
2 days ago
So, this afternoon a tech stopped out and tested everything and replaced the XB8 modem. Sadly, nothing has improved. I ran a trace route and then pinged the first four Ip addresses in that for a time 5 minutes. The results are below. Any insights would be helpful.
Ping statistics for XXXX:XXX:XX:f1::1:
Packets: Sent = 177, Received = 177, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 1542ms, Average = 31ms
Ping statistics for XXXX:447:cf7c:9130:XXXX:e3ff:XXX4:21ab:
Packets: Sent = 222, Received = 222, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 191ms, Average = 6ms
Ping statistics for XXXX:XXXX:XXXX:61::3:
Packets: Sent = 195, Received = 195, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 10ms, Maximum = 378ms, Average = 25ms
Ping statistics for XXXX:XXX:cf7c:XXXXX:XXXX:e3ff:fea4:21ab:
Packets: Sent = 172, Received = 172, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 392ms, Average = 13ms
0
0
Aceq2jot
Contributor
•
104 Messages
1 day ago
I think I have to thank the mods on here as it seems that something on the back end changed after I was still having problems with the old modem running Software version 7.6p9s2 as I am now on7.9p15s1 and things are running great both hardwired and wireless I am hitting speeds of one gig (Small House) and tracert is not hanging up on any local jumps and I have a ipv6 address again. So hopefully everything is now good. Thanks to the staff as I think they did all the work behind the scene.
4
0