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.
Category: Network
Post dealing with changes to how we route packets and configure our network.
If you are trying to use our services from the Toronto region, we are aware of connectivity issue leading to dropped packets and latency. Taking a look at the path, it looks like twelve99 is having issues in Chicago. There is nothing that we can do on our to fix this and are stuck waiting it out.
Hopefully this will clear up shortly and things will go back to normal.
There may be some connectivity hiccups throughout the evening as we are working on moving some interfaces around and restructuring parts of the network based off of lessons learned and changes that should have been implemented a year or two ago.
We are doing our best to minimize down time, but some routers will have to be rebooted as we go along.
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.