Ping or Trace Route This IP address

fluffykittenlover · Apr 2, 2017

>>> 129.232.229.238 <<< it is a south african left 4 Dead 2 Server hosted At Hetzner

Rickster · Apr 2, 2017

C:\Windows\system32>ping 129.232.229.238

Pinging 129.232.229.238 with 32 bytes of data:
Reply from 129.232.229.238: bytes=32 time=28ms TTL=54
Reply from 129.232.229.238: bytes=32 time=28ms TTL=54
Reply from 129.232.229.238: bytes=32 time=28ms TTL=54
Reply from 129.232.229.238: bytes=32 time=27ms TTL=54

Ping statistics for 129.232.229.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 28ms, Average = 27ms

Tracing route to 129.232.229.238 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.0.1
2 * * * Request timed out.
3 33 ms 30 ms 30 ms jhb-up7.ip.adsl.co.za [169.1.5.6]
4 25 ms 24 ms 24 ms jhb-net1.ip.adsl.co.za [169.1.5.52]
5 25 ms 24 ms 24 ms seacom.ixp.joburg [196.60.8.188]
6 26 ms 24 ms 25 ms xe-1-0-0-0.er-02-jnb.za.seacomnet.com [105.16.29.10]
7 24 ms 24 ms 24 ms ae-2-37.customer-gw-mfn.er-02-jnb.za.seacomnet.com [105.22.40.26]
8 26 ms 47 ms 25 ms 196.216.138.137
9 27 ms 28 ms 27 ms 196.192.191.246
10 28 ms 34 ms 34 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
11 41 ms 32 ms 38 ms row-access-switch1-row17-18.jnb1.host-h.net [197.189.193.46]
12 27 ms 27 ms 27 ms 129.232.229.238

Trace complete.

Johnatan56 · Apr 2, 2017

Code:

Pinging 129.232.229.238 with 32 bytes of data:
Reply from 129.232.229.238: bytes=32 time=27ms TTL=49
Reply from 129.232.229.238: bytes=32 time=27ms TTL=49
Reply from 129.232.229.238: bytes=32 time=26ms TTL=49
Reply from 129.232.229.238: bytes=32 time=26ms TTL=49

Ping statistics for 129.232.229.238:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 26ms, Maximum = 27ms, Average = 26ms

Yes? Johannesburg?

Rickster · Apr 18, 2017

dubberdottle said:
on my DSL i use to get less than 40 milliseconds connecting to that left 4 dead 2 Server now its spiked to over 90ms

Sum ting wong.

d7e7r7 · Apr 18, 2017

Code:

Pinging 129.232.229.238 with 32 bytes of data:

Reply from 129.232.229.238: bytes=32 time=22ms TTL=49
Reply from 129.232.229.238: bytes=32 time=31ms TTL=49
Reply from 129.232.229.238: bytes=32 time=24ms TTL=49
Reply from 129.232.229.238: bytes=32 time=23ms TTL=49

Ping statistics for 129.232.229.238:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 31ms, Average = 25ms

Code:

Tracing route to 129.232.229.238 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  164.88.57.1
  2    <1 ms    <1 ms    <1 ms  164.88.41.36
  3     1 ms     2 ms    <1 ms  62.5.100.33
  4    19 ms    20 ms    18 ms  62.5.100.61
  5    22 ms    26 ms    26 ms  62.5.100.62
  6    23 ms    28 ms    34 ms  164.88.128.12
  7    21 ms    20 ms    28 ms  host-61-14-48-1.eu.bt.net [61.14.48.1]
  8    32 ms    21 ms    20 ms  61.14.51.8
  9    21 ms    25 ms    26 ms  195.206.70.203
 10    20 ms    23 ms    22 ms  is.ixp.joburg [196.60.8.126]
 11    28 ms    34 ms    37 ms  168.209.1.192
 12    31 ms    31 ms    26 ms  168.209.88.214
 13    35 ms    26 ms    26 ms  196.34.90.124
 14    24 ms    28 ms    62 ms  196.34.90.125
 15    26 ms    23 ms    28 ms  core.xe-0-0-1-gp-sm-het-dce-2.za.africainx.net [
41.84.12.95]
 16    25 ms    23 ms    23 ms  41-66-132-246-f6.hetzner-jhb-ip4-gw.africainx.ne
t [41.66.132.246]
 17    23 ms    23 ms    33 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
 18    30 ms    23 ms    28 ms  row-access-switch1-row17-18.jnb1.host-h.net [197
.189.193.46]
 19    24 ms    23 ms    23 ms  129.232.229.238

Trace complete.

Dizzle · Apr 18, 2017

d7e7r7 said:

Code:

Pinging 129.232.229.238 with 32 bytes of data:

Reply from 129.232.229.238: bytes=32 time=22ms TTL=49
Reply from 129.232.229.238: bytes=32 time=31ms TTL=49
Reply from 129.232.229.238: bytes=32 time=24ms TTL=49
Reply from 129.232.229.238: bytes=32 time=23ms TTL=49

Ping statistics for 129.232.229.238:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 22ms, Maximum = 31ms, Average = 25ms

Code:

Tracing route to 129.232.229.238 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  164.88.57.1
  2    <1 ms    <1 ms    <1 ms  164.88.41.36
  3     1 ms     2 ms    <1 ms  62.5.100.33
  4    19 ms    20 ms    18 ms  62.5.100.61
  5    22 ms    26 ms    26 ms  62.5.100.62
  6    23 ms    28 ms    34 ms  164.88.128.12
  7    21 ms    20 ms    28 ms  host-61-14-48-1.eu.bt.net [61.14.48.1]
  8    32 ms    21 ms    20 ms  61.14.51.8
  9    21 ms    25 ms    26 ms  195.206.70.203
 10    20 ms    23 ms    22 ms  is.ixp.joburg [196.60.8.126]
 11    28 ms    34 ms    37 ms  168.209.1.192
 12    31 ms    31 ms    26 ms  168.209.88.214
 13    35 ms    26 ms    26 ms  196.34.90.124
 14    24 ms    28 ms    62 ms  196.34.90.125
 15    26 ms    23 ms    28 ms  core.xe-0-0-1-gp-sm-het-dce-2.za.africainx.net [
41.84.12.95]
 16    25 ms    23 ms    23 ms  41-66-132-246-f6.hetzner-jhb-ip4-gw.africainx.ne
t [41.66.132.246]
 17    23 ms    23 ms    33 ms  core-access-switch1.jnb1.host-h.net [197.189.193
.1]
 18    30 ms    23 ms    28 ms  row-access-switch1-row17-18.jnb1.host-h.net [197
.189.193.46]
 19    24 ms    23 ms    23 ms  129.232.229.238

Trace complete.

Why are you routing via UK

d7e7r7 · Apr 18, 2017

Dizzle said:
Why are you routing via UK

Dunno, it was done from work pc...

Anthro · Apr 18, 2017

Cybersmart via WiSP

C:\Users\>ping 129.232.229.238

Pinging 129.232.229.238 with 32 bytes of data:
Reply from 129.232.229.238: bytes=32 time=27ms TTL=56
Reply from 129.232.229.238: bytes=32 time=23ms TTL=56
Reply from 129.232.229.238: bytes=32 time=23ms TTL=56
Reply from 129.232.229.238: bytes=32 time=29ms TTL=56

Ping statistics for 129.232.229.238:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 29ms, Average = 25ms

C:\Users\>tracert -d 129.232.229.238

Tracing route to 129.232.229.238 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.100.1
2 <1 ms 7 ms 1 ms 10.0.0.1
3 1 ms 1 ms <1 ms 192.168.9.9
4 5 ms 3 ms 1 ms 196.22.240.185
5 22 ms 22 ms 27 ms 196.41.97.17
6 26 ms 23 ms 25 ms 196.60.9.24
7 28 ms 32 ms 25 ms 197.189.193.1
8 27 ms 26 ms 24 ms 197.189.193.46
9 26 ms 26 ms 23 ms 129.232.229.238

Trace complete.

Sinbad · Apr 18, 2017

D:\Users\micro>tracert 129.232.229.238

Tracing route to 129.232.229.238 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router [192.168.1.1]
2 <1 ms <1 ms <1 ms 196-212-61-1.dynamic.ftth.broadband.is [196.212.61.1]
3 1 ms 1 ms <1 ms cdsl2-rba-vl151.ip.isnet.net [196.38.73.10]
4 <1 ms <1 ms <1 ms 196.38.73.157
5 3 ms 2 ms 3 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 1 ms 1 ms 1 ms 196.26.0.69
7 1 ms 1 ms 1 ms mi-za-rba-epe1-te2-2-304.ip.isnet.net [168.209.86.250]
8 1 ms 1 ms 1 ms 196.34.90.124
9 1 ms <1 ms <1 ms 196.34.90.125
10 1 ms 1 ms 1 ms core.xe-0-0-1-gp-sm-het-dce-2.za.africainx.net [41.84.12.95]
11 1 ms 1 ms 1 ms 41-66-132-246-f6.hetzner-jhb-ip4-gw.africainx.net [41.66.132.246]
12 2 ms 2 ms 6 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
13 3 ms 4 ms 8 ms row-access-switch1-row17-18.jnb1.host-h.net [197.189.193.46]
14 1 ms 1 ms 1 ms 129.232.229.238

PBCool · Apr 24, 2017

Pinging 129.232.229.238 with 32 bytes of data:
Reply from 129.232.229.238: bytes=32 time=2ms TTL=58
Reply from 129.232.229.238: bytes=32 time=2ms TTL=58
Reply from 129.232.229.238: bytes=32 time=2ms TTL=58
Reply from 129.232.229.238: bytes=32 time=2ms TTL=58

1 <1 ms <1 ms <1 ms 192.168.0.254
2 <1 ms <1 ms <1 ms 154.0.2.73
3 1 ms <1 ms <1 ms 154.0.2.237
4 2 ms 2 ms 2 ms hetzner-1.jinx.net.za [196.223.14.98]
5 6 ms 7 ms 8 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
6 8 ms 4 ms 4 ms row-access-switch1-row17-18.jnb1.host-h.net [197.189.193.46]
7 2 ms 2 ms 2 ms 129.232.229.238

Sinbad · Apr 24, 2017

Sinbad said:
D:\Users\micro>tracert 129.232.229.238

Tracing route to 129.232.229.238 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms router [192.168.1.1]
2 <1 ms <1 ms <1 ms 196-212-61-1.dynamic.ftth.broadband.is [196.212.61.1]
3 1 ms 1 ms <1 ms cdsl2-rba-vl151.ip.isnet.net [196.38.73.10]
4 <1 ms <1 ms <1 ms 196.38.73.157
5 3 ms 2 ms 3 ms core2b-pkl-te0-0-0-0.ip.isnet.net [196.26.0.63]
6 1 ms 1 ms 1 ms 196.26.0.69
7 1 ms 1 ms 1 ms mi-za-rba-epe1-te2-2-304.ip.isnet.net [168.209.86.250]
8 1 ms 1 ms 1 ms 196.34.90.124
9 1 ms <1 ms <1 ms 196.34.90.125
10 1 ms 1 ms 1 ms core.xe-0-0-1-gp-sm-het-dce-2.za.africainx.net [41.84.12.95]
11 1 ms 1 ms 1 ms 41-66-132-246-f6.hetzner-jhb-ip4-gw.africainx.net [41.66.132.246]
12 2 ms 2 ms 6 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
13 3 ms 4 ms 8 ms row-access-switch1-row17-18.jnb1.host-h.net [197.189.193.46]
14 1 ms 1 ms 1 ms 129.232.229.238

PBCool said:
1 <1 ms <1 ms <1 ms 192.168.0.254
2 <1 ms <1 ms <1 ms 154.0.2.73
3 1 ms <1 ms <1 ms 154.0.2.237
4 2 ms 2 ms 2 ms hetzner-1.jinx.net.za [196.223.14.98]
5 6 ms 7 ms 8 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
6 8 ms 4 ms 4 ms row-access-switch1-row17-18.jnb1.host-h.net [197.189.193.46]
7 2 ms 2 ms 2 ms 129.232.229.238

When your ping is lower than an ISP's

Geoff.D · Apr 24, 2017

PBCool said:
Pinging 129.232.229.238 with 32 bytes of data:
Reply from 129.232.229.238: bytes=32 time=2ms TTL=58
Reply from 129.232.229.238: bytes=32 time=2ms TTL=58
Reply from 129.232.229.238: bytes=32 time=2ms TTL=58
Reply from 129.232.229.238: bytes=32 time=2ms TTL=58

1 <1 ms <1 ms <1 ms 192.168.0.254
2 <1 ms <1 ms <1 ms 154.0.2.73
3 1 ms <1 ms <1 ms 154.0.2.237
4 2 ms 2 ms 2 ms hetzner-1.jinx.net.za [196.223.14.98]
5 6 ms 7 ms 8 ms core-access-switch1.jnb1.host-h.net [197.189.193.1]
6 8 ms 4 ms 4 ms row-access-switch1-row17-18.jnb1.host-h.net [197.189.193.46]
7 2 ms 2 ms 2 ms 129.232.229.238

Inside job!

Not fair!

Here are my results

Code:

Pinging 129.232.229.238 with 32 bytes of data:
Reply from 129.232.229.238: bytes=32 time=31ms TTL=54
Reply from 129.232.229.238: bytes=32 time=30ms TTL=54
Reply from 129.232.229.238: bytes=32 time=31ms TTL=54
Reply from 129.232.229.238: bytes=32 time=30ms TTL=54

Ping statistics for 129.232.229.238:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 30ms, Maximum = 31ms, Average = 30ms

>tracert 129.232.229.238

Tracing route to 129.232.229.238 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.1.254
  2     *        *        *     Request timed out.
  3     *       27 ms    27 ms  105.224.0.49
  4    29 ms    27 ms    28 ms  105.224.0.162
  5    27 ms    26 ms    29 ms  105.224.0.13
  6    27 ms    27 ms    26 ms  105.187.249.2
  7    29 ms    28 ms    30 ms  196-60-9-24.ixp.joburg [196.60.9.24]
  8    33 ms    34 ms    29 ms  core-access-switch1.jnb1.host-h.net [197.189.193.1]
  9    30 ms    30 ms    31 ms  row-access-switch1-row17-18.jnb1.host-h.net [197.189.193.46]
 10    29 ms    29 ms    30 ms  129.232.229.238

Trace complete.

CooperX · Sep 13, 2017

Sinbad said:
When your ping is lower than an ISP's

you must live pretty close to the Area that Hetzner runs the servers

Join the MyBroadband community

Get started

Ping or Trace Route This IP address

fluffykittenlover

Banned

Rickster

EVGA Fanatic

Johnatan56

Honorary Master

Rickster

EVGA Fanatic

d7e7r7

Executive Member

Dizzle

Active Member

d7e7r7

Executive Member

Anthro

Expert Member

Sinbad

Honorary Master

PBCool

Cool Ideas Rep

Sinbad

Honorary Master

Geoff.D

Honorary Master

CooperX

Banned