Need some ping results to an IP

Drukpa

Having some problems with my server, and can't figure out where the problem is. When I ping from my home connection, it results in a lot of packet loss, but when I ping from some VPS from UK, no packet loss results.

When I ping an IP in the same city (Dallas, Texas) as my server, no packet loss results, from both my home connection as well as the VPS. So, can't really blame my home ISP as well.

Would really appreciate if you guys (preferably from ASIA) could do a test on the IP (72.9.144.30) and paste the results.

Thanks.

MarcusLVPSHosting

Is this happening all the time or occasionally? Maybe a routing issue?

0xdragon

@MarcusLVPSHosting said:
Is this happening all the time or occasionally? Maybe a routing issue?

I sense an offer coming.

Drukpa

Been happening continuously since last week. I am trying to rule out my home ISP, since I do not want to unnecessarily bother my host unless its really their problem.

@MarcusLVPSHosting said:
Is this happening all the time or occasionally? Maybe a routing issue?

serverian

Use just-ping.com

suliuyi

C:\Users\Administrator>ping 72.9.144.30

正在 Ping 72.9.144.30 具有 32 字节的数据:
来自 72.9.144.30 的回复: 字节=32 时间=356ms TTL=49
来自 72.9.144.30 的回复: 字节=32 时间=418ms TTL=49
来自 72.9.144.30 的回复: 字节=32 时间=357ms TTL=49
来自 72.9.144.30 的回复: 字节=32 时间=419ms TTL=49

I am from Asia, so don't mind these Chinese characters

wych

What severian said.

Drukpa

Tried this site, once you test an IP, I think the result gets stored in cache. Not very accurate.

@serverian said:
Use just-ping.com

ryanswj

Pinging 72.9.144.30 with 32 bytes of data:
Reply from 72.9.144.30: bytes=32 time=228ms TTL=42
Reply from 72.9.144.30: bytes=32 time=218ms TTL=42
Reply from 72.9.144.30: bytes=32 time=218ms TTL=42
Reply from 72.9.144.30: bytes=32 time=214ms TTL=42

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

===============================

Tracing route to tailormadeservers.com [72.9.144.30]
over a maximum of 30 hops:

1 1 ms 1 ms <1 ms router.asus.com [10.20.16.1]
2 3 ms 3 ms 3 ms bb42-60-135-254.singnet.com.sg [42.60.135.254]
3 4 ms 5 ms 5 ms 202.166.123.170
4 3 ms 3 ms 3 ms 202.166.123.169
5 3 ms 3 ms 4 ms 202.166.121.182
6 3 ms 4 ms 4 ms ae6-0.singha.singnet.com.sg [202.166.120.186]
7 8 ms 19 ms 8 ms ae3-0.pepsi.singnet.com.sg [202.166.126.125]
8 4 ms 4 ms 3 ms 203.208.191.113
9 4 ms 4 ms 4 ms 203.208.149.126
10 171 ms 185 ms 171 ms 203.208.182.122
11 198 ms 182 ms 195 ms 203.208.172.242
12 178 ms 190 ms 175 ms ge-11-2-0.mpr2.pao1.us.above.net [64.125.12.205]
13 189 ms 172 ms 171 ms ae7.cr2.sjc2.us.above.net [64.125.25.137]
14 196 ms 191 ms 194 ms ae1.cr2.lax112.us.above.net [64.125.31.234]
15 232 ms 233 ms 235 ms ae3.cr2.iah1.us.above.net [64.125.21.85]
16 228 ms 268 ms 229 ms ae2.cr2.dfw2.us.above.net [64.125.21.61]
17 221 ms 241 ms 225 ms ae7.er2.dfw2.us.above.net [64.125.20.234]
18 232 ms 232 ms 236 ms 64.124.196.226.t00876-01.above.net [64.124.196.226]
19 221 ms 238 ms 238 ms 206.123.64.45
20 280 ms 230 ms 235 ms 72.249.128.110
21 244 ms 260 ms 234 ms tailormadeservers.com [72.9.144.30]

Trace complete.

(woah! many many hops)

Drukpa

Not a network guru, but I have a feeling there's issues with above.net's routes.

From the traceroute screenshot can someone please help me know where the most likely problem is at?

autoclick

From Jakarta-Indonesia :

Pinging 72.9.144.30 with 32 bytes of data:
Reply from 72.9.144.30: bytes=32 time=229ms TTL=48
Reply from 72.9.144.30: bytes=32 time=229ms TTL=48
Reply from 72.9.144.30: bytes=32 time=230ms TTL=48
Reply from 72.9.144.30: bytes=32 time=229ms TTL=48

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

socials

Not from Asia, but..

$ ping 72.9.144.30 -c 30 | tail -n 3
--- 72.9.144.30 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29017ms
rtt min/avg/max/mdev = 177.136/321.412/754.601/125.186 ms

Everything seems fine from here (Sweden).

Never mind the min/max times, my AP is acting up. Can't be arsed to restart it again.

agoldenberg

PING 72.9.144.30 (72.9.144.30): 56 data bytes
64 bytes from 72.9.144.30: icmp_seq=0 ttl=50 time=57.924 ms
64 bytes from 72.9.144.30: icmp_seq=1 ttl=50 time=55.337 ms
64 bytes from 72.9.144.30: icmp_seq=2 ttl=50 time=55.132 ms
64 bytes from 72.9.144.30: icmp_seq=3 ttl=50 time=57.095 ms
64 bytes from 72.9.144.30: icmp_seq=4 ttl=50 time=57.114 ms
64 bytes from 72.9.144.30: icmp_seq=5 ttl=50 time=56.796 ms
64 bytes from 72.9.144.30: icmp_seq=6 ttl=50 time=56.922 ms
64 bytes from 72.9.144.30: icmp_seq=7 ttl=50 time=60.859 ms
64 bytes from 72.9.144.30: icmp_seq=8 ttl=50 time=66.420 ms
64 bytes from 72.9.144.30: icmp_seq=9 ttl=50 time=56.924 ms
64 bytes from 72.9.144.30: icmp_seq=10 ttl=50 time=57.688 ms
64 bytes from 72.9.144.30: icmp_seq=11 ttl=50 time=56.525 ms
64 bytes from 72.9.144.30: icmp_seq=12 ttl=50 time=58.969 ms
64 bytes from 72.9.144.30: icmp_seq=13 ttl=50 time=62.197 ms
64 bytes from 72.9.144.30: icmp_seq=14 ttl=50 time=59.099 ms
64 bytes from 72.9.144.30: icmp_seq=15 ttl=50 time=60.729 ms
64 bytes from 72.9.144.30: icmp_seq=16 ttl=50 time=61.492 ms
64 bytes from 72.9.144.30: icmp_seq=17 ttl=50 time=58.792 ms
64 bytes from 72.9.144.30: icmp_seq=18 ttl=50 time=64.332 ms
64 bytes from 72.9.144.30: icmp_seq=19 ttl=50 time=56.626 ms
64 bytes from 72.9.144.30: icmp_seq=20 ttl=50 time=58.163 ms
64 bytes from 72.9.144.30: icmp_seq=21 ttl=50 time=56.432 ms
64 bytes from 72.9.144.30: icmp_seq=22 ttl=50 time=54.590 ms
^C
--- 72.9.144.30 ping statistics ---
23 packets transmitted, 23 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 54.590/58.529/66.420/2.887 ms

Nothing Lost Here in Canada.

heihachi88

From Kazakhstan

definedcode

Fine from NL:

will@nl:~$ ping 72.9.144.30 -c 30 | tail -n 3
--- 72.9.144.30 ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29035ms
rtt min/avg/max/mdev = 127.518/128.415/132.190/1.499 ms

Starry

Ping statistics for 72.9.144.30:
Packets: Sent = 337, Received = 337, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 212ms, Maximum = 363ms, Average = 220ms

From Canton telecom