Thanks All, I would normally have provided more data but have been nowhere near a computer this evening and unable to check anything further. Just wanted to see if it was a wider problem that others were seeing and was going to look into tomorrow.
The BBC NOC told me these IPs were local so I think you are probably onto something with anycast issues. Paul Bone Chief Technical Officer Bridge Fibre Sent from my iPhone > On 14 Nov 2018, at 22:18, Brandon Butterworth <[email protected]> wrote: > >> On Wed Nov 14, 2018 at 09:26:15PM +0000, Chris Malton wrote: >> traceroute to bbc.co.uk (2a04:4e42:600::81), 30 hops max, 80 byte packets > > inet6num: 2a04:4e40::/29 > netname: US-FASTLY-20130718 > > So cdn, it's down to fastly/HE so neither directly under > our (BBC) control > >> 19 2a04:4e42:600::81 (2a04:4e42:600::81) 326.976 ms 326.960 ms 326.940 ms > > That's a long way away, looks like it's not a HE routing issue as that > realy is in brisbane. The question is why for UK requests > Fastly are handing out an AU node, maybe it is supposed to be anycast > and something happened to our local nodes. > > There's actually 4 returned IPs only the 3rd is close so chances > are 75% of users are getting AU > > bbc.co.uk has AAAA address 2a04:4e42:600::81 > bbc.co.uk has AAAA address 2a04:4e42::81 > bbc.co.uk has AAAA address 2a04:4e42:200::81 > bbc.co.uk has AAAA address 2a04:4e42:400::81 > > Looks like it's time to ask fastly unless the DNS is intended > to resolve locality (also outsourced, was easier when it was all > BBC stuff that might break) > >> Is that any help to you? > > Yes, any data is better than no data, thanks > > brandon >
