Ziggo outage in Amsterdam, NL
We currently have multiple Ziggo circuits in Amsterdam showing major packet loss. They have been completely uncontactable by phone for the last 4 hours. Nothing obvious on their own twitter feeds, but others are reporting similar issues: https://twitter.com/ITTDesk/status/835541853072158720 Simon
Hi, (Following up on what I said to you on IRC) Ziggo (LGI) seems to have major issues in the Netherlands, not just circuits but also IP connectivity are affected. Many other networks (including the one I'm working for) report problems reaching Ziggo, many Ziggo customers complain on twitter about internet being down, see http://allestoringen.nl/storing/ziggo, that graph tells you enough even if you don't speak Dutch. Ziggo's outages page does not report any major issues, neither does their webcare's twitter account, it does mention last Friday's major outage thoug.. My Ziggo home network connection is affected as well, some parts of the internet are reachable, some aren't, which destinations are reachable seem to change over time. Luckily, my VPN endpoint is still reachable ;) regards, Teun
On 25 Feb 2017, at 22:59, Simon Lockhart via Outages <outages@outages.org> wrote:
We currently have multiple Ziggo circuits in Amsterdam showing major packet loss. They have been completely uncontactable by phone for the last 4 hours.
Nothing obvious on their own twitter feeds, but others are reporting similar issues:
On Sun Feb 26, 2017 at 12:58:59AM +0100, Teun Vink wrote:
Ziggo (LGI) seems to have major issues in the Netherlands, not just circuits but also IP connectivity are affected.
Indeed. We finally managed to get hold of Ziggo via an escalation contact which I was provided with off-list. Looks like they had (as you say) a major IP core issue. This also affected their voice platform, which they run as VOIP over their IP core, so we were unable to reach their NOC contacts by phone. They were abe to communicate with us by email, however. Issues started 2017-02-25 16:35 UTC. We saw a slight improvement in the packet-loss around 23:30, but service was not fully restored until 04:40. Pretty much 12 hours of outage. We've not had a RFO, but I'm sure it'll be forthcoming in the next few days. Simon
participants (2)
-
Simon Lockhart -
Teun Vink