Category: Issues

So, when we connect project members to our networks, we enroll the interface on our side into our NMS for accounting. Every project member or end user can make use of up to 600GB of transit each month before being placed into a lower QoS bucket. Or so that it how things are supposed to work.

Our NMS applied its updates on its own daily not needing any real oversight from our team until about four days ago. An update failed to apply correctly which resulted in a complete failure of accounting and a mix up of interface names not matching with their respective subnets. So, in a nutshell, there was zero traffic accounting for about four days because none of the data that was accounted was correct.

This has been sorted out as of this morning and everyone’s monthly usage was reset.

We added stats to our website for the two name servers. You can now view incoming request, RTT and VM stats for the last 48 hours.

Also, While we have started dropping request for a handful of ‘.pirate’ and ‘.libre’ domains, as well as dropping request for ‘isc.org’, the request flood is still ongoing but has backed off to about half of the volume it was earlier this week. Two of the volunteers on our team are keeping an eye on things.

I just fixed these guys…why must y’all make a mess of the sandbox?

For the time being, we are not answering queries to isc.org cause someone is trying to use us as part of an attack.