Marbled Fennec Networks

Project members and guest should take a moment to review our Network Management Policy as some of the details within have changed. The changes should not directly affect any connected endpoints but it is better that ya’ll stay informed.

Bigger Changes:
* FurrIX will no longer provide temporary services to public end users; only our members and guest.
* FurrIX will no longer offer peering and cross project routing with other projects. This lessens our workload and lowers the traffic crossing our network.
* MFN has lowered the monthly data bucket to 600GB per month after reviewing the past three months of traffic patterns.

As for our website changes, we have update our about, FAQ and team pages to reflect the current state of our operations. Give those pages a quick read through when you have a moment.

So, it seems at some point in the last few months, our status bot got wrecked. Quad9 stopped answering DNS request from our network and the bot silently failed and didn’t make any alerts to us about it.

So there was half assed and just broken uptime tracking until I noticed it the other night when checking over our website.

This issue has been resolved. Steps taking were first updating the SSL cert cause it expired during this time; updating the name server settings to use CF’s public DNS; and restarting the bot. Everything appears to be working correctly now.

That little project did not go over well what so ever and a lot of things ended up broken to hell and back. Adrian is working on restoring the network back to stable images from a few nights ago and we will not be revisiting this idea again.