Ziron incident
[voice] Possible issues with customer-originating traffic transiting LINX
Resolved after 2 hours 11 minutes, on February 16, 2018.
One of our network infrastructure suppliers has identified an MPLS congestion issue in Telehouse North that was increasing latency on our primary connection to LINX. This was resolved at approximately 12:00, and round trip times are now within normal expectations.
Update timeline
- investigating Feb 16, 2018, 11:38 AM UTC
We are investigating call quality quality issues which appear to be only affecting customers who are reaching our London network via the London Internet Exchange (LINX). More details to follow.
- identified Feb 16, 2018, 11:55 AM UTC
We are looking further into what appears to be some asymmetrical routing with some peers across LINX. At this time we do not believe this is having a major impact on call quality, but may introduce an extra 15-20ms of latency.
- monitoring Feb 16, 2018, 12:15 PM UTC
One of our network infrastructure suppliers has identified an MPLS congestion issue in Telehouse North that was increasing latency on our primary connection to LINX. This was resolved at approximately 12:00, and round trip times are now within normal expectations.
- resolved Feb 16, 2018, 01:49 PM UTC
This incident has been resolved.
Your product runs on more than Ziron
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services