 MacLeechThe one and onlyPremium
join:2001-07-14
SoCal
kudos:3
2 edits | reply to Anonymous_
Re: Delay on ping said by Anonymous_:ip 98.148.247.2xx i get 78 to 83ms ip 98.148.197.1xx 90 to 110ms (even in the dead of night 3am to 4 am) Pings alone don't indicate much, traceroutes are needed.
In your traceroutes where do you find the increase in latency happening? Do you have reverse traceroutes showing similar increases in latency?
Also a 10-20 ms increase in latency isn't much of a problem, it could simply be caused by a different data route, there has to be more of a customer impacting issue than that for just about any tech support from any company to really investigate the problem. |
|
 Anonymous_AnonymousPremium
join:2004-06-21
127.0.0.1
kudos:2
 ·RoadRunner Cable
·Comcast
 ·Time Warner VOIP
4 edits | let me see if i can get that working "ip" look's like someone took it :(
1 <1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 12 ms 13 ms 8 ms cpe-98-148-208-1.socal.res.rr.com [98.148.208.1]
3 8 ms 10 ms 11 ms gig1-16.pldlca1-swt1.socal.rr.com [76.167.11.41]
4 12 ms 8 ms 8 ms cpe-76-167-11-105.socal.res.rr.com [76.167.11.10
5]
5 10 ms 12 ms 13 ms gig2-2.lsanca3-rtr1.socal.rr.com [76.167.2.34]
6 12 ms 13 ms 13 ms prt22.vnnyca2-rtr2.socal.rr.com [76.167.2.13]
7 22 ms 22 ms 21 ms tge9-3.lamdca1-swt1.socal.rr.com [76.167.2.52]
8 106 ms 71 ms 29 ms tge4-0-0.lsanca1-rtr1.socal.rr.com [76.167.2.56]
9 * * * Request timed out.
10 26 ms 25 ms 24 ms te-3-1.car1.Tustin1.Level3.net [4.71.104.149]
11 25 ms 25 ms 23 ms ae-2-3.bar1.Tustin1.Level3.net [4.69.132.218]
12 27 ms 34 ms 36 ms ae-6-6.ebr1.LosAngeles1.Level3.net [4.69.136.202
]
13 27 ms 34 ms 37 ms ae-81-81.csw3.LosAngeles1.Level3.net [4.69.137.1
0]
14 27 ms 24 ms 22 ms ae-33-89.car3.LosAngeles1.Level3.net [4.68.20.13
3]
15 34 ms 35 ms 34 ms telia-level3-ge.LosAngeles1.level3.net [4.68.110
.222]
16 101 ms 105 ms 101 ms nyk-bb2-link.telia.net [80.91.252.166]
17 103 ms 103 ms 104 ms nyk-b3-link.telia.net [80.91.248.178]
18 103 ms 103 ms 103 ms netaccess-114875-nyk-b3.c.telia.net [213.248.83.
186]
19 106 ms 102 ms 102 ms 0.e1-4.tbr1.mmu.nac.net [209.123.10.101]
20 104 ms 103 ms 101 ms 0.e-1-1.tbr1.oct.nac.net [209.123.10.17]
21 105 ms 104 ms 103 ms vlan804.esd1.oct.nac.net [209.123.10.2]
22 101 ms 105 ms 103 ms www.dslreports.com [209.123.109.175]
found a "Working IP" 98.148.206.2xx
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 17 ms 8 ms 13 ms cpe-98-148-192-1.socal.res.rr.com [98.148.192.1]
3 11 ms 9 ms 8 ms gig1-16.pldlca1-swt1.socal.rr.com [76.167.11.41]
4 18 ms 8 ms 8 ms cpe-76-167-11-105.socal.res.rr.com [76.167.11.10
5]
5 9 ms 13 ms 12 ms gig2-2.lsanca3-rtr1.socal.rr.com [76.167.2.34]
6 13 ms 12 ms 13 ms prt32.lsanca3-rtr1.socal.rr.com [76.167.2.21]
7 * * * Request timed out.
8 34 ms 29 ms 17 ms te-1-3.car1.Tustin1.Level3.net [4.79.140.37]
9 76 ms 95 ms 19 ms ae-2-3.bar1.Tustin1.Level3.net [4.69.132.218]
10 31 ms 17 ms 21 ms ae-6-6.ebr1.LosAngeles1.Level3.net [4.69.136.202
]
11 27 ms 18 ms 18 ms ae-81-81.csw3.LosAngeles1.Level3.net [4.69.137.1
0]
12 19 ms 20 ms 17 ms ae-33-89.car3.LosAngeles1.Level3.net [4.68.20.13
3]
13 32 ms 28 ms 35 ms telia-level3-ge.LosAngeles1.level3.net [4.68.110
.222]
14 92 ms 86 ms 85 ms nyk-bb1-link.telia.net [80.91.252.226]
15 92 ms 85 ms 87 ms nyk-b3-link.telia.net [80.91.250.9]
16 84 ms 84 ms 85 ms nac-112088-nyk-b3.c.telia.net [213.248.83.74]
17 88 ms 84 ms 85 ms 0.e1-1.tbr1.ewr.nac.net [209.123.10.129]
18 88 ms 84 ms 86 ms 0.e1-4.tbr1.oct.nac.net [209.123.10.122]
19 89 ms 85 ms 88 ms vlan804.esd1.oct.nac.net [209.123.10.2]
20 88 ms 87 ms 88 ms www.dslreports.com [209.123.109.175]
4
boost does not work
now it does?
TTL 86400 is this normal? |
|
MacLeechThe one and onlyPremium
join:2001-07-14
SoCal
kudos:3 | So far you've shown some inconclusive data.
Do all 98. addresses have issues or is it only certain 98. addresses? Is it only with certain paths, like the one to DSLR you've shown?
In the 2 traces you've shown the routing and latency is fine on RR's network and their upstream provider Level3's network, it just jumps when it hits Telia's network. Then again after Level3's network the path changes through Telia's network and Oac.net network. That's not something RR can control, but it may also not be the issue.
How do reverse traces look?
P.S. Do you realize that your first pic shows your IP 4 times and you only blocked 1 one them out? |
|
Anonymous_AnonymousPremium
join:2004-06-21
127.0.0.1
kudos:2 Reviews:
·RoadRunner Cable
·Comcast
·Time Warner VOIP
3 edits | said by MacLeech:So far you've shown some inconclusive data. Do all 98. addresses have issues or is it only certain 98. addresses? Is it only with certain paths, like the one to DSLR you've shown? less then 10% are fine
i had to renew 10 times to get one working one
only 50% of images load
»Edit This! -- Artify© Edition #199 |
|
MacLeechThe one and onlyPremium
join:2001-07-14
SoCal
kudos:3 | said by Anonymous_:less then 10% are fine i had to renew 10 times to get one working one 1 of the 10 of the IPs YOU'VE received are "good".
Are all the addresses you've received in the same subnet or is that 1 address part of a different subnet?
Post the gateways of the "good" IPs and the gateways of "bad" IPs. |
|
Anonymous_AnonymousPremium
join:2004-06-21
127.0.0.1
kudos:2 Reviews:
·RoadRunner Cable
·Comcast
·Time Warner VOIP
| 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
|
|
MacLeechThe one and onlyPremium
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? |
|
|
|
Anonymous_AnonymousPremium
join:2004-06-21
127.0.0.1
kudos:2 Reviews:
·RoadRunner Cable
·Comcast
·Time Warner VOIP
3 edits | yea same 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]
good
13 telia-level3-ge.LosAngeles1.level3.net [4.68.110
bad
13 telia-level3-ge.LosAngeles1.level3.net [4.68.110 |
|
K PattersonPremium,MVM
join:2006-03-12
Columbus, OH
kudos:1 | Please define working/nonworking, or good vs bad. I see nothing in the least of concern in the data you've posted. |
|
