Resolved unable to reach x12.x10hosting.com

[zapxpayx]

There seems to be traffic blocked for certain network to this host. This was working earlier in the day and stopped working in night.

Initial I thought this is something to do with my broadband as this is working on my mobile phone.

Troubleshooting

Step:1 Traceroute from local machine - Failed

tracert x12.x10hosting.com

Tracing route to x12.x10hosting.com [198.91.81.12]
over a maximum of 30 hops:

  1    14 ms     2 ms     1 ms  homerouter.cpe [192.168.8.1]
  2     *        *        *     Request timed out.
  3    43 ms    79 ms    49 ms  **mod note - redacted, just to be safe**
  4    86 ms    39 ms    40 ms  172.24.226.218
  5    36 ms    39 ms    39 ms  ae1-1983.cr0-dub4.ip4.gtt.net [213.254.197.45]
  6   139 ms   127 ms   129 ms  ae37.cr1-chi1.ip4.gtt.net [89.149.185.98]
  7   128 ms   130 ms   128 ms  ip4.gtt.net [173.205.41.90]
  8  1116 ms   339 ms   201 ms  agg1.c13.r05.s101.chi03.singlehop.net [67.212.190.250]
  9   129 ms   129 ms   130 ms  aswg1.c09.r05.s101.chi03.singlehop.net [67.212.183.74]
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.

Trace complete.

It's getting blocked after aswg1.c09.r05.s101.chi03.singlehop.net [67.212.183.74]

Step 2: Traceroute using online traceroute tool. https://www.uptrends.nl/tools/traceroute - Working

1    3    67    25    **mod note - redacted, just to be safe**
2    36    50    2    dln-b1-link.telia.net    62.115.190.224 
3    -    -    -         
4    -    -    -         
5    100    97    122    chi-b21-link.telia.net    80.91.246.162 
6    100    169    181    serverhub-ic-324864-chi-b21.c.telia.net    62.115.154.247 
7    107    191    250    agg1.c13.r05.s101.chi03.singlehop.net    67.212.190.250 
8    101    187    231    aswg1.c09.r05.s101.chi03.singlehop.net    67.212.183.74 
9    102    168    109    x12.x10hosting.com    198.91.81.12

Step 3: After that, I tried with another online traceroute tool (https://ping.eu/traceroute/)and got blocked after aswg1.c09.r05.s101.chi03.singlehop.net 67.212.183.74 - Failed

1                   *    *    *

         
2    **mod note - redacted just to be safe**    de    0.447 ms       
core23.fsn1.hetzner.com    213.239.245.237    de    0.305 ms  
core24.fsn1.hetzner.com    213.239.245.241    de    0.447 ms

         
3    core1.fra.hetzner.com    213.239.203.153    de    5.969 ms       
core1.fra.hetzner.com    213.239.229.77    de    5.043 ms  
core1.fra.hetzner.com    213.239.203.153    de    5.969 ms

         
4    zayo.fra.ecix.net    62.69.146.139    de    7.459 ms    7.452 ms    7.445 ms

         
5    ae1.cs1.fra9.de.eth.zayo.com    64.125.29.64    us    97.520 ms    97.515 ms    97.506 ms

         
6    ae0.cs1.fra6.de.eth.zayo.com    64.125.29.54    us    97.481 ms    97.614 ms    97.597 ms

         
7    ae2.cs1.ams17.nl.eth.zayo.com    64.125.29.59    us    97.578 ms    97.598 ms    97.590 ms

         
8    ae0.cs1.ams10.nl.eth.zayo.com    64.125.29.80    us    97.562 ms    97.604 ms    97.589 ms

         
9    ae2.cs1.lhr15.uk.eth.zayo.com    64.125.29.17    us    97.563 ms    97.566 ms    97.551 ms

         
10    ae0.cs3.lhr11.uk.eth.zayo.com    64.125.29.118    us    98.738 ms    102.839 ms    *

         
11    ae5.cs3.lga5.us.eth.zayo.com    64.125.29.126    us    109.109 ms    109.100 ms    108.755 ms

         
12                   *    *    *

         
13    ae11.er2.ord7.us.zip.zayo.com    64.125.26.251    us    117.630 ms    117.622 ms    114.520 ms

         
14                   *    *    *

         
15    agg1.c13.r05.s101.chi03.singlehop.net    67.212.190.250    us    112.997 ms    133.351 ms    138.987 ms

         
16    aswg1.c09.r05.s101.chi03.singlehop.net    67.212.183.74    us    98.185 ms    *    *

         
17                   *    *    *

         
18                   *    *    *

         
19                   *    *    *

         
20                   *    *    *

         
21                   *    *    *

Can you please help here?

 

[zapxpayx]

Nevermind.. It started working again.. dunno how

 

[garrettroyce]

Sometimes tracert/tracerout acts funny. It's not blocked when it does the *'s; it means that that particular server doesn't feel like giving you any information. Usually, a ping test is the easiest way to see if your server is correct. If you see "pinging x12.x10hosting.com (198.91.81.12) with blah blah blah", it knows the server is at that address. Once it knows the address, it is safe to assume it knows how to get there. However, some servers do block the IMCP ECHO protocol in the name of "security", the same way some of them block traceroute from working properly (in the name of "security"). A server not replying to ping or traceroute ultimately doesn't mean it is online or offline; it just means it didn't reply.

TLDR; ping is better than traceroute. The server might just ignore both, though. Please post if you ever think there's a problem and someone will check for you.

Edit: I blocked out your IP. Doesn't actually do much, but there's no reason we need to see where you live.

 

[zapxpayx]

Sometimes tracert/tracerout acts funny. It's not blocked when it does the *'s; it means that that particular server doesn't feel like giving you any information. Usually, a ping test is the easiest way to see if your server is correct. If you see "pinging x12.x10hosting.com (198.91.81.12) with blah blah blah", it knows the server is at that address. Once it knows the address, it is safe to assume it knows how to get there. However, some servers do block the IMCP ECHO protocol in the name of "security", the same way some of them block traceroute from working properly (in the name of "security"). A server not replying to ping or traceroute ultimately doesn't mean it is online or offline; it just means it didn't reply.

TLDR; ping is better than traceroute. The server might just ignore both, though. Please post if you ever think there's a problem and someone will check for you.

Edit: I blocked out your IP. Doesn't actually do much, but there's no reason we need to see where you live.

Yes, I agree. This is funny. I am not a networking expert, so please pardon my ignorance. I've never seen such behavior where a host server chooses not to reply to request coming from certain network (unless there is firewall or iptable rules set).

Anyways, this is working flawlessly now. Thanks for your help.