Pings

maxping · Aug 29, 2006, 18:25:51

If i get back to the low 30's i will be well happy

mrapoc · Aug 29, 2006, 18:30:36

arrrrgh its still 120+ when i used to have 20

gonna have to call tomorrow for sure

philco · Aug 29, 2006, 18:37:29

Yes, mines up and down like a yo yo now. 25-120ms.

equk · Aug 29, 2006, 18:40:59

looks like the whole network is effected now then

I've been getting it since I've been connected

hope they sort it out as quick as possible.

server I was on earlier that was pinging 30ms

Code Select

traceroute to 194.109.69.93 (194.109.69.93), 30 hops max, 40 byte packets
 1  cisco (192.168.1.1)  1.226 ms  0.683 ms  0.650 ms
 2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  21.082 ms  19.798 ms  24.241 ms
 3  * telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  21.722 ms  20.313 ms
 4  telehouse-gw.idnet.net (212.69.40.1)  20.193 ms  21.912 ms  19.806 ms
 5  lonap.he.net (193.203.5.128)  21.982 ms  23.482 ms *
 6  pos2-0.gsr12416.ams.he.net (216.66.24.158)  209.499 ms  175.293 ms  215.596 ms
 7  154.41.66.216.in-addr.arpa (216.66.41.154)  131.949 ms  141.957 ms  143.663 ms
 8  0.so-6-0-0.xr2.3d12.xs4all.net (194.109.5.5)  171.871 ms  134.972 ms  147.555 ms
 9  0.so-3-0-0.cr2.3d12.xs4all.net (194.109.5.94)  143.999 ms  135.289 ms *
10  quake3-04.xs4all.nl (194.109.69.93)  159.718 ms  129.592 ms  141.850 ms

has been like that since my last post hours ago

philco · Aug 29, 2006, 18:53:03

equk, it looks like you could have a different problem. Your tracert suggests there is a problem at he.net which is on route to the server you are trying to play on. The latency problems me and some others here are seeing start much sooner at the 1st idnet hop.

You could try contacting he.net support .... support@he.net and highlight the problem with them.

maxping · Aug 29, 2006, 18:54:51

Quote from: mrapoc on Aug 29, 2006, 18:30:36
arrrrgh its still 120+ when i used to have 20 gonna have to call tomorrow for sure

Have you done the "turn it off for 30 mins" trick its worked for me when my pings been very high.

maxping · Aug 29, 2006, 18:56:30

Quote from: philco on Aug 29, 2006, 18:53:03
Your tracert suggests there is a problem at he.net which is on route to the server you are trying to play on.

Try the tace to www.idnet.net

Heres 2 ive just done.

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 * * * Request timed out.
2 47 ms 52 ms 54 ms 212.69.63.45
3 49 ms 49 ms 48 ms 212.69.40.1
4 52 ms 57 ms 50 ms 212.69.63.1
5 62 ms 58 ms 49 ms 212.69.36.10

1 * * * Request timed out.
2 54 ms 51 ms 49 ms 212.69.63.45
3 49 ms 49 ms 49 ms 212.69.40.1
4 52 ms 52 ms 50 ms 212.69.63.1
5 49 ms 49 ms 48 ms 212.69.36.10

equk · Aug 29, 2006, 19:33:45

Quote from: philco on Aug 29, 2006, 18:53:03
equk, it looks like you could have a different problem. Your tracert suggests there is a problem at he.net which is on route to the server you are trying to play on. The latency problems me and some others here are seeing start much sooner at the 1st idnet hop.

You could try contacting he.net support .... support@he.net and highlight the problem with them.

I thought that myself but my other post got closed and I got told to post in this thread

Also the ping seemed to change at the same time as other people. So possibly is an idnet issue, not sure

but I do know there are people from the uk not having the same problems as loads of peeps I know are on the server pinging 30ms

equk · Aug 29, 2006, 19:35:47

Quote from: maxping on Aug 29, 2006, 18:56:30
Quote from: philco on Aug 29, 2006, 18:53:03
Your tracert suggests there is a problem at he.net which is on route to the server you are trying to play on.

Try the tace to www.idnet.net

Heres 2 ive just done.

Tracing route to www.idnet.net [212.69.36.10]
over a maximum of 30 hops:

1 * * * Request timed out.
2 47 ms 52 ms 54 ms 212.69.63.45
3 49 ms 49 ms 48 ms 212.69.40.1
4 52 ms 57 ms 50 ms 212.69.63.1
5 62 ms 58 ms 49 ms 212.69.36.10

1 * * * Request timed out.
2 54 ms 51 ms 49 ms 212.69.63.45
3 49 ms 49 ms 49 ms 212.69.40.1
4 52 ms 52 ms 50 ms 212.69.63.1
5 49 ms 49 ms 48 ms 212.69.36.10

here's my trace to idnet

Code Select

traceroute to www.idnet.net (212.69.36.10), 30 hops max, 40 byte packets
 1  cisco (192.168.1.1)  1.313 ms  0.683 ms  0.656 ms
 2  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  21.824 ms  25.708 ms *
 3  telehouse-bb-gw1-vpdn.idnet.net (212.69.63.45)  20.308 ms  21.966 ms  21.950 ms
 4  telehouse-gw.idnet.net (212.69.40.1)  22.046 ms  22.005 ms  22.005 ms
 5  * redbus-gw-fa0-0-1003.idnet.net (212.69.63.1)  26.744 ms  20.747 ms
 6  www.idnet.net (212.69.36.10)  21.979 ms  22.652 ms  22.058 ms

can someone do a traceroute to the ip I posted? just to see

philco · Aug 29, 2006, 19:46:14

from my idnet connection (which btw is back to normal again)

Code Select

Tracing route to quake3-04.xs4all.nl [194.109.69.93]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2    22 ms    26 ms    22 ms  telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
  3    23 ms   167 ms    22 ms  telehouse-gw.idnet.net [212.69.40.1]
  4    21 ms    22 ms    22 ms  lonap.he.net [193.203.5.128]
  5   129 ms   123 ms   123 ms  pos2-0.gsr12416.ams.he.net [216.66.24.158]
  6   133 ms   137 ms   128 ms  154.41.66.216.in-addr.arpa [216.66.41.154]
  7   111 ms   111 ms   111 ms  0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
  8   125 ms   124 ms   234 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
  9   138 ms   129 ms   129 ms  quake3-04.xs4all.nl [194.109.69.93]

from a bt connection ....

Code Select

Tracing route to quake3-04.xs4all.nl [194.109.69.93]
over a maximum of 30 hops:

  1    12 ms    11 ms    10 ms  217.32.96.250
  2    10 ms    14 ms    11 ms  213.123.110.161
  3    12 ms    12 ms    11 ms  217.41.176.5
  4    11 ms    20 ms    26 ms  217.41.176.118
  5    10 ms    18 ms    10 ms  217.41.176.54
  6    11 ms    18 ms    10 ms  217.47.73.99
  7    10 ms    18 ms    12 ms  core1-pos14-3.sheffield.ukcore.bt.net [217.32.17
1.197]
  8    13 ms    19 ms    25 ms  core1-pos7-0.manchester.ukcore.bt.net [62.6.204.
177]
  9    17 ms    18 ms    30 ms  core1-pos4-0.ealing.ukcore.bt.net [62.6.204.193]
 10    17 ms    19 ms    29 ms  core1-pos1-0-0.telehouse.ukcore.bt.net [194.74.65.113]
 11    18 ms    19 ms    23 ms  ldn-s2-rou-1002.UK.eurorings.net [195.66.224.54]
 12    19 ms    20 ms    23 ms  ldn-s2-rou-1001.UK.eurorings.net [134.222.231.61]
 13    18 ms    19 ms    20 ms  134.222.230.121
 14    31 ms    26 ms    27 ms  obl-rou-1021.NL.eurorings.net [134.222.231.173]
 15    28 ms    30 ms    31 ms  asd2-rou-1002.NL.eurorings.net [134.222.231.202]
 16    29 ms   177 ms   228 ms  asd2-rou-1001.NL.eurorings.net [134.222.231.194]
 17    29 ms    28 ms    28 ms  asd2-rou-1011.NL.eurorings.net [134.222.231.250]
 18    36 ms    36 ms    33 ms  134.222.97.18
 19    29 ms    26 ms    27 ms  0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
 20    27 ms    27 ms    27 ms  quake3-04.xs4all.nl [194.109.69.93]

as you can see, you are just on a bad route to that server. Not much you can do other than contacting he.net and letting them know. They may not be aware there is a problem.

philco · Aug 29, 2006, 19:47:37

(sry double post. Please delete)

equk · Aug 29, 2006, 19:50:03

well looking at the he.net site it seems they are in america?

Hurricane Electric
760 Mission Court
Fremont, CA 94539

Quote from: idnet supportGeographic location does not play much of a role in determining how packets
are routed. We will deliver traffic via the shortest path (fewest number of
networks) possible. I can see from your posts that this particular problem
has now resolved itself? Please let me know if this is not the case.

fastest route to the NL is to california in america?

philco · Aug 29, 2006, 19:52:17

Thats just their head office i expect.

equk · Aug 29, 2006, 19:56:16

it is in america san jose

IP ADDRESS: 193.203.5.128 (lonap.he.net)
COUNTRY REGION CITY FLAG
UNITED STATES CALIFORNIA SAN JOSE

ARGH!!!!

check here - http://webtools.live2support.com/misc_locate_ip_address.php

so it seems to be a routing issue as I suggested in my original post

CatMangler · Aug 29, 2006, 20:01:46

Quote from: philco on Aug 29, 2006, 18:10:39
same, here. About 5.30pm - 5.45pm things are well again. About the same time every day.

Are you serious!!, I'm on holiday most of the week, so gamings a lost cause during the day!!!!!!!!!!!!!

philco · Aug 29, 2006, 20:03:59

inetnum: 193.203.5.0 - 193.203.5.255
netname: LONDON-LONAP
descr: LoNAP Peering Point
descr: London
country: GB
admin-c: AS8330-RIPE
tech-c: AS8330-RIPE
status: ASSIGNED PI
mnt-by: AS8330-MNT
mnt-by: RIPE-NCC-HM-PI-MNT
mnt-lower: RIPE-NCC-HM-PI-MNT
source: RIPE # Filtered

role: LoNAP Tech contact
address: Telehouse Docklands, London

definitely in london. you wouldn't be pinging 22ms to lonap.he.net if it was in the US.

equk · Aug 29, 2006, 20:11:40

Quote from: philco on Aug 29, 2006, 20:03:59
inetnum: 193.203.5.0 - 193.203.5.255
netname: LONDON-LONAP
descr: LoNAP Peering Point
descr: London
country: GB
admin-c: AS8330-RIPE
tech-c: AS8330-RIPE
status: ASSIGNED PI
mnt-by: AS8330-MNT
mnt-by: RIPE-NCC-HM-PI-MNT
mnt-lower: RIPE-NCC-HM-PI-MNT
source: RIPE # Filtered

role: LoNAP Tech contact
address: Telehouse Docklands, London

definitely in london. you wouldn't be pinging 22ms to lonap.he.net if it was in the US.

hmm

It's still very strange how it's such a high ping. Also seems to be a routing issue as looking at the BT one it is a lot faster. 26ms in comparison to 130ms?

still not very happy

it picks up the next one as new york?

IP ADDRESS: 216.66.24.158
COUNTRY REGION CITY FLAG
UNITED STATES NEW YORK NEW YORK

equk · Aug 29, 2006, 20:30:40

I just spoke to simon and he has put my mind as ease, hopefully they will sort routing out

he also explained about my phone line etc.

Also the site that checks is probably checking the company resistration address.

Hopefully by the time the 10days is over the routing aswell as my connection will be a lot more stable.

Excellent support tho

mrapoc · Aug 29, 2006, 20:44:19

i think my pings are back to normal for the time being - can some1 give me an ip to ping which they are getting normal pings on?

maxping · Aug 29, 2006, 20:58:15

EQUK here you go.

Tracing route to 194.109.69.93 over a maximum of 30 hops

1 * * * Request timed out.
2 49 ms 49 ms 48 ms 212.69.63.45
3 49 ms 49 ms 49 ms 212.69.40.1
4 48 ms 49 ms 48 ms 193.203.5.128
5 126 ms 127 ms 126 ms 216.66.24.158
6 182 ms 173 ms 178 ms 216.66.41.154
7 169 ms * 174 ms 194.109.5.5
8 186 ms 165 ms 169 ms 194.109.5.94
9 183 ms 177 ms 183 ms 194.109.69.93

mrapoc · Aug 29, 2006, 20:59:35

QuoteTracing route to quake3-04.xs4all.nl [194.109.69.93]
over a maximum of 30 hops:

1 55 ms 99 ms 199 ms speedtouch.lan [192.168.1.254]
2 23 ms 23 ms 23 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 23 ms 23 ms 24 ms telehouse-gw.idnet.net [212.69.40.1]
4 25 ms 24 ms 25 ms lonap.he.net [193.203.5.128]
5 81 ms 82 ms 83 ms pos2-0.gsr12416.ams.he.net [216.66.24.158]
6 131 ms 134 ms 124 ms 154.41.66.216.in-addr.arpa [216.66.41.154]
7 132 ms 152 ms 135 ms 0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
8 167 ms 150 ms 150 ms 0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
9 134 ms 138 ms 130 ms quake3-04.xs4all.nl [194.109.69.93]

Trace complete.

equk · Aug 29, 2006, 21:07:52

cool

guess that confirms it is a routing problem with idnet

maxping · Aug 29, 2006, 21:16:16

I have done another including the details

1 * * * Request timed out.
2 49 ms 54 ms 58 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 52 ms 51 ms 51 ms telehouse-gw.idnet.net [212.69.40.1]
4 62 ms 63 ms 61 ms lonap.he.net [193.203.5.128]
5 144 ms 139 ms 135 ms pos2-0.gsr12416.ams.he.net [216.66.24.158]
6 159 ms 158 ms 182 ms 154.41.66.216.in-addr.arpa [216.66.41.154]
7 299 ms 176 ms 166 ms 0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
8 176 ms 171 ms 173 ms 0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
9 185 ms 187 ms 186 ms quake3-04.xs4all.nl [194.109.69.93]

browney · Aug 30, 2006, 14:10:20

Tracing route to quake3-04.xs4all.nl [194.109.69.93]
over a maximum of 30 hops:

1 4 ms <1 ms <1 ms www.routerlogin.com [192.168.0.1]
2 32 ms 28 ms 29 ms telehouse-bb-gw1-vpdn.idnet.net [212.69.63.45]
3 30 ms 32 ms 32 ms telehouse-gw.idnet.net [212.69.40.1]
4 31 ms 32 ms 49 ms redbus-gw-fa0-0-1003.idnet.net [212.69.63.1]
5 49 ms 51 ms 48 ms ams-ix.sara.xs4all.net [195.69.144.48]
6 48 ms 51 ms 49 ms 0.so-6-0-0.xr2.3d12.xs4all.net [194.109.5.5]
7 47 ms 47 ms 54 ms 0.so-3-0-0.cr2.3d12.xs4all.net [194.109.5.94]
8 46 ms 46 ms 47 ms quake3-04.xs4all.nl [194.109.69.93]

Trace complete.

equk · Aug 30, 2006, 14:26:22

yer seems ok atm, from what Simon said last night it seems the network the connection is routed through gets overloaded. Which is why it's ok at certain times of the day.

Still 46ms when it's a good time of the day tho (bit higher than 26-30ms)