Bad ip:98.148.212.xxx gateway: 98.148.208.1
Bad ip:98.148.201.xxx gateway: 98.148.192.1
Bad ip:98.148.201.xxx gateway: 98.148.192.1
Good IP:98.148.215.xxx gateway: 98.148.208.1
Very Bad (127ms spikes) ip:98.148.210.xxx gateway: 98.148.208.1
Bad ip:98.148.201.xxx gateway 98.148.192.1
Good ip:98.148.201.xxx gateway 98.148.192.1
Very Good IP:98.148.247.xxx gateway IP:98.148.246.1
MacLeech The one and only Premium join:2001-07-14 SoCal kudos:3
Yet to see a pattern here...
Good and bad IPs in the same subnets.
So is there a pattern to the traceroutes between good and bad IPs? Do the bad ones all go bad in the same spot? Do the bad ones have a different return route?
also did i forget to say Power boost does not even work that good with the BAD ip's (sometimes not at all)
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 13 ms 21 ms 9 ms cpe-98-148-246-1.socal.res.rr.com [98.148.246.1]
3 8 ms 8 ms 8 ms gig1-16.pldlca1-swt1.socal.rr.com [76.167.11.41]
4 11 ms 8 ms 8 ms cpe-76-167-11-105.socal.res.rr.com [76.167.11.10
5]
5 11 ms 11 ms 9 ms gig2-2.lsanca3-rtr1.socal.rr.com [76.167.2.34]
6 13 ms 27 ms 12 ms prt32.lsanca3-rtr1.socal.rr.com [76.167.2.21]
7 * * * Request timed out.
8 30 ms 18 ms 24 ms te-1-3.car1.Tustin1.Level3.net [4.79.140.37]
9 17 ms 15 ms 18 ms ae-2-3.bar1.Tustin1.Level3.net [4.69.132.218]
10 20 ms 29 ms 17 ms ae-6-6.ebr1.LosAngeles1.Level3.net [4.69.136.202
]
11 21 ms 17 ms 19 ms ae-71-71.csw2.LosAngeles1.Level3.net [4.69.137.6
]
12 21 ms 17 ms 26 ms ae-23-79.car3.LosAngeles1.Level3.net [4.68.20.69
]
13 30 ms 39 ms 30 ms telia-level3-ge.LosAngeles1.level3.net [4.68.110
.222]
14 85 ms 83 ms 84 ms nyk-bb1-link.telia.net [80.91.252.226]
15 98 ms 88 ms 90 ms nyk-b3-link.telia.net [80.91.248.174]
16 85 ms 87 ms 85 ms nac-112088-nyk-b3.c.telia.net [213.248.83.74]
17 89 ms 86 ms 87 ms 0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
18 88 ms 89 ms 85 ms 0.e-1-1.tbr1.oct.nac.net [209.123.10.17]
19 91 ms 86 ms 94 ms vlan804.esd1.oct.nac.net [209.123.10.2]
20 87 ms 87 ms 84 ms www.dslreports.com [209.123.109.175]
Trace complete.
Tracing route to dslreports.com [209.123.109.175]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 15 ms 13 ms 11 ms cpe-98-148-192-1.socal.res.rr.com [98.148.192.1]
3 11 ms 11 ms 13 ms gig1-16.pldlca1-swt1.socal.rr.com [76.167.11.41]
4 22 ms 8 ms 22 ms cpe-76-167-11-105.socal.res.rr.com [76.167.11.10
5]
5 16 ms 13 ms 12 ms gig2-2.lsanca3-rtr1.socal.rr.com [76.167.2.34]
6 15 ms 13 ms 13 ms prt32.lsanca3-rtr1.socal.rr.com [76.167.2.21]
7 * * * Request timed out.
8 20 ms 20 ms 18 ms te-3-1.car1.Tustin1.Level3.net [4.71.104.149]
9 29 ms 17 ms 18 ms ae-2-3.bar1.Tustin1.Level3.net [4.69.132.218]
10 25 ms 20 ms 32 ms ae-6-6.ebr1.LosAngeles1.Level3.net [4.69.136.202
]
11 19 ms 32 ms 19 ms ae-81-81.csw3.LosAngeles1.Level3.net [4.69.137.1
0]
12 20 ms 22 ms 40 ms ae-33-89.car3.LosAngeles1.Level3.net [4.68.20.13
3]
13 31 ms 44 ms 31 ms telia-level3-ge.LosAngeles1.level3.net [4.68.110
.222]
14 99 ms 97 ms 97 ms nyk-bb2-link.telia.net [80.91.252.166]
15 96 ms 95 ms 99 ms nyk-b3-link.telia.net [80.91.248.178]
16 99 ms 96 ms 105 ms netaccess-114875-nyk-b3.c.telia.net [213.248.83.
186]
17 98 ms 96 ms 96 ms 0.e1-1.tbr1.ewr.nac.net [209.123.10.129]
18 99 ms 101 ms 101 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
19 98 ms 97 ms 98 ms vlan804.esd1.oct.nac.net [209.123.10.2]
20 102 ms 99 ms 99 ms www.dslreports.com [209.123.109.175]
·
·