Agreed from my monitoring. Sorry for top post.
Regards, Chris On 23 November 2018 15:47:38 GMT, Paul Bone <[email protected]> wrote: >Hi Chris, > >BBC NOC have just confirmed this is fixed and I now see 2msec to >bbc.co.uk from Cambridge again. > >Best Regards >Paul > >Paul Bone >Chief Technical Officer >email: [email protected] >office/service desk: +44 (0)1223 755055 >mobile: +44 (0)7713 393621 | direct: >www.bridgefibre.co.uk > >BT are ceasing new ISDN services by 2020 and then ISDN entirely by >2025... >Is your phone system future proof? Talk to our experts today. > > >-----Original Message----- >From: uknof <[email protected]> On Behalf Of Chris >Malton >Sent: 23 November 2018 10:30 >To: Martin Barry <[email protected]> >Cc: [email protected] >Subject: Re: [uknof] Fastly routes broken via HE? > >On 23/11/2018 10:22, Martin Barry wrote: >> On 2018-11-21 08:10, Chris Malton wrote: >>> I believe its 2a04:4e42:200::81, 2a04:4e42:600::81 that are >affected. >> >> We (Fastly) are investigating. >> >Hi Martin, > >Many thanks for investigating. > >The duplicates and loss resolved themselves on, I think, Wednesday >night (I have been tied up in a lot of client work since then). > >We're now just seeing ~80ms latency from my monitoring sites which >seems to be caused by it taking a trip over the pond to NYC and then on >to Bell Canada. > >I think this is the same issue Paul at BridgeFibre was also seeing as >of yesterday afternoon. > >If you need any more info, please do shout. > >Regards, > >Chris -- Sent from my Android phone with K-9 Mail. Please excuse my brevity.
