Tickets - can't ping the ipv4 address of vnhan01.sixxs.net :: SixXS

Ticket ID: SIXXS #7629558
Ticket Status: Resolved

PoP: vnhan01 - NetNam Corporation (Hanoi)

can't ping the ipv4 address of vnhan01.sixxs.net

Shadow Hawkins on Thursday, 16 August 2012 10:01:07

Hello, I can't ping the ipv4 address of vnhan01.sixxs.net, it should be 119.17.194.232, my ip address is 221.2.228.180, below is the tracert result from my ip to 119.17.194.232, could you kindly please help to check it? thank you. 1 1 ms 1 ms 1 ms 221.2.228.190 2 1 ms 1 ms 1 ms 221.2.251.109 3 2 ms 1 ms 1 ms 60.214.255.226 4 5 ms 5 ms 4 ms 221.2.255.217 5 22 ms 21 ms 20 ms 219.158.99.165 6 21 ms 21 ms 21 ms 219.158.4.214 7 24 ms 25 ms 25 ms 219.158.97.74 8 195 ms 173 ms 160 ms 203.208.147.105 9 143 ms * 134 ms 203.208.173.173 10 310 ms 172 ms 175 ms 203.208.174.210 11 115 ms 116 ms 123 ms static.vdc.vn [222.255.165.21] 12 114 ms 120 ms 149 ms 203.162.231.9 13 114 ms 132 ms * static.vdc.vn [123.30.63.94] 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out.

can't ping the ipv4 address of vnhan01.sixxs.net

Shadow Hawkins on Tuesday, 08 October 2013 11:30:13

i can ping the ipv4 address of vnhan01.sixxs.net, but the response time is not stable, it changing from about 200ms to max 39364 ms. As a result, i can't ping the peer ipv6 address of my tunnel(T106978, 2401:e800:100:39::1). Could you kindly please help to check it? Thank you very much. the following are the ping results. sunxi@sunxi-ThinkPad-Edge-E530c:~$ ping 119.17.194.232 PING 119.17.194.232 (119.17.194.232) 56(84) bytes of data. 64 bytes from 119.17.194.232: icmp_req=1 ttl=47 time=39364 ms 64 bytes from 119.17.194.232: icmp_req=2 ttl=47 time=38365 ms 64 bytes from 119.17.194.232: icmp_req=3 ttl=47 time=37366 ms 64 bytes from 119.17.194.232: icmp_req=4 ttl=47 time=36366 ms 64 bytes from 119.17.194.232: icmp_req=5 ttl=47 time=35366 ms 64 bytes from 119.17.194.232: icmp_req=6 ttl=47 time=34367 ms 64 bytes from 119.17.194.232: icmp_req=7 ttl=47 time=33367 ms 64 bytes from 119.17.194.232: icmp_req=8 ttl=47 time=32367 ms 64 bytes from 119.17.194.232: icmp_req=9 ttl=47 time=31368 ms 64 bytes from 119.17.194.232: icmp_req=10 ttl=47 time=30368 ms 64 bytes from 119.17.194.232: icmp_req=11 ttl=47 time=29369 ms 64 bytes from 119.17.194.232: icmp_req=12 ttl=47 time=28369 ms 64 bytes from 119.17.194.232: icmp_req=28 ttl=47 time=12372 ms 64 bytes from 119.17.194.232: icmp_req=29 ttl=47 time=11372 ms 64 bytes from 119.17.194.232: icmp_req=30 ttl=47 time=10373 ms 64 bytes from 119.17.194.232: icmp_req=41 ttl=47 time=13741 ms 64 bytes from 119.17.194.232: icmp_req=42 ttl=47 time=12742 ms 64 bytes from 119.17.194.232: icmp_req=43 ttl=47 time=11743 ms 64 bytes from 119.17.194.232: icmp_req=44 ttl=47 time=10743 ms 64 bytes from 119.17.194.232: icmp_req=45 ttl=47 time=9744 ms 64 bytes from 119.17.194.232: icmp_req=46 ttl=47 time=8744 ms 64 bytes from 119.17.194.232: icmp_req=47 ttl=47 time=7744 ms 64 bytes from 119.17.194.232: icmp_req=48 ttl=47 time=6745 ms 64 bytes from 119.17.194.232: icmp_req=49 ttl=47 time=5745 ms 64 bytes from 119.17.194.232: icmp_req=50 ttl=47 time=4746 ms 64 bytes from 119.17.194.232: icmp_req=51 ttl=47 time=3746 ms 64 bytes from 119.17.194.232: icmp_req=52 ttl=47 time=2746 ms 64 bytes from 119.17.194.232: icmp_req=53 ttl=47 time=1747 ms 64 bytes from 119.17.194.232: icmp_req=54 ttl=47 time=747 ms 64 bytes from 119.17.194.232: icmp_req=55 ttl=47 time=278 ms 64 bytes from 119.17.194.232: icmp_req=56 ttl=47 time=279 ms 64 bytes from 119.17.194.232: icmp_req=57 ttl=47 time=4443 ms 64 bytes from 119.17.194.232: icmp_req=58 ttl=47 time=3436 ms 64 bytes from 119.17.194.232: icmp_req=59 ttl=47 time=2429 ms 64 bytes from 119.17.194.232: icmp_req=60 ttl=47 time=1421 ms 64 bytes from 119.17.194.232: icmp_req=61 ttl=47 time=414 ms 64 bytes from 119.17.194.232: icmp_req=62 ttl=47 time=25008 ms 64 bytes from 119.17.194.232: icmp_req=63 ttl=47 time=24001 ms 64 bytes from 119.17.194.232: icmp_req=64 ttl=47 time=22993 ms 64 bytes from 119.17.194.232: icmp_req=65 ttl=47 time=21985 ms 64 bytes from 119.17.194.232: icmp_req=66 ttl=47 time=20977 ms 64 bytes from 119.17.194.232: icmp_req=67 ttl=47 time=19970 ms 64 bytes from 119.17.194.232: icmp_req=68 ttl=47 time=18962 ms 64 bytes from 119.17.194.232: icmp_req=69 ttl=47 time=17955 ms 64 bytes from 119.17.194.232: icmp_req=70 ttl=47 time=16947 ms 64 bytes from 119.17.194.232: icmp_req=71 ttl=47 time=15939 ms 64 bytes from 119.17.194.232: icmp_req=72 ttl=47 time=14931 ms 64 bytes from 119.17.194.232: icmp_req=73 ttl=47 time=13923 ms 64 bytes from 119.17.194.232: icmp_req=74 ttl=47 time=12915 ms 64 bytes from 119.17.194.232: icmp_req=75 ttl=47 time=11908 ms 64 bytes from 119.17.194.232: icmp_req=76 ttl=47 time=10900 ms 64 bytes from 119.17.194.232: icmp_req=77 ttl=47 time=9892 ms 64 bytes from 119.17.194.232: icmp_req=78 ttl=47 time=8884 ms 64 bytes from 119.17.194.232: icmp_req=79 ttl=47 time=7876 ms 64 bytes from 119.17.194.232: icmp_req=80 ttl=47 time=6868 ms ^C --- 119.17.194.232 ping statistics --- 90 packets transmitted, 55 received, 38% packet loss, time 89249ms rtt min/avg/max/mdev = 278.091/15590.944/39364.161/11548.647 ms, pipe 40 sunxi@sunxi-ThinkPad-Edge-E530c:~$ ping6 2401:e800:100:39::1 PING 2401:e800:100:39::1(2401:e800:100:39::1) 56 data bytes ^C --- 2401:e800:100:39::1 ping statistics --- 66 packets transmitted, 0 received, 100% packet loss, time 65518ms

can't ping the ipv4 address of vnhan01.sixxs.net

Jeroen Massar SixXS Staff

on Tuesday, 08 October 2013 17:00:02

A ping does not show where the latency is happening; a traceroute would. But please understand that we likely can do nothing about any latency involved on the intermediary hops.

can't ping the ipv4 address of vnhan01.sixxs.net

Jeroen Massar SixXS Staff

on Thursday, 16 August 2012 10:19:54

There are some IPv4 routing areas in that region. IPv6 is still working which is why the PoP is marked as online. The problem is being looked into.

can't ping the ipv4 address of vnhan01.sixxs.net

Shadow Hawkins on Friday, 23 November 2012 14:59:39

Hello, I also can't ping the ipv4 pop of vnhan01.sixxs.net which should be 119.17.194.232, and my ip address is 180.172.176.80. Could you kindly please help to check it?Thank you. Here is the tracert informations from my computer to the ipv4 pop: D:\Documents and Settings\Administrator>tracert 119.17.194.232 Tracing route to vnhan01.sixxs.net [119.17.194.232] over a maximum of 30 hops: 1 2 ms 1 ms 1 ms 192.168.1.1 2 1 ms 1 ms 2 ms 192.168.1.1 3 11 ms 3 ms 3 ms 124.74.56.15 4 4 ms 3 ms 3 ms 124.74.57.153 5 3 ms 3 ms 3 ms 124.74.209.9 6 22 ms 16 ms 17 ms 61.152.86.194 7 27 ms 27 ms 30 ms 202.97.33.18 8 3 ms 3 ms 4 ms 202.97.33.126 9 4 ms 3 ms 9 ms 202.97.35.238 10 * 170 ms 169 ms p16-7-3-2.r23.tokyjp01.jp.bb.gin.ntt.net [61.120 .146.141] 11 * 223 ms 255 ms p64-6-2-0.r21.newthk02.hk.bb.gin.ntt.net [129.25 0.2.121] 12 234 ms * 233 ms ae-2.r02.chwahk02.hk.bb.gin.ntt.net [129.250.3.1 53] 13 277 ms 268 ms 269 ms 203.131.243.74 14 190 ms 189 ms 188 ms ci228-12.netnam.vn [210.86.228.12] 15 * * * Request timed out. 16 * * * Request timed out. ...(omitted, all "Request timed out.") 29 * * * Request timed out. 30 * * * Request timed out.

can't ping the ipv4 address of vnhan01.sixxs.net

Shadow Hawkins on Tuesday, 01 December 2015 00:21:38

XiSun wrote: I can't ping the ipv4 pop of vnhan01.sixxs.net. Here is the tracert informations from my computer. 1 18 ms <1 ms <1 ms 192.168.25.148 2 <1 ms <1 ms <1 ms 192.168.100.2 3 <1 ms <1 ms <1 ms 10.0.0.101 4 1 ms <1 ms 1 ms 175.25.dsnet [203.110.175.25] 5 1 ms 1 ms 1 ms 208.145.dsnet [211.144.208.145] 6 2 ms 1 ms 1 ms 208.209.dsnet [211.144.208.209] 7 5 ms 3 ms 2 ms 222.73.128.145 8 3 ms 4 ms 3 ms 61.152.81.145 9 5 ms 3 ms 3 ms 101.95.120.78 10 * * * Request timeout. 11 * * * Request timeout. 12 91 ms 80 ms 80 ms 202.97.51.62 13 * * * Request timeout. 14 89 ms 89 ms 89 ms static.vdc.vn [123.30.120.65] 15 * * * Request timeout. 16 90 ms 90 ms 93 ms static.vdc.vn [123.30.63.94] 17 * * * Request timeout. 18 * * * Request timeout. Could you kindly please help to check it ? Thank you.

can't ping the ipv4 address of vnhan01.sixxs.net

Shadow Hawkins on Saturday, 24 November 2012 00:28:38

Now the problem is resolved, I can ping vnhan01.sixxs.net again.

State change: confirmed Locked

Jeroen Massar SixXS Staff

on Thursday, 16 August 2012 10:19:04

The state of this ticket has been changed to confirmed

State change: resolved Locked

Jeroen Massar SixXS Staff

on Wednesday, 22 August 2012 10:58:51

The state of this ticket has been changed to resolved

can't ping the ipv4 address of vnhan01.sixxs.net

Shadow Hawkins on Friday, 23 November 2012 15:39:48

The status is up, but i can't ping 119.17.194.232. It just turns to be timed out

can't ping the ipv4 address of vnhan01.sixxs.net

Shadow Hawkins on Friday, 23 November 2012 16:16:30

hello, here is my tracert result. Tracing route to vnhan01.sixxs.net [119.17.194.232] over a maximum of 30 hops: 1 1 ms <1 ms 1 ms 192.168.0.1 2 * * * Request timed out. 3 3 ms 2 ms 3 ms 119.145.246.9 4 6 ms 4 ms 5 ms 183.59.0.122 5 5 ms 4 ms 6 ms 183.59.0.250 6 5 ms 5 ms 4 ms 202.97.34.114 7 26 ms 20 ms 7 ms 202.97.60.197 8 6 ms 4 ms 6 ms 202.97.60.22 9 74 ms 73 ms 79 ms 202.97.4.122 10 127 ms 130 ms 125 ms p64-6-2-0.r21.newthk02.hk.bb.gin.ntt.net [129.250.2.121] 11 182 ms 173 ms * ae-2.r02.chwahk02.hk.bb.gin.ntt.net [129.250.3.153] 12 221 ms 212 ms 221 ms 203.131.243.74 13 135 ms 136 ms 137 ms ci228-12.netnam.vn [210.86.228.12] 14 * * * Request timed out. ... ... ... 30 * * * Request timed out.

Please note Posting is only allowed when you are logged in.