For the next thirty minutes, our project will have limited general use bandwidth. Our backups have been in a failed state for three weeks and I just got them back functional and am running a backup task on the whole project right now.
Category: Operations
Information about changes or proposals that affect the way our project operates.
This project isn’t dead just yet, I just have had way too much going on in my life to stay on top of things. Over the next few days I should have some down time and will be slowly updating routers, VMs and so on to keep us operational. You’ll notice that things like the network graphs are working once again.
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.