Parts of internet down?

[#1]

Quote from: Peterxrm

Its the same in Sunny Bognor Regis

Same in sunny Littlehampton.

[#2]

For me, changing to Google DNS fixed the DNS issues, but most websites still won't load with the error message changing from DNS lookup to connection timed out.
The ones that do load tend to be very slow, and very few actually load.
This is in Glasgow.

[#3]

Same here in Essex, tried ringing, the phones are down too.  

[#4]

Try openDNS
208.67.222.222
208.67.220.220
Works for me. DM

[#5]

Thanks Champnet!!! working now

[#6]

Yeah, the issue isn't DNS. there appears to be a routing SNAFU somewhere.
Traceroutes to 4.2.2.2 (root DNS server) stop at a BT router. I get similar results on various other sites.
Changing DNS will get you through to some places, but notothers.

[#7]

same for me in London N9, internet went down at midnight, rebooted the modem/router connection came back up immediately, but could not connect to many web sites that earlier in the day had been fine, changed my DNS servers to use google's DNS servers and everything seems to be working OK this morning.

[#8]

traceroute to 4.2.2.2 (4.2.2.2), 30 hops max, 38 byte packets
 1  lo0.10.central10.ptw-bng01.plus.net (195.166.128.170)  6.941 ms  6.784 ms  6.789 ms
 2  irb.10.PTW-CR01.plus.net (84.93.249.1)  7.326 ms  irb.10.PTW-CR02.plus.net (84.93.249.2)  7.414 ms  irb.10.PTW-CR01.plus.net (84.93.249.1)  46.321 ms
 3  195.99.126.182 (195.99.126.182)  8.456 ms  8.504 ms  195.99.126.138 (195.99.126.138)  7.313 ms
 4  core1-te0-3-0-12.ealing.ukcore.bt.net (109.159.254.101)  12.046 ms  109.159.254.176 (109.159.254.176)  11.367 ms  core1-te0-15-0-10.ealing.ukcore.bt.net (109.159.254.206)  10.024 ms
 5  62.172.103.139 (62.172.103.139)  7.880 ms  transit2-xe-11-1-0.ilford.ukcore.bt.net (194.72.20.154)  8.519 ms  8.549 ms
 6  t2c4-xe-9-3-0-0.uk-eal.eu.bt.net (166.49.168.61)  8.291 ms  18.141 ms  t2c4-xe-10-1-0-0.uk-eal.eu.bt.net (166.49.168.37)  8.500 ms
 7  xe-8-3-3.edge3.London1.Level3.net (195.50.124.73)  33.061 ms  5-1-2.ear2.London2.Level3.net (212.187.201.153)  512.891 ms  759.330 ms
 8  ae-123-3509.edge5.London1.Level3.net (4.69.166.33)  8.257 ms  ae-236-3612.edge5.London1.Level3.net (4.69.166.61)  8.859 ms  ae-234-3610.edge5.london1.Level3.net (4.69.166.53)  8.584 ms
 9  ae-234-3610.edge5.london1.Level3.net (4.69.166.53)  8.506 ms  ae-236-3612.edge5.London1.Level3.net (4.69.166.61)  8.619 ms  ae-234-3610.edge5.london1.Level3.net (4.69.166.53)  8.880 ms
10  b.resolvers.Level3.net (4.2.2.2)  8.649 ms  8.564 ms  8.577 ms

[#9]

Quote from: jaark

Yeah, the issue isn't DNS. there appears to be a routing SNAFU somewhere. Traceroutes to 4.2.2.2 (root DNS server) stop at a BT router. I get similar results on various other sites. Changing DNS will get you through to some places, but notothers.

This ^.
Seems to be a mismatch of where packets should go for certain routes.
Tracert from my PN line which completes at work fine, but down some odd route in PN's network:

Tracing route to edge-star-shv-01-iad3.facebook.com [31.13.69.197]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  RT-AC56U-9348 [192.168.0.1]
  2    17 ms    16 ms    16 ms  lo0.12.central12.pcl-bng01.plus.net [195.166.130
.140]
  3    16 ms    16 ms    16 ms  irb.12.pcl-cr02.plus.net [84.93.249.114]
  4    17 ms    17 ms    17 ms  195.99.126.98
  5    17 ms    17 ms    17 ms  core3-te0-19-0-20.faraday.ukcore.bt.net [109.159
.249.157]
  6    17 ms    17 ms    17 ms  peer2-et-3-3-0.faraday.ukcore.bt.net [62.6.201.1
65]
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13  ^C

[#10]

Moderators Note.
locked in favour of https://community.plus.net/forum/index.php/topic,143619.0/topicseen.html