Internet Packet Loss Issues

@XfinityAbbie​ yes every other device  seems to get small lag spikes but in the room where i keep my ps5 , i get large and frequent lag spikes along with packet loss. The ps5 isnt the only device affected in this room as i have tried a laptop as well and get the same issues as the ps5.

Thanks for the additional information, @user_843cc5! Are you familiar with our awesome Xfinity App? There are a ton of benefits included in this one app, from viewing cameras from our Xfinity Home Security service to managing your in-home WiFi network, including devices and users! That's my favorite feature of the app for my household- managing usage time for my kids on their assigned devices and making sure I don't have unrecognized devices on my WiFi network. 

Part of the problem in my own home is that it was built in 1908, and has some unfavorable building materials when it comes to my WiFi signal. It's also two stories with a basement, and we're spread from top to bottom! I used the Xfinity App to make sure I had my modem positioned the best for my home before I ended up ordering some xFI Pods to cover our "dead spots" and improve our coverage. (Mine are 1st Gen Pods. Now, one Pod generally works to cover an entire home with your Gateway!)

For some tips on modem placement for the best speed and coverage, you can click on the little person icon in the upper left corner once in the app. From there, scroll down to the "More Resources" section, and click on the "help" option. On the next screen, you'll see a few very helpful options, with both "Xfinity internet and xFI WiFi Connection Troubleshooting" and "Improving WiFi Network Performance" being on the list. I highly recommend checking out the section on improving network performance first, just to make sure that your modem is in the best place and that some other common occurrences might not be impacting your connection.

Did you know that a fish tank can impact your WiFi?! 

You can find some additional awesome information on our Xfinity app at https://www.xfinity.com/support/articles/xfinity-xfi-overview, including several useful links to dive even deeper into all the awesome features and benefits this app can offer for you! 

Have you tried moving your PS5 to a different room to see if you still have the same problem elsewhere?

@EG​ I do not have the same issue when connected with ethernet. No lag spikes or packet loss. Here is my information from my modem. It is a motorola mg8725. 

Downstream Bonded Channels

Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected    1 Locked 256 QAM 28 579.0 9.9 37.0 71 0    2 Locked 256 QAM 1 417.0 9.9 40.1 21 0    3 Locked 256 QAM 2 423.0 9.8 40.0 26 0    4 Locked 256 QAM 3 429.0 9.8 40.1 31 0    5 Locked 256 QAM 4 435.0 9.9 40.2 25 0    6 Locked 256 QAM 5 441.0 9.8 40.2 18 0    7 Locked 256 QAM 6 447.0 9.9 40.1 27 0    8 Locked 256 QAM 7 453.0 10.0 40.3 31 0    9 Locked 256 QAM 8 459.0 10.0 40.4 32 0    10 Locked 256 QAM 9 465.0 10.0 40.3 28 0    11 Locked 256 QAM 10 471.0 10.1 40.4 20 0    12 Locked 256 QAM 11 477.0 10.1 40.4 28 0    13 Locked 256 QAM 12 483.0 10.1 40.5 30 0    14 Locked 256 QAM 13 489.0 10.1 40.3 53 0    15 Locked 256 QAM 14 495.0 10.0 40.4 51 0    16 Locked 256 QAM 15 501.0 10.0 40.5 63 0    17 Locked 256 QAM 16 507.0 10.0 40.4 39 0    18 Locked 256 QAM 17 513.0 10.0 40.6 34 0    19 Locked 256 QAM 18 519.0 10.0 39.6 56 0    20 Locked 256 QAM 19 525.0 10.1 40.0 55 0    21 Locked 256 QAM 20 531.0 10.2 31.1 2499 0    22 Locked 256 QAM 21 537.0 10.0 29.8 274148 194818    23 Locked 256 QAM 22 543.0 10.0 30.7 29730 536    24 Locked 256 QAM 23 549.0 10.0 37.5 78 0    25 Locked 256 QAM 24 555.0 10.0 40.6 68 0    26 Locked 256 QAM 25 561.0 10.0 40.8 59 0    27 Locked 256 QAM 26 567.0 10.0 39.6 49 0    28 Locked 256 QAM 27 573.0 9.9 39.7 65 0    29 Locked 256 QAM 29 585.0 9.8 38.0 80 0    30 Locked 256 QAM 30 591.0 9.7 38.7 108 0    31 Locked 256 QAM 31 597.0 9.6 40.8 102 0    32 Locked 256 QAM 32 603.0 9.5 40.9 80 0    33 Locked OFDM 193 957.0 5.3 41.3 1260359227 0

Upstream Bonded Channels

Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)    1 Locked SC-QAM 17 5120 16.4 46.5    2 Locked SC-QAM 18 5120 22.8 46.0    3 Locked SC-QAM 19 5120 29.2 46.8    4 Locked SC-QAM 20 5120 35.6 47.3

Event Log

Time    Priority    Description      00:54:10 Web Dec 14 2022   Critical(3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:54:50 Web Dec 14 2022   Critical(3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:54:51 Web Dec 14 2022   Critical(3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:54:54 Web Dec 14 2022   Critical(3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:54:54 Web Dec 14 2022   Critical(3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:55:00 Web Dec 14 2022   Critical(3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:55:01 Web Dec 14 2022   Critical(3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:55:03 Web Dec 14 2022   Critical(3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:40:36:82:3d:f8;CMTS-MAC=00:90:f0:7f:03:00;CM-QOS=1.1;CM-VER=3.1;     00:55:09 Web Dec 14 2022   Critical(3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;     00:58:20 Web Dec 14 2022   Critical(3)   UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:58:41 Web Dec 14 2022   Critical(3)   REG RSP not received;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:58:46 Web Dec 14 2022   Critical(3)   UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:58:54 Web Dec 14 2022   Critical(3)   No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:58:55 Web Dec 14 2022   Critical(3)   UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:58:55 Web Dec 14 2022   Critical(3)   No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     00:58:55 Web Dec 14 2022   Critical(3)   UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:01:05 Web Dec 14 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:02:27 Web Dec 14 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:02:42 Web Dec 14 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:04:51 Web Dec 14 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:06:27 Web Dec 14 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:08:49 Web Dec 14 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:09:42 Web Dec 14 2022   Critical(3)   UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:09:57 Web Dec 14 2022   Critical(3)   UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:11:10 Web Dec 14 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     01:19:58 Web Dec 14 2022   Critical(3)   UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical(3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;     Time Not Established   Critical(3)   UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     14:50:22 Sat Dec 17 2022   Notice(6)   Honoring MDD; IP provisioning mode = IPv6     14:50:24 Sat Dec 17 2022   Notice(6)   DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     14:50:26 Sat Dec 17 2022   Critical(3)   UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     15:07:12 Sat Dec 17 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     19:23:12 Sat Dec 17 2022   Notice(6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 21; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     19:23:23 Sat Dec 17 2022   Warning(5)   MDD message timeout;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     19:23:34 Sat Dec 17 2022   Notice(6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 21 22; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     19:23:57 Sat Dec 17 2022   Notice(6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 21; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     19:34:05 Sat Dec 17 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     09:44:15 Mon Dec 19 2022   Notice(6)   CM-STATUS message sent. Event Type Code: 20; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     09:46:44 Mon Dec 19 2022   Notice(6)   CM-STATUS message sent. Event Type Code: 22; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;     09:50:36 Mon Dec 19 2022   Critical(3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;