Half of the internet just disappeared, Plusnet or wider issue?

[#1]

Was just playing WoW and got disconnected, after that I couldn't access any Blizzard sites or even Google or Reddit. Still can't access many sites. ANy idea what's going on?

[#2]

You are not alone. But seems to have recovered now. BBC was iffy; Guardian was not found; Amazon was not found; Football365 was not found on my windows box but it seemed as if I could get them on my iPhone. PlusNet DNS issue?

[#3]

Yep same here just drops off, looks like a blip, thought it may have been plusnet changing gateway.

[#4]

It's not just you as Now TV froze here (which it has never done before) and various web sites timed out.

I'm using Google DNS fwiw.

[#5]

You are not alone.

Cannot resolved many websites e.g. I can access http://www.bbc.co.uk/ but cannot get to http://www.independent.co.uk/ 

More worryingly I cannot VPN into work!! 

[#6]

This suggests it was quite a widespread issue, not specific to us: http://downdetector.co.uk/

[#7]

seems to be ok now...

[#8]

Gah! I couldn't even get here to find out what was happening. Just wasted time rebooting etc.

[#9]

Thanks Chris. If you find out what was the cause, please let us know.

[#10]

It's doesn't seem related to us so it's unlikely we'll be able to find the cause from here.

[#11]

http://downdetector.co.uk/problems/bt-british-telecom/news/83248-problems-at-bt

[#12]

Not sure why you're specifically linking to BT there, looking at http://downdetector.co.uk/ shows this impacted a huge range of sites and services.

[#13]

Seems to be back to normal at the moment. That Downdetector link shows massive outages. I wonder what happened?

[#14]

---

@Chris wrote:

Not sure why you're specifically linking to BT there, looking at http://downdetector.co.uk/ shows this impacted a huge range of sites and services.

---

Plusnet uses a lot of BT for routing purposes e.g.

traceroute to guardian.co.uk (104.156.81.233), 30 hops max, 60 byte packets
 1  router (192.168.1.1)  0.387 ms  0.434 ms  0.727 ms
 2  * * *
 3  * * *
 4  be3-3100.pcn-ir01.plus.net (195.166.143.128)  25.217 ms  25.213 ms  25.279 ms
 5  core1-BE1.colindale.ukcore.bt.net (195.99.125.132)  25.341 ms  25.404 ms  25.459 ms
 6  195.99.127.83 (195.99.127.83)  35.073 ms 195.99.127.36 (195.99.127.36)  34.894 ms core3-hu0-14-0-7.faraday.ukcore.bt.net (195.99.127.64)  34.953 ms
 7  213.137.183.34 (213.137.183.34)  34.826 ms 213.137.183.38 (213.137.183.38)  23.749 ms  23.852 ms
 8  ldn-b3-link.telia.net (213.248.67.97)  16.715 ms  16.694 ms  16.617 ms
 9  ldn-bb3-link.telia.net (62.115.117.10)  16.827 ms * ldn-bb3-link.telia.net (62.115.117.4)  13.681 ms
10  * ldn-b3-link.telia.net (80.91.247.86)  15.609 ms ldn-b3-link.telia.net (80.91.245.27)  12.261 ms
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
...

[#15]

Indeed we do, however as I've said this appears unrelated. If you look at the overall downdetector link, this affected a huge range of services and people that are completely unrelated to BT in any way.