Is the Internet broke (in parts)?

I have a fancy new ADSL line running at a speedy 3Mbps. Its kinda OK but this afternoon many websites are unreachable. I can get here, but not ispreview.co.uk. I can get google.co.uk but not duckduckgo.com. ee.co.uk doesn't work, the BBC does. Best of all I can't reach zen.co.uk...

Tried the usual tricks, cleared caches, restarted, tried changing DNS. Maybe its something else?

Is DNS resolving the sites to an IP address and how far does a trace route go in terms of reaching the sites?

This after a minute or so for zen.co.uk. Yes, does find IP.

Traceroute has started�

traceroute: Warning: zen.co.uk has multiple addresses; using 34.248.255.53
traceroute to zen.co.uk (34.248.255.53), 64 hops max, 72 byte packets
1 fritz.box (192.168.1.1) 1.690 ms 0.825 ms 0.760 ms
2 vt1.cor2.lond1.ptn.zen.net.uk (51.148.72.22) 20.330 ms 20.518 ms 20.425 ms
3 ae-9.agg2.lond1.ptn.zen.net.uk (51.148.73.16) 26.580 ms 27.794 ms 38.843 ms
4 51-148-73-55.dsl.zen.co.uk (51.148.73.55) 19.966 ms 20.966 ms 23.181 ms
5 amazon-gw-a.lonap.net (5.57.80.8) 33.179 ms 20.599 ms 19.981 ms
6 54.239.101.110 (54.239.101.110) 35.226 ms 33.939 ms 62.165 ms
7 54.239.101.121 (54.239.101.121) 21.232 ms 20.580 ms 19.657 ms
8 * * *
9 54.239.44.41 (54.239.44.41) 33.544 ms 31.841 ms 30.862 ms
10 * * *
11 52.93.7.160 (52.93.7.160) 49.853 ms 36.897 ms 44.802 ms
12 52.93.101.65 (52.93.101.65) 30.185 ms 31.115 ms 31.114 ms
13 52.93.101.72 (52.93.101.72) 51.899 ms 54.013 ms 45.915 ms
14 52.93.36.83 (52.93.36.83) 31.015 ms 31.600 ms 31.766 ms
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *

MTU setting maybe?

An odd value can cause some sites to work fine but others not.

Matt

Not sure where my MTU setting is TBH. Mac or router? Either way I haven't touched it, honost!

In reply to a post by Woolwich:

Not sure where my MTU setting is TBH. Mac or router? Either way I haven't touched it, honost!

Ah, Mac.

Configure: automatically
MTU: Standard (1500)

AV software or parental controls gone mad?

Clock set to correct time?

Having same issues tonight on Pulse8. Ive rebooted router, changed DNS yet certain sites are slow to load, while others are normal speed. Speed tests, pings etc all fine.

Tracing route to gamerankings.com [64.30.228.167]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 28 ms 28 ms 28 ms host-92-23-0-1.as13285.net [blanked out]
3 30 ms 29 ms 29 ms host-78-151-229-205.as13285.net [78.151.229.205]
4 29 ms 30 ms 29 ms host-78-151-229-204.as13285.net [78.151.229.204]
5 35 ms 35 ms 35 ms host-78-144-9-35.as13285.net [78.144.9.35]
6 36 ms 36 ms 37 ms akamai.prolexic.com [195.66.224.31]
7 36 ms 36 ms 36 ms a72-52-60-200.deploy.static.akamaitechnologies.com [72.52.60.200]
8 38 ms 37 ms 37 ms ae121.access-a.sech-lon2.netarch.akamai.com [72.52.60.205]
9 * * * Request timed out.
10 171 ms * * a209-200-160-232.deploy.static.akamaitechnologies.com [209.200.160.232]
11 * * * Request timed out.
12 * 172 ms 171 ms irb-1214.spine4.phx2.cbsig.net [216.239.126.226]
13 172 ms * * gamerankings-www-vip1.phx2.cbsig.net [64.30.228.167]
14 173 ms * * gamerankings-www-vip1.phx2.cbsig.net [64.30.228.167]
15 * 173 ms * gamerankings-www-vip1.phx2.cbsig.net [64.30.228.167]
16 173 ms 172 ms 172 ms gamerankings-www-vip1.phx2.cbsig.net [64.30.228.167]

Thats one of sites im having issues with.

Edited by bobble_bob (Tue 01-May-18 19:25:50)

Do Zen use a Talk Talk line by any chance?

Post deleted by bobble_bob

In reply to a post by Woolwich:

Not sure where my MTU setting is TBH. Mac or router? Either way I haven't touched it, honost!

Router.

Try lowering to 1432 just to see if there is any behaviour change. You can revert if not.

Matt

Well I am with BT and I can access those sites fine, but I did some trace routes to them and have the following:

traceroute --icmp zen.co.uk
traceroute to zen.co.uk (34.248.255.53), 30 hops max, 60 byte packets
 1  192.168.2.253 (192.168.2.253)  0.271 ms  0.303 ms  0.263 ms
 2  * * *
 3  * * *
 4  31.55.186.188 (31.55.186.188)  3.965 ms  3.939 ms  4.341 ms
 5  core3-hu0-16-0-3.faraday.ukcore.bt.net (195.99.127.198)  4.121 ms  4.270 ms  4.255 ms
 6  peer2-et-2-3-0.redbus.ukcore.bt.net (62.172.103.37)  3.640 ms  3.583 ms  3.465 ms
 7  195.99.126.11 (195.99.126.11)  3.509 ms  3.562 ms  3.532 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

As you can see traceroute gives fails to get to the destination before the 30 hops.

traceroute --icmp duckduckgo.com
traceroute to duckduckgo.com (79.125.105.113), 30 hops max, 60 byte packets
 1  192.168.2.253 (192.168.2.253)  0.342 ms  0.288 ms  0.256 ms
 2  * * *
 3  31.55.186.177 (31.55.186.177)  3.031 ms  3.002 ms  2.974 ms
 4  31.55.186.176 (31.55.186.176)  4.027 ms  3.995 ms  3.970 ms
 5  195.99.127.110 (195.99.127.110)  3.964 ms  3.935 ms  4.419 ms
 6  peer2-et-9-1-0.redbus.ukcore.bt.net (62.172.103.43)  3.444 ms  3.266 ms  3.316 ms
 7  195.99.126.11 (195.99.126.11)  3.410 ms  3.375 ms  3.300 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Its the same with duckduckgo.com

traceroute --icmp ee.co.uk
traceroute to ee.co.uk (54.72.201.146), 30 hops max, 60 byte packets
 1  192.168.2.253 (192.168.2.253)  0.365 ms  0.307 ms  0.263 ms
 2  * * *
 3  * * *
 4  31.55.186.176 (31.55.186.176)  5.314 ms  5.509 ms  5.474 ms
 5  host213-121-192-52.ukcore.bt.net (213.121.192.52)  3.919 ms  3.892 ms  4.345 ms
 6  peer2-et-2-3-0.redbus.ukcore.bt.net (62.172.103.37)  4.510 ms  4.452 ms  4.394 ms
 7  195.99.126.11 (195.99.126.11)  4.427 ms  4.519 ms  4.519 ms
 8  * * *
 9  * * *
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

Same with ee.co.uk

traceroute --icmp www.ispreview.co.uk
traceroute to www.ispreview.co.uk (217.160.0.152), 30 hops max, 60 byte packets
 1  192.168.2.253 (192.168.2.253)  0.428 ms  0.365 ms  0.325 ms
 2  * * *
 3  * * *
 4  31.55.186.184 (31.55.186.184)  5.487 ms  5.609 ms  5.559 ms
 5  195.99.127.100 (195.99.127.100)  4.500 ms  4.628 ms  4.597 ms
 6  213.121.193.199 (213.121.193.199)  5.977 ms  5.898 ms  5.754 ms
 7  linx.bb-c.the.lon.gb.oneandone.net (195.66.224.98)  5.043 ms  5.092 ms  5.057 ms
 8  ae-6.bb-c.bap.rhr.de.oneandone.net (212.227.120.49)  18.633 ms  18.607 ms  18.571 ms
 9  217-160-0-152.elastic-ssl.ui-r.com (217.160.0.152)  18.528 ms  18.493 ms  18.209 ms

ISPReview seems ok for me.

traceroute --icmp bbc.co.uk
traceroute to bbc.co.uk (151.101.0.81), 30 hops max, 60 byte packets
 1  192.168.2.253 (192.168.2.253)  0.324 ms  0.278 ms  0.225 ms
 2  * * *
 3  * * *
 4  31.55.186.188 (31.55.186.188)  4.081 ms  4.051 ms  4.040 ms
 5  core4-hu0-17-0-9.faraday.ukcore.bt.net (213.121.192.64)  3.986 ms  3.955 ms  3.945 ms
 6  peer8-et-0-1-3.telehouse.ukcore.bt.net (109.159.252.98)  3.539 ms  3.720 ms  3.594 ms
 7  195.99.126.83 (195.99.126.83)  3.492 ms  3.398 ms  3.353 ms
 8  151.101.0.81 (151.101.0.81)  2.880 ms  2.939 ms  2.907 ms

BBC Site seems fine.

traceroute --icmp google.co.uk
traceroute to google.co.uk (216.58.208.163), 30 hops max, 60 byte packets
 1  192.168.2.253 (192.168.2.253)  0.328 ms  0.285 ms  0.249 ms
 2  * * *
 3  * * *
 4  31.55.186.180 (31.55.186.180)  4.378 ms  4.346 ms  4.315 ms
 5  195.99.127.54 (195.99.127.54)  3.280 ms  3.252 ms  3.287 ms
 6  peer8et-7-0-3.telehouse.ukcore.bt.net (62.172.103.174)  3.381 ms  3.486 ms  3.329 ms
 7  109.159.253.191 (109.159.253.191)  3.192 ms  3.144 ms  3.099 ms
 8  * * *
 9  216.239.56.192 (216.239.56.192)  3.139 ms  3.098 ms  3.150 ms
10  216.239.46.29 (216.239.46.29)  4.068 ms  4.019 ms  3.965 ms
11  lhr25s09-in-f3.1e100.net (216.58.208.163)  3.108 ms  3.075 ms  3.039 ms

As so is Google.

What I have noticed is that ZEN, EE and DuckDuckGO they all fail at the same point, maybe they are using the same hosting company and that hosting company is having issues.

The strange thing is I am having no issues viewing the sites.

Have you tried flushing your DND cache (assuming you are on a PC)

ipconfig /flushdns

Then re-open the browser and try again.

Paul

Edited by PaulKirby (Tue 01-May-18 21:05:37)

I tried changing DNS, still the same. Tried on my phone, still the same. Its not the same sites as the OP, i have different sites having issues

One is http://www.gamefaqs.com/

https://community.talktalk.co.uk/t5/Broadband/Terrib...

Someone over on the TT forums having similar issues

In reply to a post by MrSaffron:

AV software or parental controls gone mad?

Clock set to correct time?

Can�t see anything unusual on the router, different devices (Mac & iPad) having same trouble with certain sites.

In reply to a post by bobble_bob:

Do Zen use a Talk Talk line by any chance?

My POTS line is on a Zen account as is my ADSL.

Well I didn't say try a different DNS, I said flush it, it might of stored some old routing.

The site you refer to seems fine to me in the >> browser (screenshot) << and also the routing:

traceroute --icmp gamefaqs.gamespot.com
traceroute to gamefaqs.gamespot.com (64.30.228.84), 30 hops max, 60 byte packets
1 192.168.2.253 (192.168.2.253) 0.430 ms 0.357 ms 0.318 ms
2 * * *
3 * * *
4 31.55.186.184 (31.55.186.184) 5.453 ms 5.697 ms 6.987 ms
5 core3-hu0-8-0-5.faraday.ukcore.bt.net (195.99.127.40) 4.114 ms 4.171 ms 4.936 ms
6 peer1-et1-1-0.telehouse.ukcore.bt.net (213.121.193.161) 4.900 ms 4.244 ms 4.291 ms
7 akamai.prolexic.com (195.66.224.31) 6.621 ms 6.485 ms 6.522 ms
8 a72-52-60-192.deploy.static.akamaitechnologies.com (72.52.60.192) 5.189 ms 5.157 ms 5.245 ms
9 ae120.access-a.sech-lon2.netarch.akamai.com (72.52.60.197) 11.444 ms 11.922 ms 11.957 ms
10 * * *
11 a209-200-160-232.deploy.static.akamaitechnologies.com (209.200.160.232) 132.547 ms 131.873 ms 132.302 ms
12 reth0-1205.fw3.phx2.cbsig.net (216.239.126.221) 132.590 ms 133.162 ms 133.089 ms
13 irb-1214.spine3.phx2.cbsig.net (216.239.126.224) 134.494 ms 134.146 ms 134.133 ms
14 gamefaqs-www-vip1.phx2.cbsig.net (64.30.228.84) 132.733 ms 132.515 ms 132.983 ms

It is strange though that people on different ISP's are having issues.

Paul

No, not a PC but a Mac. But I see the same trouble when using my iPad.

I�ll investigate more if the issues persists overnight. Odd how you can see sites but your traceroutes look like mine.

Too late now and to make it worst, I can�t get to Netflix...

In reply to a post by bobble_bob:

https://community.talktalk.co.uk/t5/Broadband/Terrib...

Someone over on the TT forums having similar issues

Yeah, just checked my PS4 and XBOne and they all are fine.

Paul

Will trying flushing DNS, but would this effect other devices if it was a routing issue?

In reply to a post by bobble_bob:

Will trying flushing DNS, but would this effect other devices if it was a routing issue?

Not normally, unless those other devices also have the same old records cached.

But its worth a try anyhow, when ever sites become sluggish I clear my DNS Cache, some times it helps, but not all the time.

Paul

Tried it anyway but not helped

It is strange though that people on different ISP's are having issues.

Not only different ISPs but different websites aswell

More and more forums posts over on the TT forums, and downdetector TT page having people saying the same thing. Do Zen lines run off the TTB network?

Edited by bobble_bob (Tue 01-May-18 22:03:52)

Seems to be working now for me, certainly the sites that were down and PSN. Will see what its like in the morning

Still broken this morning. Restarted router, still the same. Can't access zen.co.uk, pings timeout. Then at 0900 it started working again, can access Zen and ISP Review etc. So it seems okay for the moment.

Who knows...

All mine came back last night and were working at 6am this morning. Im on a TTB connection though

In reply to a post by Woolwich:

Still broken this morning. Restarted router, still the same. Can't access zen.co.uk, pings timeout. Then at 0900 it started working again, can access Zen and ISP Review etc. So it seems okay for the moment.

Who knows...

The pings timing out doesn't mean a routing issue, it might be that host might be set not to respond to ICMP Pings.
Which was why my trace routes timed out and I was also able to view all the sites.

Paul