Kansas City (qmci2) - Service Degredation

Issue Start: 4:48 UTC, December 10th
Issue Stop: 21:30 UTC, December 10th

Quad9 has implemented compensating controls as of 21:30 UTC, that should result in no service degradation as of the posting of this message.

If service degradation persists post 21:30 UTC, please report this to support@quad9.net.

We are continuing to monitor.

We are currently experiencing service degradation in our Kansas City (qmci2) location.

* Due to Zayo (AS6461) recently exiting all internet exchanges in the US, Quad9 has been forced to pull all North America Zayo traffic into this location as a stopgap until a longer-term solution can be identified to spread the traffic among more Quad9 PoPs in North America. This stopgap solution prevents many ISPs in North America from routing to London as the "best" Quad9 path.
* Starting today, a large ISP in the Midwest started sending us a high volume of, legitimate-but-overwhelming traffic without warning or notice.
* These two items combined are resulting in a massive increase in compute and resources.

Quad9 is working on a short-term solution to restore service quality as soon as possible.

Please note that you can identify the Quad9 PoP to which you route by running a traceroute or performing the following DNS query in CLI:
nslookup -q=cname id.server.on.quad9.net. 9.9.9.9

If the result contains "qmci2", the this is relevant to you.

Issue Start: 4:48 UTC, December 10th