Realkone
New Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Re: Packet Loss (Outgoing) and Latency Spikes
Time Priority Description Thu Jun 14 18:31:44 2018 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=7c:bf:b1:ee:59:ce;CMTS-MAC=00:59:dc:79:04:f0;CM-QOS=1.1;CM-VER=3.0; Thu Jun 14 16:13:38 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=7c:bf:b1:ee:59:ce;CMTS-MAC=00:59:dc:79:04:f0;CM-QOS=1.1;CM-VER=3.0; Mon Jun 11 06:31:44 2018 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=7c:bf:b1:ee:59:ce;CMTS-MAC=00:59:dc:79:04:f0;CM-QOS=1.1;CM-VER=3.0; Sun Jun 10 08:50:26 2018 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=7c:bf:b1:ee:59:ce;CMTS-MAC=00:59:dc:79:04:f0;CM-QOS=1.1;CM-VER=3.0; Thu Jun 07 18:31:44 2018 Error (4) DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=7c:bf:b1:ee:59:ce;CMTS-MAC=00:59:dc:79:04:f0;CM-QOS=1.1;CM-VER=3.0; Thu Jun 07 09:17:08 2018 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=7c:bf:b1:ee:59:ce;CMTS-MAC=00:59:dc:79:04:f0;CM-QOS=1.1;CM-VER=3.0;4Views0likes0CommentsRe: Packet Loss (Outgoing) and Latency Spikes
Ping test accompanied by a tracert to one of the game servers Pinging google.com [172.217.14.174] with 32 bytes of data: Ping statistics for 172.217.14.174: Packets: Sent = 86, Received = 86, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 78ms, Maximum = 193ms, Average = 94ms Tracert 52.53.85.226 1 <1 ms <1 ms <1 ms 192.168.0.1 2 9 ms 56 ms 7 ms 10.71.20.1 3 38 ms 18 ms 16 ms ip68-4-14-64.oc.oc.cox.net [68.4.14.64] 4 8 ms 25 ms 8 ms 100.120.104.8 5 21 ms 42 ms 37 ms 68.1.1.63 6 27 ms 38 ms 23 ms ip70-167-151-90.at.at.cox.net [70.167.151.90] 7 * * * Request timed out. 8 * * * Request timed out. 9 23 ms 40 ms 23 ms 54.239.42.143 10 * * * Request timed out. 11 21 ms 77 ms 32 ms 54.240.242.78 12 22 ms 56 ms 21 ms 52.93.47.150 13 19 ms 32 ms 19 ms 52.93.47.157 14 20 ms 21 ms 21 ms 54.240.242.147 15 18 ms 21 ms 22 ms 52.93.47.88 16 * * * Request timed out. 17 * * * Request timed out.0Views0likes0CommentsRe: Packet Loss (Outgoing) and Latency Spikes
Here is a ping test accompanied by a tracert to one of the game servers Pinging google.com [172.217.14.174] with 32 bytes of data: Reply from 172.217.14.174: bytes=32 time=87ms TTL=252 Reply from 172.217.14.174: bytes=32 time=81ms TTL=252 Reply from 172.217.14.174: bytes=32 time=130ms TTL=252 Reply from 172.217.14.174: bytes=32 time=79ms TTL=252 Reply from 172.217.14.174: bytes=32 time=84ms TTL=252 Reply from 172.217.14.174: bytes=32 time=80ms TTL=252 Reply from 172.217.14.174: bytes=32 time=93ms TTL=252 Reply from 172.217.14.174: bytes=32 time=180ms TTL=252 Reply from 172.217.14.174: bytes=32 time=98ms TTL=252 Reply from 172.217.14.174: bytes=32 time=98ms TTL=252 Reply from 172.217.14.174: bytes=32 time=99ms TTL=252 Reply from 172.217.14.174: bytes=32 time=96ms TTL=252 Reply from 172.217.14.174: bytes=32 time=79ms TTL=252 Reply from 172.217.14.174: bytes=32 time=81ms TTL=252 Reply from 172.217.14.174: bytes=32 time=90ms TTL=252 Reply from 172.217.14.174: bytes=32 time=104ms TTL=252 Reply from 172.217.14.174: bytes=32 time=118ms TTL=252 Reply from 172.217.14.174: bytes=32 time=80ms TTL=252 Reply from 172.217.14.174: bytes=32 time=90ms TTL=252 Reply from 172.217.14.174: bytes=32 time=97ms TTL=252 Reply from 172.217.14.174: bytes=32 time=88ms TTL=252 Reply from 172.217.14.174: bytes=32 time=129ms TTL=252 Reply from 172.217.14.174: bytes=32 time=100ms TTL=252 Reply from 172.217.14.174: bytes=32 time=80ms TTL=252 Reply from 172.217.14.174: bytes=32 time=99ms TTL=252 Reply from 172.217.14.174: bytes=32 time=112ms TTL=252 Reply from 172.217.14.174: bytes=32 time=80ms TTL=252 Reply from 172.217.14.174: bytes=32 time=116ms TTL=252 Reply from 172.217.14.174: bytes=32 time=102ms TTL=252 Reply from 172.217.14.174: bytes=32 time=193ms TTL=252 Reply from 172.217.14.174: bytes=32 time=82ms TTL=252 Reply from 172.217.14.174: bytes=32 time=83ms TTL=252 Reply from 172.217.14.174: bytes=32 time=82ms TTL=252 Reply from 172.217.14.174: bytes=32 time=145ms TTL=252 Reply from 172.217.14.174: bytes=32 time=79ms TTL=252 Reply from 172.217.14.174: bytes=32 time=85ms TTL=252 Reply from 172.217.14.174: bytes=32 time=131ms TTL=252 Reply from 172.217.14.174: bytes=32 time=78ms TTL=252 Reply from 172.217.14.174: bytes=32 time=79ms TTL=252 Reply from 172.217.14.174: bytes=32 time=78ms TTL=252 Reply from 172.217.14.174: bytes=32 time=78ms TTL=252 Reply from 172.217.14.174: bytes=32 time=83ms TTL=252 Reply from 172.217.14.174: bytes=32 time=81ms TTL=252 Reply from 172.217.14.174: bytes=32 time=82ms TTL=252 Reply from 172.217.14.174: bytes=32 time=83ms TTL=252 Reply from 172.217.14.174: bytes=32 time=84ms TTL=252 Reply from 172.217.14.174: bytes=32 time=84ms TTL=252 Reply from 172.217.14.174: bytes=32 time=104ms TTL=252 Reply from 172.217.14.174: bytes=32 time=85ms TTL=252 Reply from 172.217.14.174: bytes=32 time=98ms TTL=252 Reply from 172.217.14.174: bytes=32 time=79ms TTL=252 Reply from 172.217.14.174: bytes=32 time=79ms TTL=252 Ping statistics for 172.217.14.174: Packets: Sent = 86, Received = 86, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 78ms, Maximum = 193ms, Average = 94ms 52.53.85.226 1 <1 ms <1 ms <1 ms 192.168.0.1 2 9 ms 56 ms 7 ms 10.71.20.1 3 38 ms 18 ms 16 ms ip68-4-14-64.oc.oc.cox.net [68.4.14.64] 4 8 ms 25 ms 8 ms 100.120.104.8 5 21 ms 42 ms 37 ms 68.1.1.63 6 27 ms 38 ms 23 ms ip70-167-151-90.at.at.cox.net [70.167.151.90] 7 * * * Request timed out. 8 * * * Request timed out. 9 23 ms 40 ms 23 ms 54.239.42.143 10 * * * Request timed out. 11 21 ms 77 ms 32 ms 54.240.242.78 12 22 ms 56 ms 21 ms 52.93.47.150 13 19 ms 32 ms 19 ms 52.93.47.157 14 20 ms 21 ms 21 ms 54.240.242.147 15 18 ms 21 ms 22 ms 52.93.47.88 16 * * * Request timed out. 17 * * * Request timed out.0Views0likes0CommentsRe: Packet Loss (Outgoing) and Latency Spikes
Setup information: Modem/Router: Motorola SURFboard SBG6782 Docsis 3.0 Wiring: Underground, residential neighborhood Affected Connections: Wired and Wireless Normal Speeds (wired): 100-120 Mbps download and 7-10 upload Computer is hardwired -> switch -> router (total length to cover is less than 100 ft.) Startup Procedure Procedure Status Comment Acquire Downstream Channel Locked Connectivity State OK Operational Boot State OK Operational Configuration File OK Security Enabled BPI+2Views0likes0CommentsPacket Loss (Outgoing) and Latency Spikes
6 Months ago I was experiencing very bad latency spikes at certain times of the day and stayed consistent (starts from 5-7pm up to 10-2amevery day). I also started playing a game called Fortnite (also 6 months ago) and I've been getting packet loss (unplayable) on the outgoing end ever since and it is severe loss at times. I have called 3 technicians, one called an ops team to replace the wire running from the node to my house. Another replaced the connector. And the third guy had put something to enhance signal levels on the node. I also had him bring out a brand new modem/router from his van and connect it for 15 minutes to test and the loss still occurred. *The coax cable is not connected to a splitter *Tried replacing the 2 in 1 router/modem with a netgear nighthawk (also not affected by puma 6) *Tried connecting straight to my surfboard *Tried different ethernet cables *Tried resetting surfboard countless times *Wireless has packet loss as well *Tried 2 other computers in the household and also a laptop8.2KViews0likes4Comments