We are setting this as resolved as the symptoms have been clear for some time.
Feb 5, 11:17 GMT
A fix has been implemented and we are monitoring the results.
Feb 1, 11:48 GMT
We have chased Amazon further today for a response. We are also investigating a workaround involving forcing the affected traffic via an alternative route.
Jan 31, 14:47 GMT
We are continuing to chase 3rd-party networks for resolution to this issue. Symptoms appear to appear daily at 16:00 approximately, and continue for around one hour.
Jan 31, 10:57 GMT
We are continuing to investigate this issue.
Jan 30, 18:44 GMT
We are aware that the issue recurred around 1600 GMT. We are engaging conversations between our tier-1 peer and Amazon to ensure this is resolved ASAP.
Jan 30, 16:42 GMT
Our investigations are continuing, however the symptoms have now subsided. We will provide a further update today.
Jan 30, 09:56 GMT
Under our request, the peers are discussing the issue. We are expecting an update within 24 hours.
Jan 29, 16:55 GMT
We are investigating some packet loss in the connection between one of our tier-1 peers and the Amazon region in Seattle. The case has been reported to both Amazon and the peer, and investigations are ongoing.
Jan 29, 16:44 GMT