NinerNet Communications™
System Status

Server and System Status

NC020: Server rebooted

20 November 2015 10:07:39 +0000

We have rebooted server NC020 after it was overwhelmed. We’re looking into it right now and will post details here as soon as we have them.

NC027: Mail server queue clearing

2 November 2015 10:05:03 +0000

A configuration change on server NC027 (the mail server) over the weekend to once again introduce virus scanning has, as on previous occasions, overloaded the server. We made this change over the weekend after earlier doubling the capacity of the server and making other changes recently that should have seen a significant increase in server performance. Indeed, testing over the weekend showed a significant improvement over previous attempts to introduce virus scanning.

The result of this is that incoming emails have been delayed this morning, including messages between accounts on the same server. Therefore we have again reversed this configuration change and the mail queue has begun clearing. We hope that it will be clear within the next hour.

We apologise for this inconvenience.

NC027: Access issue update

18 September 2015 19:43:54 +0000

After spending some time on this issue yesterday and today — and receiving a complaint from only one client who later informed us that the issue no longer existed — we’re closing this matter and considering it a transient network issue, probably closer to the client’s ISP than to server NC027.

Apologies for the false alarm, but we do take your complaints seriously.

If you have any questions or concerns, please let us know by contacting NinerNet support. Thank-you.

NC027: Access issues

17 September 2015 20:49:50 +0000

We are aware of an issue with server NC027, where most client email is hosted. However, we have not yet determined exactly what the problem is. Some services on the server are accessible, while some are not.

We are currently working with the data centre to determine the issue, and will post further updates here.

NC020: Credits for outage

11 September 2015 19:16:40 +0000

Further to our previous posts, we will be processing credits to the accounts of all affected clients for the outage on NC020.

NC020: Web server stoppage update

11 September 2015 18:59:36 +0000

After some research, combing of the logs on the server, and reading of documentation, we believe we found a reason that the web server stopped working, but we believe the cause evaporated when, in our desire to get everything working again as quickly as possible, we just rebooted the machine after other options to restart the web server failed. However, even the suspected cause does not fully jibe with the observed symptoms.

The good news is that we have recently commissioned a new server (NC030) to take on the websites hosted on NC020. We are still working on setting up the control panel on that, but we hope to have it in production as soon as possible.

We apologise for this incident, and thank you for your patience and understanding.

NC020: Server rebooted

11 September 2015 14:20:56 +0000

The web server on NC020 was found to be unresponsive today, but would also not respond to commands to restart. As a result we rebooted the machine and this seems to have fixed the problem.

We’re busy analysing the logs to determine the cause, and will post an update here if we find anything.

NC027: Delayed mail

23 July 2015 07:59:00 +0000

Due to a recent configuration change, the mail queue on server NC027 was not able to keep up with this morning’s (UTC) mail volume, and mail was backlogged and delayed. We have reversed the configuration change and the mail queue is currently clearing.

We apologise for the inconvenience.

NC020: Reboot required

21 April 2015 19:47:58 +0000

There were some file consistency issues on server NC020 that started at 17:47 UTC today.

Websites on the server remained online during the problem, but no logging would have happened during that time. Incoming email to aliased domains was delayed during the issue as well.

A file system consistency check was done and the server was rebooted 30 minutes later at 18:17. This solved the issue.

NC027: Server rebooted

30 December 2014 05:55:30 +0000

Server NC027 was rebooted at 05:43 UTC after being found unresponsive. We are looking into the cause of the issue.

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), OPERATIONAL.NC036OperationalUp?
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: