http://www.dslreports.com/forum/58-packet-loss-of-doom-FIXED-27884984 en Wed, 19 Jun 2013 02:22:50 EDT Wed, 19 Jun 2013 02:22:50 EDT http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27890660
]]> http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27890660 Tue, 08 Jan 2013 07:16:33 EDT http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27888846
Is there any way to just hack in the modem to see this stuff. I don't under stand why they had to lock it out to me. only they can log in to it. I have to trust there word on what ever they say about it, because they locked me out with the user name and password crap. ]]> http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27888846 Mon, 07 Jan 2013 15:23:42 EDT http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27888122
If so, log into it and turn off "IP Flood Protection" and "Port Scan Protection", then try again.
»www.ubeeinteractive.com/support/···nterface
»www.ubeeinteractive.com/support/···settings]]> http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27888122 Mon, 07 Jan 2013 11:44:27 EDT http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27887376
I hope they replace the modem, because I hate this ubee POS. ]]> http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27887376 Mon, 07 Jan 2013 06:24:32 EDT http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27885278 http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27885278 Sun, 06 Jan 2013 10:50:37 EDT http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27884986
Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\ >tracert www.google.com

Tracing route to www.google.com [74.125.130.99]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 39 ms 80 ms 127 ms cpe-075-189-232-001.nc.res.rr.com [75.189.232.1]

3 15 ms 16 ms 14 ms a-rtr1-10gig0-2-0-1.1116.nc.rr.com [66.26.46.57]

4 15 ms 29 ms 14 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 28 ms 30 ms 22 ms 107.14.19.20
6 23 ms 23 ms 21 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 21 ms 20 ms 20 ms 74.125.49.181
8 96 ms 24 ms 21 ms 209.85.252.80
9 24 ms 23 ms 45 ms 72.14.236.152
10 52 ms 28 ms 30 ms 72.14.235.12
11 31 ms 30 ms 30 ms 216.239.48.4
12 31 ms 30 ms 30 ms 209.85.254.247
13 * * * Request timed out.
14 30 ms 30 ms 29 ms gh-in-f99.1e100.net [74.125.130.99]

Trace complete.

C:\Users\> tracert www.foxnews.com

Tracing route to a20.g.akamai.net [24.25.26.83]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 28 ms 47 ms 20 ms cpe-075-189-232-001.nc.res.rr.com [75.189.232.1]

3 13 ms 15 ms 13 ms a-rtr1-10gig0-2-0-1.1116.nc.rr.com [66.26.46.57]

4 14 ms 13 ms 14 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 13 ms 14 ms 17 ms te-0-25.akamai-swt.akamai.net [24.25.24.158]
6 16 ms 14 ms 14 ms rdc-024-025-026-083.southeast.rr.com [24.25.26.8
3]

Trace complete.

C:\Users\> tracert www.engadget.com

Tracing route to v6v4.win.blogsmith.aol.com.aol.akadns.net [205.188.87.118]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 45 ms 41 ms 21 ms cpe-075-189-232-001.nc.res.rr.com [75.189.232.1]

3 13 ms 16 ms 14 ms a-rtr1-10gig0-2-0-1.1116.nc.rr.com [66.26.46.57]

4 14 ms 68 ms 18 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 29 ms 29 ms 30 ms 107.14.19.44
6 20 ms 20 ms 21 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 21 ms 20 ms 21 ms pop2-ash-xe-1-3-0.atdn.net [66.185.138.245]
8 21 ms 20 ms 21 ms dar2-dtc-xe-1-1-0.atdn.net [66.185.152.115]
9 22 ms 24 ms 37 ms gear2-dtc-10GigabitEthernet1-1.net.aol.com [66.1
85.150.38]
10 23 ms 21 ms 20 ms edge4-dtc-ae479.net.aol.com [149.174.32.26]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\>tracert www.youtube.com

Tracing route to youtube-ui.l.google.com [74.125.134.91]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 31 ms 20 ms 25 ms cpe-075-189-232-001.nc.res.rr.com [75.189.232.1]

3 18 ms 14 ms 14 ms a-rtr1-10gig0-2-0-1.1116.nc.rr.com [66.26.46.57]

4 12 ms 14 ms 15 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 25 ms 24 ms 53 ms 107.14.19.44
6 23 ms 20 ms 37 ms ae-2-0.pr0.dca10.tbone.rr.com [66.109.6.169]
7 20 ms 21 ms 20 ms 66.109.9.66
8 90 ms 45 ms 20 ms 209.85.252.46
9 23 ms 24 ms 24 ms 72.14.236.148
10 32 ms 35 ms 32 ms 72.14.235.10
11 32 ms 30 ms 30 ms 216.239.48.40
12 31 ms 31 ms 30 ms 72.14.239.127
13 * * * Request timed out.
14 30 ms 33 ms 30 ms gg-in-f91.1e100.net [74.125.134.91]

Trace complete.

C:\Users\> tracert www.cnn.com

Tracing route to cnn-56m.gslb.vgtf.net [157.166.248.10]
over a maximum of 30 hops:

1 2 ms 2 ms 2 ms 192.168.1.1
2 3237 ms 47 ms 46 ms cpe-075-189-232-001.nc.res.rr.com [75.189.232.1]

3 14 ms 14 ms 14 ms a-rtr1-10gig0-2-0-1.1116.nc.rr.com [66.26.46.57]

4 12 ms 15 ms 13 ms ae19.rlghncpop-rtr1.southeast.rr.com [24.93.64.0
]
5 27 ms 23 ms 29 ms 107.14.19.20
6 23 ms 20 ms 22 ms 107.14.19.65
7 47 ms 21 ms 21 ms ge-7-1-6.pr0.chi10.tbone.rr.com [66.109.9.74]
8 34 ms 26 ms 20 ms vlan90.csw4.Washington1.Level3.net [4.69.149.254
]
9 21 ms 21 ms 24 ms ae-91-91.ebr1.Washington1.Level3.net [4.69.134.1
41]
10 32 ms 30 ms 30 ms ae-2-2.ebr3.Atlanta2.Level3.net [4.69.132.85]
11 30 ms 28 ms 30 ms ae-73-73.ebr2.Atlanta2.Level3.net [4.69.148.254]

12 32 ms 31 ms 30 ms ae-2-52.edge2.Atlanta4.Level3.net [4.69.150.81]

13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.]]> http://www.dslreports.com/forum/Re-58-packet-loss-of-doom-27884986 Sun, 06 Jan 2013 06:00:00 EDT http://www.dslreports.com/forum/58-packet-loss-of-doom-FIXED-27884984 30-32 down load and .99mbs upload on the TWC test and like this on speedtest.net:



But my packet loss looks like this:








I have issues with connecting to some web sites and even a "smaller" Site like google will fail to load/take a few sec on a i7 2.4ghz QUAD core laptop. when it should load in a spit sec.

They are sending a tech out, but I don't know what to tell him.

Edit: Here is a speed test from my Verizon 4G phone:


And a pingtest:


Update: I knew it was the modem, no more 58% packet loss. now there is 0 packet loss.

Well I guess that's it then, it's fixed the end. thanks ]]> http://www.dslreports.com/forum/58-packet-loss-of-doom-FIXED-27884984 Sun, 06 Jan 2013 05:56:54 EDT