Hello, freeBNC! Here’s a list of things that happened since last report: New Japanese server! New server in the Netherlands (previous one had stability issues) We have 8 ZNC nodes now! Things may be reworked soon, in the backend, to provide a better service. (Also, considering to run a paid service, without discontuining freeBNC; for “premium” stuff)
US2 is back
Hello. I’ve recently brought our US2 server back up. The problem was on Amazon’s AWS end. «Thank you for contacting AWS Support regarding your EC2 instance availability. We apologize that it is currently unreachable for you. I took a look at the instance in our system, and I can see that the underlying hardware for this
US2 node status
As most of you noticed lately on, the US2 node has been down since yesterday. I personally apologize for the outage. I’ve checked with Amazon today, since I couldn’t be able to before; I tried rebooting the instance, but the Amazon checks themselves failed to detect a properly running server. There’s a support ticket going
Internal Improvements & Early April Report
Hello, freeBNC users! A lot passed since last report, so let’s sum up changes. Most servers were reinstalled; with a downtime of ~2 minutes per server, they’re running fine since ~2 weeks. US2 moved from SiliconValley to AWS New servers! Namely, Netherlands and what you can see as «localhost» on status.freebnc.net, which is not used
Webchat back up on every server
Status minisite
Hello! In the past day, I’ve set up a mini-site for monitoring purposes, uptime and such. The informations you can see about each server are: Used/Free RAM Network Status (upload/download) Used/Free HDD Server Load (unix) Server Uptime ZNC Status The script also supports the drawing of graphs; just click on the time-lapse you wish to control. You can reach
Servers Migration Completed!
Servers Move – day #2
Servers Move
For organization and stability purpose, most servers are going to move. Those are: us2 br au ie sg This means the servers will be down for ~1h each; not all at once. You will be able to connect to the new server via the hostname new-servername.freebnc.net (e.g. new-us2.freebnc.net) while the original one propagates. US2 is going