NY7737's profile

Frequent Visitor

 • 

15 Messages

Monday, May 11th, 2026 4:30 AM

Issues with disconnecting while playing any battle.net game

Hello,

I am experiencing persistent disconnect/reconnect issues specifically with Blizzard games/services on my personally owned ARRIS SURFboard G54-B48D gateway on Xfinity service in [Edited: "Personal Information"].

The issue primarily affects Diablo IV and World of Warcraft. Other internet services remain stable during the issue.

Symptoms:

Diablo IV enters a “Reconnecting to Diablo IV” state after roughly 30–60 minutes of gameplay.
Reconnect state does not recover and eventually results in:
disconnect to character select OR
full game crash/closure.
During these events, the Battle.net launcher also briefly reloads or appears to lose connection temporarily.
Discord, YouTube, browsing, downloads, and general internet remain functional during the issue.
In WoW, abilities sometimes grey out and stop responding as if the server connection stalled.
Ping tests to Blizzard and 1.1.1.1 remain stable during normal operation with no major spikes or packet loss observed.

Hardware / Network Info:

Gateway: ARRIS SURFboard G54-B48D
Connection: Wired Ethernet
Ethernet cable tested/replaced
PC NIC supports gigabit+
Xfinity 1300 Mbps plan
Peak download speeds around 100 MB/s observed
No Wi-Fi usage during testing
No background downloads/streaming during gameplay
No overlays running
Battle.net hardware acceleration disabled

Troubleshooting already performed:

Rebooted modem/router and PC multiple times.
Disabled IPv6 on PC and gateway-related IPv6 features.
Tested different firewall settings on G54:
Medium
Custom
Low security
UPnP enabled.
Verified bridge mode was disabled.
Changed DNS to Cloudflare:
1.1.1.1
1.0.0.1
Flushed DNS cache with:
ipconfig /flushdns
Verified issue occurs without other devices using bandwidth.
Verified issue occurs without overlays/background apps.
Tested with ExitLag:
Session stability improved noticeably (sometimes extending past 1 hour)
However reconnect/disconnect issue still eventually occurred.
Discord and general internet remain stable while Blizzard services disconnect/reload.

Observed behavior strongly suggests:

possible NAT/session persistence issue,
firmware-level UDP session handling problem,
or routing/session instability affecting Blizzard traffic specifically.

Because the issue persists across DNS, IPv6, firewall, and local PC troubleshooting — and because ExitLag measurably improves session duration — I am requesting investigation into:

possible firmware updates for the ARRIS G54-B48D,
known UDP/NAT session handling issues,
or compatibility issues affecting Blizzard/Battle.net services.

My current firmware is 

Firmware Version: AC01.02.012_022625_G5X.04.20.122
SDK: QCA_Networking_2022.SPF.12.2 CS

I would also appreciate confirmation whether newer firmware is available for this gateway on Xfinity’s network.

Oldest First
Selected Oldest First

Official Employee

 • 

626 Messages

3 days ago

 

NY7737, hello there and thanks for reaching out sharing that information as it is very helpful. I do want to apologize about the experience you're having. I'd love to do some troubleshooting to see what we can do further. When did you start experiencing these troubles? 

 

Frequent Visitor

 • 

15 Messages

I've noticed the issues with world of warcraft about 3 months ago.
the issue was more noticeable with diablo 4 which i started playing again about 2 weeks ago.
I've been monitoring my connection with other things and noticed that it only drops for those two, or any other game related to blizzard

(edited)

Official Employee

 • 

626 Messages

 

NY7737, ahh ok, I've heard that before. I'd assume it is usually during online multiplayer game play? 

 

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

Frequent Visitor

 • 

15 Messages

yes, though even if im not in a party the issue still persists.
im assuming its an issue with my connection to their servers. but im not 100% sure.
after doing a lot of different tests on my end, i decided to reach out

Official Employee

 • 

3.3K Messages

 

NY7737 Have you set up any port forwarding at this time to see if it helps with the 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

Frequent Visitor

 • 

15 Messages

3 days ago

yes, I've tried with port forward on and off.
the ports i used were
TCP - 1119, 3724, 6113
UDP - 1119, 3478-3479, 5060, 5062, 6250

it doesnt seem to help

Official Employee

 • 

3.3K Messages

Let's see what we can find on our end with the device to see if we can help NY7737

 

Can you send us a direct message with your full name, name of account holder (if different), and service address please?

To send a "Direct Message" to Xfinity Support:

Click "Sign In" If necessary

Click the "Direct Messaging" icon (speech bubble)

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

Visitor

 • 

1 Message

1 hour ago

I have also been experiencing this issue for a few weeks now -- it is making playing any Blizzard game impossible. I am curious if you are located in Florida. 

I have run WinMTR traces that show 1% packet loss and latency spikes up to 105ms starting at the very first Comcast hop (96.120.98.49). This indicates an issue with the drop to my house or the neighborhood node.
My local gateway (Hop 1) shows 0% loss and sub-1ms latency over 1,400 packets, so the issue is definitely on the ISP side of the demarc. Given that the loss is consistent across the entire trace starting at the CMTS, I suspect there is noise or ingress on the line that is causing intermittent T3 timeouts.

Curious if you have found a solution or heard back from Xfinity on this.

forum icon

New to the Community?

Start Here