Visitor
•
4 Messages
Xfinity XB8 Wi-Fi Gaming Lag, Websites, Double NAT Confirmed, Tech Visit Unresolved. Seeking Line Fix.
Hello everyone,
I recently changed my home network setup to directly connect my PC to my Xfinity XB8 Gateway. My PC is currently connected via Wi-Fi to the gateway. Since this change, I've been experiencing severe mouse latency and instability (feeling like jitter) when playing online games, and I'm unable to access or log in to a few specific websites.
I have already contacted Xfinity about this issue, and a technician came for an on-site visit on July 30, 2025. However, the problem persisted after the visit and was not resolved.
I've performed some basic troubleshooting and network diagnostics, and have found a few key points. I'm hoping to get some help from the community or Xfinity support.
1. My Network Setup Overview:
ISP: Xfinity
Xfinity Gateway Model: XB8
Current Connection Method: PC connected via Wi-Fi to the Xfinity XB8 Gateway (PC Wi-Fi adapter model: Intel(R) Wi-Fi 6E AX210 160MHz).
Previous Setup: Xfinity Gateway (in Bridge Mode) connected to a NETGEAR XR1000 router, with the PC connected to the XR1000.
2. Issues I'm Experiencing:
Gaming Experience: Severe mouse latency, lag, and/or jitter when playing online games (e.g., Valorant, CS2).
Website Access: Unable to access or log in to a few specific websites (e.g., [If convenient, please provide examples of which websites here, such as a banking website, shopping site, etc.]).
3. Diagnostics Performed and Findings (Based on PingPlotter and Gateway Status):
Xfinity XB8 Gateway IP/DNS Status:
Local IP Address (IPv4): 10.0.0.1
Public WAN IP Address (IPv4): 69.136.XXX.XXX (Originally 69.136.205.159)
Public WAN IP Address (IPv6): 2001:558:6044:6:XXXX:XXXX:XXXX:XXXX (Originally 2001:558:6044:6:b01a:ccba:d6aa:6513)
Primary DNS Server (IPv4): 75.75.75.75
Primary DNS Server (IPv6): 2001:558:feed::1
Gateway's Local IPv6 Address: 2601:902:c000:c7ec:1236:aaff:fede:ff8f
IPv4 Double NAT Confirmation (Based on PingPlotter to 8.8.8.8):
I ran PingPlotter tracing 8.8.8.8.
The PingPlotter results show my PC's path as: Hop 1 is 10.0.0.1, and Hop 2 is 10.146.243.74.
This clearly indicates that my Xfinity XB8 Gateway is currently operating in router mode, and I am experiencing Double NAT on IPv4.
IPv6 Path Jitter (Based on PingPlotter to Google's IPv6 Address):
I ran PingPlotter tracing 2607:f8b0:4002:c11::67.
The results show my PC's path as: Hop 1: 2601:902:c000:c7ec:1236:aaff:fede:ff8f, Hop 2: 2001:558:1033:19::2.
On the IPv6 path, Hop 2 (IP: 2001:558:1033:19::2) shows a high average latency (40.03ms) and very high maximum latency (529.67ms). This indicates significant jitter and intermittent high latency on the IPv6 path.
4. Questions I Need Help With:
How can I completely resolve the Double NAT issue on IPv4? My Xfinity XB8 Gateway appears to be running in router mode, and IPv4 traffic is still subject to Double NAT even after attempting to enable Bridge Mode in the settings. I need to confirm if my gateway can be truly set to Bridge Mode to allow my devices to directly obtain a public IPv4 address. If it's not possible via the user interface, would Xfinity technical support need to perform an operation on their backend?
Is my Xfinity XB8 Gateway, acting as the primary router, experiencing Bufferbloat? Given that it lacks advanced QoS settings, could this be a primary cause of my gaming mouse latency and jitter? Since the on-site technician visit did not resolve the problem, is it possible for Xfinity to optimize my line configuration from their backend to reduce network congestion and jitter?
What can I do about the high jitter and latency on the IPv6 path? (e.g., should I try to optimize or disable IPv6 if it's impacting gaming performance?)
How can I fix the issue of being unable to access certain websites? I have tried setting public DNS (8.8.8.8 / 8.8.4.4) on the Xfinity XB8 Gateway, but I want to confirm if this is the correct troubleshooting direction.
Thank you in advance for your your help and suggestions!
Sincerely,
[Edited: "Personal Information"]
No Responses!