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
