 DrDrewSo that others may surf.
join:2009-01-28
SoCal
kudos:8
1 edit | reply to bluepoint
Re: Bad Gateway said by bluepoint:That's what I'm trying to point at the router is busy. Why was it pinging 30ms before the storm and 2000ms now? What do you think happens? Wouldn't you think gaming will be affected?
It's not 2000ms now, it's not responding now. At least that's what you said and showed originally.
If it's 2000ms then show us.
Use PingPlotter, run it for awhile, and post some graph screenshots. A single tracert with single hop times don't show enough to really give a good answer.
--
If it's important, back it up... twice. Even 99.999% availability isn't enough sometimes. |
|
1 edit | Ok I just did a tracert and it's better and it's responding. :uhh:
1: 0 ms 192.168.1.1
2: 458 ms 68.174.228.1 (cpe-68-174-228-1.si.res.rr.com)
3: 15 ms 24.164.129.218 (24-164-129-218.si.rr.com)
4: 0 ms 24.164.128.34 (tenge-0-4-0-4-nycmny1-rtr02.si.rr.com)
5: 15 ms 184.152.112.147 (bun119.nycmnytg-rtr001.nyc.rr.com)
6: 15 ms 24.29.148.250 (bun6-nycmnytg-rtr002.nyc.rr.com)
7: 15 ms 66.109.6.78 (ae-4-0.cr0.nyc30.tbone.rr.com)
8: 15 ms 107.14.19.153
9: 31 ms 4.30.135.153 (xe-11-0-2.edge2.Newark1.Level3.net)
10: 31 ms 4.69.156.30 (ae-31-51.ebr1.Newark1.Level3.net)
11: 15 ms 4.69.132.97 (ae-2-2.ebr1.NewYork1.Level3.net)
12: 15 ms 4.69.134.66 (ae-61-61.csw1.NewYork1.Level3.net)
13: 15 ms 4.69.155.6 (ae-14-60.car4.NewYork1.Level3.net)
14: 16 ms 4.53.94.218 (SPLICE-COMM.car4.NewYork1.Level3.net)
15: 15 ms 67.215.65.132 (hit-nxdomain.opendns.com)
The target host "67.215.65.132" have been reached.
Query finished.
1: 0 ms 192.168.1.1
2: 405 ms 68.174.228.1 (cpe-68-174-228-1.si.res.rr.com)
3: 0 ms 24.164.129.218 (24-164-129-218.si.rr.com)
4: 15 ms 24.164.128.34 (tenge-0-4-0-4-nycmny1-rtr02.si.rr.com)
5: 31 ms 184.152.112.147 (bun119.nycmnytg-rtr001.nyc.rr.com)
6: 15 ms 24.29.148.250 (bun6-nycmnytg-rtr002.nyc.rr.com)
7: 16 ms 107.14.19.24
8: 15 ms 66.109.6.161 (ae-1-0.pr0.nyc30.tbone.rr.com)
9: 15 ms 216.55.0.65
10: 98 ms 216.156.0.21 (vb1011.rar3.washington-dc.us.xo.net)
11: 77 ms 207.88.12.9 (te-3-0-0.rar3.atlanta-ga.us.xo.net)
12: 94 ms 207.88.12.2 (te-3-0-0.rar3.dallas-tx.us.xo.net)
13: 78 ms 216.156.0.126 (ae0d0.mcr2.sandiego-ca.us.xo.net)
14: 358 ms 216.55.27.26
15: 94 ms 69.43.169.112 (ge5-2-6509-a.castleaccess.com)
16: 109 ms 69.43.129.188
17: 93 ms 69.43.161.162
The target host "69.43.161.162" have been reached.
Query finished.
I think they are probably working on those nodes. |
|
|
|
DrDrewSo that others may surf.
join:2009-01-28
SoCal
kudos:8 | Read this:
»www.nessoft.com/kb/article/packe···-24.html
or this:
»www.nessoft.com/kb/2 |
|
