NinerNet Communications™
System Status

Server and System Status

Twitter account

28 December 2024 20:06:02 +0000

We have all but officially abandoned our Twitter account. We just need to take the link off of this status website and close our account. In fact, we tried to close our account, but we couldn’t log into it even though we were allegedly sent a “confirmation code” to our extant email address. Twitter/X is completely broken.

If you visit our account or any of our few posts you will find that Twitter/X have “fixed” it/them by redirecting you to their home page so, really, we have not abandoned Twitter/X, they and Elon Musk have abandoned us and many other former Twitter users. Twitter has gone from a great communication tool, that we nevertheless didn’t use to its full capability, to a complete waste of time, and we won’t waste any more time with it.

Considering we never used Twitter to its full extent, it’s not likely we’ll replace it. You can subscribe to this blog’s RSS feed and be informed of posts here — which, other than this one, are all important status updates — just as quickly, so why bother?

Upcoming nameserver infrastructure changes

28 December 2024 03:53:34 +0000

We are alerting our clients to some upcoming work on our nameserver infrastructure.

With immediate effect, right after this blog post, we will be changing the nameservers for our infrastructure domain, ninernet.net. This will, seamlessly, transfer the management of this domain, which underpins all of NinerNet‘s servers; each server has a DNS (domain name system) name based on the ninernet.net domain — e.g., the primary mail server is nc036.ninernet.net and the primary web server is nc041.ninernet.net. As stated, this transition should be seamless and will not be noticed by any of our clients. The new nameservers for this domain (ninernet.net) are already set up, and the only thing that is changing is where other servers on the Internet will look for authoritative information for the ninernet.net domain.

The second part of this plan is to set up new nameservers for all of our clients with a new and improved control panel. However, this phase will not take place until January. At that time we will advise clients what you need to know.

Please note that the ninernet.net domain is not the niner.net domain; the niner.net domain is, of course, our primary domain for all web and email purposes; on the other hand, the ninernet.net domain, which we registered in 2005, is purely an infrastructure domain. About the only time you will see it is when we refer to it like this and when you look at the extended headers of your email messages.

Thank-you in advance for your attention to this matter, although no action is needed on your part.


Update, 2024-12-28: Domains that use the ANAME record type may experience issues on their websites. We’ll be addressing these individually as they arise.

NC036: Mail server is back to normal

20 December 2024 13:51:23 +0000

Server NC036 (the primary mail server) is back to normal. All mail in the mail queue has been cleared and delivered to all local accounts and remote/foreign domains.

We do not currently have an explanation for this occurrence, but we are looking into it. Our apologies for the interruption.

If you have any specific questions or issues with this now-resolved event, please contact NinerNet support. Thank-you, and we apologise for this incident.

NC036: Mail server update

20 December 2024 13:28:50 +0000

Server NC036 is recovering. Delayed email is being delivered and the mail queue is decreasing.

NC036: Server is temporarily struggling

20 December 2024 13:07:52 +0000

Server NC036 (the primary mail server) is temporarily struggling under an unusually large mail load. We are working to determine the cause of this and bring everything back to normal.

In the meantime you may experience delays in sending or receiving messages.

We will update as and when there is new information.

NC041: Maintenance concluded

24 November 2024 22:10:24 +0000

Our weekend maintenance is over and complete, save for the one WordPress website that won’t update. This particular website is an ongoing problem, but when the update is run from within WordPress the update works. So we’ll be asking that client to do that themselves.

The server was rebooted four times, with a total downtime of a little under six minutes over the course of about four hours … actually, quite a bit less, as I was reading an article with respect to replacing the operating system on all of our servers. Time flies when you’re reading!

Everything is running just fine on server NC041 now. If you have any questions or concerns, please contact NinerNet support. Thank-you for your patience and understanding.

NC041: Server maintenance in progress today

24 November 2024 17:48:58 +0000

During our weekend maintenance window we are working on dealing with some WordPress upgrades on server NC041 that are not going as planned. The server may be rebooted a number of times. During this maintenance our third-party monitoring will be paused, as it usually is during scheduled maintenance.

Once we are done we will post an update here. We don’t expect to cause much in the way of interruptions, but we are letting you know in advance in case you notice. Thanks for your patience.

NC041: Server reboot complete

19 November 2024 12:44:20 +0000

NC041 has been rebooted and is again online and serving websites. Our apologies for the brief interruption. It was down for about a minute.

NC041: Emergency reboot

19 November 2024 12:36:23 +0000

In a few minutes we will be rebooting NC041, the primary web server. It should only be down for about a minute, and we’ll post here again as soon as it is up.

NC036: Evaluating the effectiveness of being listed in the UCEPROTECT whitelist

19 July 2024 03:57:16 +0000

Just about a month ago we became aware of the problem with delivering email to Microsoft-hosted domains. At that time, one of the actions we took was to pay to have our mail server’s IP address listed in the UCEPROTECT whitelist that effectively removed our IP address from a huge list of blacklisted IP addresses that are only listed because of the lackadaisical approach of our data centre (Digital Ocean) to removing spammers from their network of data centres.

We weren’t certain at the time that this action would achieve anything and, to be frank, we have no concrete evidence to believe that our doing so has had the desired effect. We think there is strong evidence that it has, but there is no way we can determine that definitively. The strong evidence is that we have had very few problems with mail to Microsoft-hosted domains since a couple of days after the problem started on 20 June.

Our subscription to this whitelist expires on Monday the 22nd. To test the effectiveness of this subscription we are going to allow it to lapse. If we see a sudden uptick in email messages to Microsoft-hosted domains bouncing then we’ll take that as evidence that the subscription is working, and we’ll immediately renew it. In that case, messages you send to such domains will bounce temporarily, so please forward those bounce messages to NinerNet support and we will immediately divert future messages to those domains via our secondary outbound mail servers. This is a temporary and planned test; if these bounces happen it is not evidence that our systems are failing for any reason. If they don’t bounce then we will have learned that our paying for the listing is a waste of money.

The purpose of this message is to let you know of this test in advance. We expect that if messages start bouncing again and we renew the subscription, everything will be back to normal within about 24 hours, and immediately for domains we add to our mail server configuration to have messages go out via our secondary mail server. That said, we have also found that retrying if you get a bounce in this situation sometimes succeeds! It’s bizarre.

Thank-you for your continued patience with issues like this thrown at us by massive providers that don’t care about you, people who choose to host with their competitors.

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: