cancel
Showing results for 
Search instead for 
Did you mean: 
Ant3000
Contributor
503 Views
Message 211 of 295

Re: Cannot access BBC or Facebook

Looking at the bigger picture why would BT care if, lets say 10%, of it's customers can only access certain parts of the internet some of the time?

 

The bigger issue is that 10% of BT's customer can't access the websites of some of the webs biggest players (amazon, tesco, ebay etc) which is then effecting their profits.

 

---Mr J Smith was a stauch shopper of Tesco until his ISP couldn't serve the website and so he has now defected to Asda---

 

BT is potentailly losing customers for these big retaillers, amd I'm not so sure that they are going to take the news well!!

 

 

0 Ratings
Ant3000
Contributor
488 Views
Message 212 of 295

Re: Cannot access BBC or Facebook

16:24 / 217.43.181.32 / all DNS's

 

BBC, Tesco, amazon, ebay - no worky!

0 Ratings
Ant3000
Contributor
454 Views
Message 213 of 295

Re: Cannot access BBC or Facebook

17:43 still not working!
0 Ratings
alnitak
Newbie
415 Views
Message 214 of 295

Re: Cannot access BBC or Facebook

I have this problem right now, and have been suffering it intermittently for weeks.

 

I'm *not* using BT's DNS servers, nor a BT supplied router.  I'm running a local fully recursive DNS server with DNSSEC validation.  I can assure you folkds this is *not* a problem with BT's DNS per-se, but it does appear to be a problem with the BT-hosted Akamai servers in the 213.120.157 network.

 

My current WAN IP is 86.133.223.246.   Here's a traceroute to the address I'm currently getting for newsimg.bbc.co.uk:

 

% traceroute 213.120.157.67

traceroute to 213.120.157.67 (213.120.157.67), 64 hops max, 52 byte packets

 1  10.1.2.1 (10.1.2.1)  0.806 ms  0.493 ms  0.457 ms

 2  217.41.191.186 (217.41.191.186)  39.222 ms  49.076 ms  73.454 ms

 3  * * *

 4  * * *

[ad naseum]

 

Here's a traceroute to the very same IP from my Amazon EC2 instance in the US East Cost:

$ traceroute 213.120.157.67

traceroute to 213.120.157.67 (213.120.157.67), 30 hops max, 60 byte packets

 1  100.124.189.129 (100.124.189.129)  0.893 ms  1.179 ms  1.435 ms

 2  100.76.169.13 (100.76.169.13)  0.629 ms 100.76.169.15 (100.76.169.15)  0.713 ms 100.76.169.12 (100.76.169.12)  0.672 ms

 3  100.76.169.32 (100.76.169.32)  0.650 ms 100.76.169.46 (100.76.169.46)  0.634 ms 100.76.169.27 (100.76.169.27)  0.604 ms

 4  ip-10-128-158-6.ec2.internal (10.128.158.6)  0.716 ms ip-10-128-122-7.ec2.internal (10.128.122.7)  0.693 ms ip-10-128-142-4.ec2.internal (10.128.142.4)  0.665 ms

 5  ip-10-128-109-54.ec2.internal (10.128.109.54)  1.275 ms ip-10-128-133-254.ec2.internal (10.128.133.254)  1.415 ms ip-10-128-184-118.ec2.internal (10.128.184.118)  1.237 ms

 6  100.64.130.7 (100.64.130.7)  1.431 ms 100.64.132.139 (100.64.132.139)  1.504 ms 100.64.135.119 (100.64.135.119)  0.876 ms

 7  100.64.128.230 (100.64.128.230)  1.048 ms 100.64.129.218 (100.64.129.218)  1.342 ms 100.64.128.168 (100.64.128.168)  0.879 ms

 8  ip-10-1-3-2.ec2.internal (10.1.3.2)  0.622 ms ip-10-1-3-100.ec2.internal (10.1.3.100)  0.589 ms ip-10-1-173-84.ec2.internal (10.1.173.84)  0.586 ms

 9  100.64.36.17 (100.64.36.17)  8.155 ms 100.64.36.15 (100.64.36.15)  1.695 ms 100.64.38.141 (100.64.38.141)  9.037 ms

10  216.182.224.208 (216.182.224.208)  2.431 ms 216.182.224.78 (216.182.224.78)  1.692 ms 216.182.224.94 (216.182.224.94)  1.733 ms

11  100.64.14.175 (100.64.14.175)  1.641 ms 100.64.14.95 (100.64.14.95)  14.387 ms 100.64.2.199 (100.64.2.199)  16.819 ms

12  100.64.0.112 (100.64.0.112)  1.669 ms 100.64.0.246 (100.64.0.246)  1.618 ms 100.64.0.100 (100.64.0.100)  1.638 ms

13  100.64.16.229 (100.64.16.229)  22.144 ms 100.64.16.141 (100.64.16.141)  2.303 ms 100.64.16.5 (100.64.16.5)  0.805 ms

14  72.21.222.137 (72.21.222.137)  0.696 ms 205.251.245.67 (205.251.245.67)  0.846 ms 72.21.222.34 (72.21.222.34)  0.904 ms

15  72.21.220.52 (72.21.220.52)  1.451 ms 72.21.220.36 (72.21.220.36)  1.284 ms 72.21.220.52 (72.21.220.52)  1.356 ms

16  ixp1-ae0-0.us-ash.eu.bt.net (166.49.169.17)  1.053 ms 72.21.220.52 (72.21.220.52)  2.565 ms 72.21.220.36 (72.21.220.36)  1.331 ms

17  ixp1-ae0-0.us-ash.eu.bt.net (166.49.169.17)  0.912 ms t2c3-xe-0-0-3-0.uk-lof.eu.bt.net (166.49.208.76)  80.399 ms ixp1-xe-1-3-0-0.us-ash.eu.bt.net (166.49.169.13)  0.957 ms

18  t2c3-xe-0-1-0-0.uk-lof.eu.bt.net (166.49.208.58)  80.759 ms t2c3-xe-11-0-0-0.uk-lof.eu.bt.net (166.49.208.52)  98.564 ms  98.528 ms

19  core1-te0-10-0-2.faraday.ukcore.bt.net (213.121.193.188)  81.447 ms 213.137.183.5 (213.137.183.5)  80.807 ms core2-te0-10-0-0.faraday.ukcore.bt.net (213.121.193.216)  86.330 ms

20  core1-Te0-0-0-13.ealing.ukcore.bt.net (213.121.193.32)  82.134 ms host213-121-193-8.ukcore.bt.net (213.121.193.8)  84.815 ms core1-te0-11-0-5.ealing.ukcore.bt.net (213.121.193.38)  86.683 ms

21  host213-121-193-52.ukcore.bt.net (213.121.193.52)  84.147 ms host213-121-193-64.ukcore.bt.net (213.121.193.64)  80.388 ms core2-Te0-3-0-7.ealing.ukcore.bt.net (213.121.193.66)  84.293 ms

22  109.159.248.120 (109.159.248.120)  90.159 ms acc1-10GigE-0-0-0-6.bm.21cn-ipp.bt.net (109.159.248.82)  81.759 ms 109.159.248.76 (109.159.248.76)  85.695 ms

23  109.159.248.92 (109.159.248.92)  81.096 ms 217.41.222.186 (217.41.222.186)  82.334 ms  82.137 ms

24  31.55.166.69 (31.55.166.69)  90.800 ms  86.005 ms  90.430 ms

25  213.120.157.67 (213.120.157.67)  88.210 ms * 31.55.166.69 (31.55.166.69)  86.042 ms

 

So, I can reach this BT-hosted Akamai box perfectly well from outside BT's network but bizarrely can't access it from the inside.

 

I used to run ISP networks for a living - it would seem odd if this were the 512k problem since what I'm seeing here is an internal routing problem, not one relating to the "global routing table" size issue that triggered the TCAM problems this week.

0 Ratings
Brandscill
Aspiring Expert
410 Views
Message 215 of 295

Re: Cannot access BBC or Facebook

What I don't understand is if it is the 512K limit Ant (and I'm not flat out disagreeing with you) is why doesn't it affect all ISP's assuming it's on the sites end or all customers of an ISP assuming it's an ISP end?

Why would some of BT's customers get served up the correct route and others not?

On a side note, where are you based? Wonder if there is a location correlation between us all!
0 Ratings
Highlighted
alnitak
Newbie
398 Views
Message 216 of 295

Re: Cannot access BBC or Facebook

I'm pretty sure it's not the 512k limit.  This appears to be a problem for BT Broadband customers accessing a group of BT-hosted Akamai CDN nodes that won't be getting used by other ISPs.

 

For the BT tech that asked for pcaps - I just tried making a connection to newsimg.bbc.co.uk:80 (resolved to

213.120.157.34) and the pcaps showed nothing.  Specifically the nothing they showed was any response from the Akamai server!  My half of the TCP connection showed up perfectly well, but there was zero response from 213.120.157.34

 

This might suggest that the problem is in the routing from the Akamai nodes back to the broadband users rather than the other way around.

 

0 Ratings
alnitak
Newbie
384 Views
Message 217 of 295

Re: Cannot access BBC or Facebook

and now I've just reconnected my DSL line with a new WAN IP of 86.154.155.23, and everything is working.  Note that I'm now using servers in the 213.120.161/24 block instead of 213.120.157/24:

 

% traceroute newsimg.bbc.co.uk

traceroute: Warning: newsimg.bbc.co.uk has multiple addresses; using 213.120.161.144

traceroute to a1733.g.akamai.net (213.120.161.144), 64 hops max, 52 byte packets

 1  10.1.2.1 (10.1.2.1)  2.352 ms  2.182 ms  2.134 ms

 2  217.41.191.186 (217.41.191.186)  34.028 ms  34.578 ms  35.188 ms

 3  217.47.41.193 (217.47.41.193)  34.286 ms  39.225 ms  35.009 ms

 4  213.1.69.110 (213.1.69.110)  38.450 ms  38.301 ms  49.600 ms

 5  31.55.164.103 (31.55.164.103)  38.923 ms  39.408 ms  39.420 ms

 6  31.55.164.191 (31.55.164.191)  39.360 ms  39.519 ms  38.601 ms

 7  31.55.164.109 (31.55.164.109)  39.198 ms  38.021 ms  38.471 ms

 8  31.55.166.77 (31.55.166.77)  45.379 ms  37.672 ms  37.007 ms

 9  213.120.161.144 (213.120.161.144)  47.684 ms  89.841 ms  54.979 ms

 

0 Ratings
nkjG4NvlQ3LI
Contributor
377 Views
Message 218 of 295

Re: Cannot access BBC or Facebook

I've just come across this thread from a post on a mailing list. I've not noticed any problems, though I don't use BT DNS and I have censorship set to off. 

 

I run a mix of Linux and BSDs on all of my devices currently with MTU of 1492. Location is Newcastle on Tyne region, on FTTC. I do get regular congestion symptoms at peak times but haven't noticed any complete fails.

 

 A quick skim over the posts so far smells like  a CDN problem to me.

 

If I get hit by it I'll grab some pcaps and post them in here.

 

 

 

edited: I can't spell, as usual

0 Ratings
Ant3000
Contributor
376 Views
Message 219 of 295

Re: Cannot access BBC or Facebook

From a laymans perspective everything seemed to stack up for the 512k thing but maybe I was just clutching at straws in the hope we'd stumbled upon the answer between us however with alnitak bringing his knowledge and a fresh perspective I'm hopeful that we may be onto something more concrete as like brandschill mentions "why does it only effect certain BT customers"?

Let's hope that alnitak can spare some time to keep on the case for the benefit of us all
0 Ratings
nkjG4NvlQ3LI
Contributor
368 Views
Message 220 of 295

Re: Cannot access BBC or Facebook

my WAN IP = 86.132.215.48, DNS is 8.8.8.8 for this test.  FTTC, Newcastle on Tyne region

 

note the 33% loss on the lastline

 

$ mtr --tcp 80 -w -r -b -c 3  newsimg.bbc.co.uk
Start: Sat Aug 16 23:06:05 2014
HOST: HP-xw8600-M17M                                                    Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- ???                                                                                                       100.0     3    0.0   0.0   0.0   0.0   0.0
  2.|-- 217.32.144.70                                                                                       0.0%     3    4.5   4.7   4.5   4.9   0.0
  3.|-- 217.32.144.110                                                                                     0.0%     3    4.7   4.8   4.7   4.9   0.0
  4.|-- 212.140.235.194                                                                                   0.0%     3    8.6   8.6   8.6   8.7   0.0
  5.|-- 213.120.180.165                                                                                   0.0%     3    9.8   9.7   9.5   9.8   0.0
  6.|-- 217.41.169.107                                                                                    0 .0%     3    9.6   9.9   9.6  10.1   0.0
  7.|-- acc1-10GigE-9-3-0.sf.21cn-ipp.bt.net (109.159.251.95)                     0.0%     3    9.4   9.0   8.3   9.4   0.0
  8.|-- core2-te-0-4-0-17.ilford.ukcore.bt.net (109.159.251.49)                      0.0%     3   19.1  19.8  19.1  20.6   0.0
  9.|-- peer4-te0-2-1-0.telehouse.ukcore.bt.net (109.159.254.146)                0.0%     3   23.4  22.2  20.0  23.4   1.7
 10.|-- 195.99.126.195                                                                                      0.0%     3   17.4  17.2  16.8  17.4   0.0
 11.|-- a23-63-99-242.deploy.static.akamaitechnologies.com (23.63.99.242) 33.3%     3   91.0 145.7  91.0 200.5  77.5

 

0 Ratings