NinerNet Communications™
System Status

Server and System Status

NC036: Update 7

21 March 2026 02:31:38 +0000

Updates will now be sequentially numbered.

We’ve marked server NC036 as “degraded”, because that’s what it is. Email within the group of clients for which we are responsible works. With the outside world, it doesn’t.

Our live monitoring indicates that our uptime is 99.998%, but as we’ve indicated before, this is not 100% accurate. Even AI is “accurately inaccurate”.

You still have access to your account(s) on the server. Please do with that information what you consider to be best for your business.

NC036: A luta continua

21 March 2026 00:21:36 +0000

We implemented the permanent fix yesterday. However, the result seems to be the same: NO EMAIL.

I half expected that this would reveal to me that I had made a stupid mistake, and all this palaver was for nothing. That would have been supremely uncomfortable, but at least we’d all be online. But we’re not.

I know you, our clients, have struggled for the last two days. So have we, there is no doubt. I literally feel your pain.

We have two options at this point, but I want to make clear at the outset that your data — your 5.1 million emails, 2.9 terabytes — are safe. Additionally, I am still alive, which could be a positive or a negative for you, depending on how you view the situation.

Option one, and the option I’d prefer under normal circumstances, is to start fresh with a new mail server, and even just verbalising that fills me with that feeling you get at the beginning of a footrace. You don’t know if you’ll come first, or 101st, but goddam, you’re going to race your heart out.

Option two, to put it succinctly, is to know when to quit. It’s not the end I envisioned when I was supposed to hand over the business and our name in May last year, but nothing lasts forever.

Already I hear most of you leaning towards option two. I don’t blame you. Just get out of the way, Craig, and let me get my email and entrust it to someone with a bigger marketing budget.

If I choose option one, it’s going to take at least a week … and that’s being optimistic. So you will not be able to send or receive email for all of next week, and if everything works, you’ll be online by Monday, 30 March 2026 … I hope.

If I choose option two, that would be like giving the order to “abandon ship”; you don’t want to be in the cold water, but the only other option is even less palatable.

I’ve decided, after much soul searching and personal conversations today, to take option one.

Who knows what NinerNet will look like in a week or a month. However, I know what’s most important for me, and that is that you have your access to the 5.1 million emails you have entrusted to us. You will have access to them, and what you do with them will be up to you.

We will, as always, be communicative, and post updates here. We’re not ignoring your emails — which we ironically continue to receive — but our focus must be and is on keeping everyone as informed as possible.

NC036: Further update

20 March 2026 13:34:40 +0000

We continue to receive reports of continued problems from a very few clients.

We essentially addressed the problem on the evening (UTC) of 19 March. We have yet to put in place a permanent fix. The permanent fix is to attach a secondary volume, and move some back-ups onto the secondary volume, to free up space on the primary hard drive to store and process email. We have not done this yet.

However, we have freed up a huge amount of space, so the server is comfortably handling all the email thrown at it. This is the temporary fix.

The reported problems seem to focus on two areas:

  • Bounced email, and
  • Expected but not received emails.

We have been working on the mail server non-stop for about 21 hour now. We have rebooted the server once (in the morning UTC) and restarted applications a few times. During that time foreign mail servers may have been disconnected in the middle of trying to deliver an email, resulting in their bouncing the email with an error that refers to “losing the connection while receiving the initial server greeting”. Given how often this would have happened (not very much) we’re surprised to see this bounce, but it’s obviously happened. We can only expect these events to lessen as things return to normal.

We ourselves have noticed that emails from external/foreign sources have not been arriving lately. We can only expect that these emails are delayed, and we expect to receive them again in the next 24 hours. Please be patient.

If you check your domain at mxtoolbox.com you will find that it should comply with all or most requirement to have your email delivered. Not complying with every requirement is not necessarily a bad thing.

We expect to have the permanent fix in place within the next 12 hours, but the temporary fix is more than enough to keep the email flowing. Thank-you.

NC036: Most email flowing normally

20 March 2026 07:45:21 +0000

It seems, from monitoring our own company email, that email is flowing normally. However, tests I have done to my personal email address are still delayed. This doesn’t really make sense, as our server is not blocking any inbound email. We’re still working on the permanent fix, but in the meantime there is plenty of disk space to take in the biggest of emails.

NC036: Webmail works

19 March 2026 23:00:40 +0000

We have rebooted the mail server, so the webmail is working again. We don’t know how long that was generating an error, but it wasn’t reported by anyone until a few minutes ago.

NC036: Progress update

19 March 2026 18:15:15 +0000

This seems to be a disk space issue. We have freed up enough space that backlogged email has been released. There should be no problems sending and receiving email now, but we are still working to implement a permanent fix. Apologies for the interruption.

We will have further updates as we implement the permanent fix.

NC036: Mail server issues

19 March 2026 16:48:26 +0000

We have been informed that some clients (probably all) are encountering issues with the mail server. We are looking into the cause now.

NC033 & NC035: Progress report 1

14 November 2025 08:12:07 +0000

This is one of those operations that takes only a few minutes if you’ve done it a thousand times before. 🙂 But we’ve sort of addressed the imminent possible problem of our secondary mail relay service changing one of their requirements. To be frank, although this maintenance needed (and still needs) to be done, we’ve instead done a lot of manual work that has addressed the immediate problem before the weekend.

But we do need to spin up two new nameservers; it’s been at the top of our list for some time, and will greatly improve how you will be able to manage the nameservice for your domains. Since we last did this a few years ago we’ve found that we have greater choice of software and methods than we had before, and so we’re going to take some time over the weekend to evaluate a number of different options. Finishing the maintenance over the weekend will also ensure that we avoid stepping on anybody’s toes in the middle of their changing their DNS.

We will finish over the weekend and continue to post further updates here. Thank-you for your patience.

NC033 & NC035: Nameservers undergoing replacement

13 November 2025 14:33:24 +0000

We need to replace our two nameservers (NC033 and NC035) in short order. Under normal circumstances this would be a seamless operation, of which we could just notify you after the fact. However, we always notify you of planned maintenance in advance anyway, but in this case we are under a tight deadline to do this due to changed requirements at our secondary mail relay service.

Our plan is to carry out this operation over the next few hours. It’s unclear whether SMTP2GO’s deadline is in the UTC time zone or in New Zealand where the company is located. If the deadline is in the UTC time zone then we’ll be finished long before the deadline. There will be no downtime, but if there is any interruption if will be for some outbound email. We will work to avoid this and implement workarounds if necessary.

There will be a new look with a new control panel next time you log into dns.niner.net. In one of our next few posts we will post screenshots of the new control panel so that you know what to expect.

If you have any questions, please contact NinerNet support. We will post updates as necessary as work progresses. Thank-you.

NC041: PHP upgrades complete

28 June 2021 03:41:51 +0000

We continued last weekend’s maintenance this weekend, and as a result the latest iterations of PHP versions 7.3, 7.4 and 8.0 have been installed on server NC041. This means that you can log into your account in the server’s control panel to upgrade your version of PHP to the version of your choice. We do recommend that you upgrade to the latest version (8.0.7), but it’s possible that your web application may have different requirements. If you have trouble with PHP 8, we suggest downgrading incrementally until you’re running a version that works for you. If you can’t run 8.0, you’re welcome to contact us if you think the issue is on our server, but generally you will need to contact the provider of the web application.

To effect the upgrade for a single website, please follow these instructions:

  1. Log into the control panel.
  2. If you have more than one website, select the domain from the drop-down list in the top, left-hand corner.
  3. Navigate to Server Configuration -> PHP Options.
  4. Leaving other PHP options as they are already set, click the drop-down list of PHP versions to the right of “Default HTML directory”.
  5. Select the latest version (highest number) from the drop-down list. (This is also where you would select any other version if you so wish.)
  6. Click the “Save” button underneath “PHP information”.
  7. Let the following page load, and you’re done!

If you have any issues successfully carrying this out, please contact NinerNet support, and we will assist.

Thank-you.

NinerNet home page

Systems at a Glance:


Loc.SystemStatusPing
Server NC023, London, United Kingdom (Relay server), INTERNAL.NC023InternalUp?
Server NC028, Vancouver, Canada (Monitoring server), INTERNAL.NC028InternalUp?
Server NC031, New York, United States of America (Web server), INTERNAL.NC031InternalUp?
Server NC033, Toronto, Canada (Primary nameserver), OPERATIONAL.NC033OperationalUp?
Server NC034, Lusaka, Zambia (Phone server), INTERNAL.NC034InternalUp?
Server NC035, Sydney, Australia (Secondary nameserver), OPERATIONAL.NC035OperationalUp?
Server NC036, Amsterdam, Netherlands (Mail server), DEGRADED.NC036DegradedUp?
Server NC040, Toronto, Canada (Web server), INTERNAL.NC040InternalUp?
Server NC041, New York, United States of America (Web server), OPERATIONAL.NC041OperationalUp?
Server NC042, Seattle, United States of America (Status website), OPERATIONAL.NC042OperationalUp?

Subscriptions:

RSS icon. RSS

Twitter icon. Twitter

Search:

 

Recent Posts:

Archives:

Categories:

Links

Tags:

.co.zm domains .com.zm domains .zam.co domains back-up bounce messages browser warnings connection issues control panel database dns dos attack dot-zm domains down time email email delivery error messages ftp hardware imap mail mailing lists mail relay mail server microsoft migration nameservers network networking performance php phplist pop reboot shaw shaw communications inc. smtp spam spamassassin ssl ssl certificate tls tls certificate viruses webmail web server

Resources:

On NinerNet: