Forum Discussion

Nbanes's avatar
Nbanes
New Contributor

Unusable Internet due to packet loss at Node

Let me begin by saying I'm at my wit's end, I've been dealing with *** service for over 2 years now and at no point has my internet been "Usable" Its constantly disconnected me due to massive amounts of packet loss and intermittent outages - this is absolutely ridiculous. I pay for Gigablast with unlimited data. download speeds are fine, but I could literally not give a *** about that, i need a STABLE AND CONSISTENT CONNECTION.

Trying to work from home? hardly a chance in hell I can even speak with clients without them hearing every other word out of my mouth, the LYING cox rep told me it was my equipment so I went out and spent 3,000 on new modems, and routers, Ethernet, etc. 

Want to steam or play gamers? Hell no, Good luck! Here's a traceroute showing dogshit internet at my node:

TRACEROUTE:
traceroute to 72.201.100.214 (72.201.100.214), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.377 ms 0.361 ms 0.357 ms
2 24.105.18.130 (24.105.18.130) 1.114 ms 1.115 ms 1.113 ms
3 137.221.105.14 (137.221.105.14) 1.109 ms 1.107 ms 1.104 ms
4 137.221.66.22 (137.221.66.22) 0.703 ms 0.709 ms 0.707 ms
5 137.221.83.86 (137.221.83.86) 636.973 ms 636.999 ms 862.526 ms
6 * * *
7 137.221.68.32 (137.221.68.32) 6.092 ms 6.077 ms 6.056 ms
8 langbbrj02-ae1.301.r2.la.cox (68.105.30.129) 6.518 ms 5.451 ms 5.430 ms
9 mcdldsrj01-ae1.0.rd.ph.cox (68.1.3.115) 17.129 ms 16.819 ms 16.804 ms
10 * * *
11 ip72-201-100-214.ph.ph.cox (72.201.100.214) 25.423 ms 25.429 ms 25.424 ms

07/05/2022 01:19:36 UTC

PING:
PING 72.201.100.214 (72.201.100.214) 56(84) bytes of data.
64 bytes from 72.201.100.214: icmp_seq=1 ttl=53 time=24.9 ms
64 bytes from 72.201.100.214: icmp_seq=2 ttl=53 time=24.1 ms
64 bytes from 72.201.100.214: icmp_seq=3 ttl=53 time=23.6 ms
64 bytes from 72.201.100.214: icmp_seq=4 ttl=53 time=22.2 ms

— 72.201.100.214 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 22.293/23.771/24.938/0.970 ms

07/05/2022 01:19:36 UTC

MTR:
Start: Sat May 7 01:19:36 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.3 0.3 0.3 0.4 0.0
2.|-- 24.105.18.130 0.0% 10 0.6 0.6 0.5 0.7 0.0
3.|-- 137.221.105.14 0.0% 10 1.0 2.9 0.7 20.5 6.2
4.|-- 137.221.66.22 0.0% 10 0.7 0.6 0.4 0.8 0.0
5.|-- 137.221.83.86 0.0% 10 187.6 509.0 43.3 1508. 415.4
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- 137.221.68.32 0.0% 10 14.3 14.7 5.9 73.9 21.0
8.|-- langbbrj02-ae1.301.r2.la.cox 0.0% 10 5.5 8.9 5.4 17.6 4.3
9.|-- mcdldsrj01-ae1.0.rd.ph.cox 0.0% 10 16.9 16.8 16.7 17.0 0.0
10.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
11.|-- ip72-201-100-214.ph.ph.cox 30.0% 10 40.7 26.7 21.8 40.7 6.4

07/05/2022 01:19:36 UTC

See specifically 11.|-- ip72-201-100-214.ph.ph.cox 30.0%  10 40.7 26.7 21.8 40.7 6.4. Reps keep coming out and telling me "Everything is fine, the signal is strong" absolutely lying sacks of garbage.

Something is wrong and it needs fixing.  

No RepliesBe the first to reply