This is a strange one but I'll do my best to help. To be honest this is either a routing issue that we can flag up to Networks or it's something on your local network - pc security software for instance.
I have a couple of questions to ask:
Are you having this problem on one or more devices?
Is the site inaccessible over Wi-Fi or Ethernet, or both?
Please perform a traceroute, via a wired connection, to the National Lottery website, and post the output on here. That should provide us with a good idea of what's happening.
I'm getting the problem just through the cable modem here on Virgin. It's multiple devices, phone via WiFi, Laptop via WiFi, desktop via Cat5e cable, Web browser on wired Apple TV... all don't return any pages from the national-lottery site.
If I VPN into my work's network in London, I get through just fine on the phone and desktop which have the VPN connection.
I can sometimes see images from the National Lottery website if I search via Google, sometimes they will load (I think they might be cached actually in my browser) and sometimes not. The routing to the national lottery load balancer looks OK, but I can't get any further than that. The DNS is returning the same IP address for the load balancer both through virginmedia and through my VPN.
My son who is also in Watford, in another part of the town about 2 miles away, can access the national lottery site fine.
I have my modem set to pass-through or modem mode only as I have more advanced networking gear than the Superhub hanging off it.
I can only think that it's something the Lottery people have done to block some IP addresses somehow. Or it's a blocked route in Virgin somewhere. I'm getting the trace route now.
Traceroute has started…
traceroute to www.lb.national-lottery.co.uk (126.96.36.199), 64 hops max, 72 byte packets 1 INTERNAL NETWORK ADDRESS (INTERNAL NETWORK ADDRESS OF GATEWAY) 3.950 ms 4.504 ms 1.446 ms 2 * * * 3 watf-core-2b-xe-032-0.network.virginmedia.net (188.8.131.52) 98.667 ms 28.399 ms 3076.649 ms 4 popl-bb-1c-ae1-0.network.virginmedia.net (184.108.40.206) 39.516 ms 21.825 ms 49.270 ms 5 * * * 6 nrth-ic-1-ae1-0.network.virginmedia.net (220.127.116.11) 686.222 ms 28.745 ms 33.983 ms 7 m674-mp2.cvx1-b.lis.dial.ntli.net (18.104.22.168) 39.345 ms 19.478 ms 15.075 ms 8 * * * 9 22.214.171.124 (126.96.36.199) 150.907 ms 151.798 ms 312.646 ms 10 188.8.131.52 (184.108.40.206) 1017.660 ms 177.331 ms 34.502 ms 11 * * 220.127.116.11 (18.104.22.168) 1528.585 ms 12 22.214.171.124 (126.96.36.199) 15.369 ms 21.639 ms 27.528 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * *
and then it goes on and on but my trace route has no timeout like the web browser does.
The results are, pretty much, what I get when run a traceroute to the same destination IP (188.8.131.52) via command prompt and then from the CMTS using your default gateway address.
There is a small variation with the latter - the IP on hop 14, 184.108.40.206, where the last octet changes to 110.
If you don't mind I'd like you to repeat the traceroute, but this time remove your own router please and disable modem mode on the Hub.
This will provide a new WAN IP and I'm interested to see the results of that.
Yes, I had considered the implications of posting an IP address, but I couldn't see any realistic way to give you the important information whilst redacting any of it! And whilst it shouts out my broad location, I use a net-moniker anyway, and the information can't actually be used for that much mischief that isn't already possible to do another way.
Knowing that you appear to have taken ownership of the issue means that I can PM you more information later on when I get change to gather it. Thank you!