Author |
Topic: TRACEROUTE since Hotbrick went in suffering lag (Read 349 times) |
|
Cosworth
Full Member
Gender: 
|
 |
TRACEROUTE since Hotbrick went in suffering lag
« on: 12/03/03 at 21:57:48 » |
 Quote
|
ok here goes before the new router went in i would run a ping of 40 to 70ms to the server even when there was loads of people i very rarely went over 90ms to the server unless i was downloading
since this hotbrick router has went in my ping lowest i can get it like 250ms+ i know i have never had the problems before i also find that im being kicked offline alot more so a ran a traceroute but dunno what it means so imma post it and can you tell me if its me or you or somewhere through the line
1 <10 ms <10 ms <10 ms HotBrick_600/2_Router [10.0.0.250]
2 813 ms 828 ms 765 ms Grimsby_UBR [172.24.191.254]
3 828 ms 922 ms 703 ms nott-t2cam1-b-ge-wan51-128.inet.ntl.com [80.4.47.225]
4 688 ms 437 ms 297 ms not-t2core-b-ge-wan64.inet.ntl.com [80.1.79.89]
5 141 ms 125 ms 109 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 31 ms 16 ms 15 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
7 31 ms 31 ms 16 ms so5-0-0.loncr2.london.opentransit.net [193.251.254.141]
8 391 ms 797 ms 640 ms so3-0-0.loncr1.london.opentransit.net [193.251.128.205]
9 547 ms 391 ms 390 ms aol2.gw.opentransit.net [193.251.254.54]
10 578 ms 469 ms 515 ms accessl1-loh-s0-0-0.atdn.net [66.185.136.230]
11 * * * Request timed out.
12 1204 ms 1125 ms 875 ms ACBE571B.ipt.aol.com [172.190.87.27]
Trace complete.
ran a secont time to check for difference about 5 minutes later
1 <10 ms <10 ms <10 ms HotBrick_600/2_Router [10.0.0.250]
2 437 ms 360 ms 312 ms Grimsby_UBR [172.24.191.254]
3 47 ms 15 ms 47 ms nott-t2cam1-b-ge-wan51-128.inet.ntl.com [80.4.47.225]
4 16 ms 15 ms <10 ms not-t2core-b-ge-wan64.inet.ntl.com [80.1.79.89]
5 422 ms 391 ms 328 ms nth-bb-b-so-300-0.inet.ntl.com [62.253.188.37]
6 703 ms 453 ms 281 ms nth-bb-a-ae0-0.inet.ntl.com [62.253.185.117]
7 328 ms 219 ms 93 ms so5-0-0.loncr2.london.opentransit.net [193.251.254.141]
8 47 ms 15 ms 16 ms so3-0-0.loncr1.london.opentransit.net [193.251.128.205]
9 16 ms 15 ms 16 ms aol2.gw.opentransit.net [193.251.254.54]
10 79 ms 78 ms 15 ms accessl1-loh-s0-0-0.atdn.net [66.185.136.230]
11 * * * Request timed out.
12 219 ms 188 ms 187 ms ACBE571B.ipt.aol.com [172.190.87.27]
Trace complete.
|
|
 IP Logged |
|
|
|
Jurian
Full Member
Lillium inter spinas, The lilly among thorns
 
Gender:
|
|
Re: TRACEROUTE since Hotbrick went in suffering la
« Reply #1 on: 12/04/03 at 08:45:53 » |
Quote
|
well lol isn't the router just other crappy hubs  i haven't been kicked yet since new router is up
|
|
IP Logged |
I dream about how it's going to end,
Approaching me quickly.
Leaving a life of fear,
I only want my mind to be clear.
|
|
|
JLH
Game Creator / Administrator
Gender:
|
|
Re: TRACEROUTE since Hotbrick went in suffering la
« Reply #2 on: 12/04/03 at 10:49:33 » |
Quote
|
that's a bit of lag there on one of my net lines, which didn't last long as by hop 6 it was sorted, but by hop 8 had started again, that happens now and then, and the only thing i can do about that is to add more internet lines for peak time.
|
|
IP Logged |
Anything i post on here is subject to change at any time without notification to the board.
|
|
|
Cosworth
Full Member
Gender:
|
|
Re: TRACEROUTE since Hotbrick went in suffering la
« Reply #3 on: 12/04/03 at 20:40:30 » |
Quote
|
so its not me thats lagging then its a point in the route that is?
|
|
IP Logged |
|
|
|
Jurian
Full Member
Lillium inter spinas, The lilly among thorns
Gender:
|
|
Re: TRACEROUTE since Hotbrick went in suffering la
« Reply #4 on: 12/04/03 at 21:05:32 » |
Quote
|
that's what tracrt does pings the hub on the route. so yeah it's other hubs
|
|
IP Logged |
I dream about how it's going to end,
Approaching me quickly.
Leaving a life of fear,
I only want my mind to be clear.
|
|
|
JLH
Game Creator / Administrator
Gender:
|
|
Re: TRACEROUTE since Hotbrick went in suffering la
« Reply #5 on: 12/05/03 at 01:50:19 » |
Quote
|
more specifically, the route between my router and the local ntl ubr site, which is a 1024/256 connection, so may lag in peak time, but shouldn't last long, if anything, it'd just be a bit bursty for a bit.
|
|
IP Logged |
Anything i post on here is subject to change at any time without notification to the board.
|
|
|
|
Home 
Help 
Search 
Members 
Member Map 
Login 
Register
Reply
Notify of replies
Send Topic
Print