Forum Discussion

sneakers's avatar
sneakers
Joining in
2 months ago

Troubleshoot Blocked Website

Hi there.
Im a user of a piece of software for tracking sneaker sales, and generating invoices etc. 

Its hosted on the domain restock.gg. 

Since roughly the 13th of Feb, im unable to update the software. It reaches out to websocket.restock.gg and resolves to IP 193.142.146.219, but i can't seem to route to the address. 

Using a VPN, or a mobile connection the IP and domain is accessible and the software works as expected. 

I've contacted VM support, who say neither the domain nor the IP is on their block lists. 
Can any VM customers in here attempt to traceroute or ping the IP address, from your connection to help us troubleshoot the issue ?

Looking to see if this is not routeable for multiple customers on VM, or just me. 

Thanks, 

 

  • Client62's avatar
    Client62
    Alessandro Volta

    There have been a few gripes in recent days about routing not working for some IPs.
    The last failed trace route looked like it might be for a customer in the Manchester area.

    From Colchester, Essex using VM internet we can ping and trace route to websocket.restock.gg at 193.142.146.219, see below :

    >ping websocket.restock.gg

    Pinging websocket.restock.gg [193.142.146.219] with 32 bytes of data:
    Reply from 193.142.146.219: bytes=32 time=32ms TTL=118
    Reply from 193.142.146.219: bytes=32 time=32ms TTL=118
    Reply from 193.142.146.219: bytes=32 time=29ms TTL=118
    Reply from 193.142.146.219: bytes=32 time=27ms TTL=118

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

    >tracert websocket.restock.gg

    Tracing route to websocket.restock.gg [193.142.146.219]
    over a maximum of 30 hops:

      1     2 ms     1 ms     2 ms  192.168.0.1
      2     *        *        *     Request timed out.
      3    15 ms    16 ms    12 ms  80.255.193.200
      4     *        *        *     Request timed out.
      5     *        *        *     Request timed out.
      6    20 ms    20 ms    19 ms  aor.uk-lon03a-ri1.network.virginmedia.net [62.254.42.174]
      7     *        *        *     Request timed out.
      8     *        *        *     Request timed out.
      9    28 ms    27 ms    28 ms  cz-prg02a-ra2-ae-99-45.aorta.net [84.116.136.149]
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12     *        *        *     Request timed out.
     13    30 ms    29 ms    27 ms  193.142.146.219

    Trace complete.

  • From Peterborough, Cambridgeshire I can ping and tracert to websocket.restock.gg on 193.142.146.219 as below.

    ping websocket.restock.gg

    Pinging websocket.restock.gg [193.142.146.219] with 32 bytes of data:
    Reply from 193.142.146.219: bytes=32 time=22ms TTL=118
    Reply from 193.142.146.219: bytes=32 time=20ms TTL=118
    Reply from 193.142.146.219: bytes=32 time=21ms TTL=118
    Reply from 193.142.146.219: bytes=32 time=21ms TTL=118

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

    tracert websocket.restock.gg

    Tracing route to websocket.restock.gg [193.142.146.219]
    over a maximum of 30 hops:

      1    <1 ms    <1 ms    <1 ms  skinner.xfiles.local [192.168.0.1]
      2     8 ms     7 ms     9 ms  10.53.38.157
      3     8 ms     7 ms     9 ms  80.255.197.214
      4     *        *        *     Request timed out.
      5     *        *        *     Request timed out.
      6    12 ms    14 ms    21 ms  aor.uk-lon03a-ri1.network.virginmedia.net [62.254.42.174]
      7     *        *        *     Request timed out.
      8    22 ms    27 ms    22 ms  nl-ams17b-rc1-ae-14-0.aorta.net [84.116.137.21]
      9     *        *        *     Request timed out.
     10     *        *        *     Request timed out.
     11     *        *        *     Request timed out.
     12     *        *        *     Request timed out.
     13    23 ms    22 ms    23 ms  193.142.146.219

    Trace complete.

  • Hi sneakers 

    Welcome to our Community Forums and thanks for your post.

    We have some info here under 'What if a site is blocked when it shouldn't be?' that may help.