Forum Discussion

weefuzzy's avatar
weefuzzy
Settling in
3 days ago
Solved

Timeouts with some websites

Since last night, I can't connect to 34sp.com (my web hosting provider) or any of my web sites on VM, unless I'm on a VPN, with any device I try. If I'm on a VPN, everything is absolutely fine. Otherwise, it says 'connecting to (blah)' and then times out. traceroutes to 34sp.com on the hub (Hub3) just black-hole. I don't have child locks, virus protection or any of that enabled. 

34sp isn't geo-blocked in any way: they're just a UK hosting provider. They don't seem to be blacklisted on any virus/malware lists that I can see. 

 

 

I've talked both to the chatbot and to an actual human in support, who was trying their best but unfortunately none the wiser. I've rebooted everything, done a factory reset on the hub, and tried using alternative DNS on my device. 

So, I'm pretty sure it's a VM problem and that it's not a configuration issue at my end. I did think it might have been some mysterious block imposed just on me, because it happened in the midst of me doing some upgrades on my sites and there was a lot of refreshing going on. However, when I just signed up here, using an email address for one of those sites didn't work, so maybe VM as a whole is having issues connecting to 34sp servers? 

Any pointers on how to diagnose this – or even fix it – much appreciated. 

 

 

timeouts
websites
  • legacy1's avatar
    legacy1
    3 days ago

    Its also possible VM is not to blame and that 34sp.com is blocking you by your IP.

    so try hub in modem mode

    or maybe 34sp.com has your IP listed as being malicious 

    GreyNoise IP Check

6 Replies

  • weefuzzy's avatar
    weefuzzy
    Settling in
    2 days ago

    Thanks again everyone. Turned out it was my IP being blocked, because I'd got a password wrong too many times <blush> 

  • weefuzzy's avatar
    weefuzzy
    Settling in
    2 days ago

    Thanks for the great suggestions everyone. In fact it looks like my traceroute is failing after it leaves VM, so quite possibly 34sp are just blocking my IP – I'll write and ask them! Happily, my IP isn't on GreyNoise...

    Using interface: en0
traceroute to 34sp.com (80.82.125.33), 64 hops max, 40 byte packets
 1  192.168.0.1 (192.168.0.1) 48 bytes to 192.168.0.14  12.549 ms  5.765 ms  5.536 ms
 2  10.53.39.53 (10.53.39.53) 36 bytes to 192.168.0.14  19.846 ms  23.281 ms  14.098 ms
 3  80.255.198.166 (80.255.198.166) 36 bytes to 192.168.0.14  15.655 ms  15.377 ms  15.286 ms
 4  * * *
 5  * * *
 6  80.255.204.77 (80.255.204.77) 36 bytes to 192.168.0.14  26.044 ms  22.604 ms  19.673 ms
 7  linx.r4.man1.34sp.com (195.66.244.35) 48 bytes to 192.168.0.14  60.199 ms  20.085 ms  24.917 ms
 8  * * *
 9  * * *
10  * * *

     

    • Steven_L's avatar
      Steven_L
      Icon for Forum Team rankForum Team
      8 hours ago

      Hello weefuzzy,

      Welcome to the Community, and thanks for taking the time to post here on the forums. I’m sorry to hear of the issues that you’re experiencing with your connection.

      Have you been able to get your issues resolved since you last posted?

      Kind Regards,

      Steven_L

  • legacy1's avatar
    legacy1
    Alessandro Volta
    3 days ago

    Its also possible VM is not to blame and that 34sp.com is blocking you by your IP.

    so try hub in modem mode

    or maybe 34sp.com has your IP listed as being malicious 

    GreyNoise IP Check

  • Roger_Gooner's avatar
    Roger_Gooner
    Alessandro Volta
    3 days ago

    This is my trace route.

    C:\>tracert 34sp.com

Tracing route to 34sp.com [80.82.125.33]
over a maximum of 30 hops:

  1     3 ms    <1 ms    10 ms  192.168.0.1
  2     *        *        *     Request timed out.
  3     9 ms     7 ms    10 ms  80.255.195.134
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7    16 ms    14 ms    14 ms  80.255.204.77
  8    16 ms    15 ms    13 ms  linx.r4.man1.34sp.com [195.66.244.35]
  9   280 ms    15 ms    16 ms  80.82.125.33

Trace complete.

C:\>

    It shows my path to 34SP works whilst yours doesn't, so this is a VM routing/peering issue affecting only certain regions and no amount of rebooting will help.

    So, say this to VM: “I’m experiencing a regional routing fault. I cannot reach 34SP’s network (AS51059) from my Virgin Media connection. Another VM user's traceroute shows a black hole inside VM’s network before the LINX handoff, so I'm suffering from  a broken route inside VM’s core or at a VM–LINX peer. The site works instantly through a VPN, which proves the issue is with VM’s routing path, not my equipment. Please escalate this to the Network Team for a routing/peering investigation.”

  • Client62's avatar
    Client62
    Alessandro Volta
    3 days ago

    Localised VM network routing issues are not unknown. 
    A trace route that breaks can be the giveaway.

    Using our VM Connection ( from Colchester ) we can access https://www.34sp.com/