NinerNet Communications™
System Status

Server and System Status

NC031: Database restarted

16 October 2017 21:30:51 +0000

The database on server NC031 was restarted at 21:25 UTC and is online and working again. We are investigating the cause of this issue.

NC031: Database issues

16 October 2017 21:03:09 +0000

We are investigating a database issue on server NC031 that is affecting database-driven websites. We will report details here.

NC018: Server back online

9 September 2017 14:39:20 +0000

No sooner had I clicked “publish” on that last post than the server was put back online. Again, we apologise for the service interruption.

NC018: Server taken offline prematurely

9 September 2017 14:30:56 +0000

Somebody at our data centre jumped the gun, and has taken server NC018 offline two days earlier than it should have been taken offline. This is (or will shortly be) causing a problem for all services on most domains, including our own.

We are waiting for the data centre to reactivate the server, and will update this ticket as it’s possible to do so.

We very sincerely and humbly apologise for this situation.

Access to control panel on server NC018

28 August 2017 21:16:37 +0000

Access to the control panel on server NC018 has been temporarily blocked while we deal with an issue on there. At this point, the only service provided by server NC018 is “nameservice”, as all client websites and email have been migrated to newer servers. Therefore the only reason you might need access to this control panel it to make changes to the DNS for your domain.

If you need to make changes to your domain’s DNS, please contact us with the changes you would like to make, and we will assist you as soon as possible. Thank-you, and we apologise for the inconvenience.

NC027: Mail server emergency maintenance

23 February 2017 16:22:59 +0000

The mail server (NC027) was shut down between 16:08 and 16:11 UTC this (Thursday) afternoon for some emergency maintenance. This would have resulted in a brief interruption in your ability to send and receive email.

If you have any questions about this, please contact us. Thank-you.

NC027: Mail server report

30 January 2017 13:18:24 +0000

We have not yet been able to determine a cause of the problem with the mail server (NC027). It seems that it stopped processing mail at 08:46 UTC, which means it was unavailable for 56 minutes until it was up and running again at 09:42 UTC. The server didn’t become completely unresponsive to monitoring until about 09:25 UTC, which is when the problem came to out attention. A few minutes later, after determining that the server was completely inaccessible and posting to our status page, we issued a full reboot. After a few minutes of disk scanning, the server was back online and processing email.

We apologise again for this brief interruption in service. If you have any questions, please contact us and we will be happy to respond.

NC027: Mail server rebooted

30 January 2017 10:01:07 +0000

The mail server (NC027) was rebooted and back online at 09:42 UTC. We are looking into the problem and will post an update here within the next two hours.

We apologise for the inconvenience.

NC027: Problem on mail server

30 January 2017 09:34:18 +0000

We are aware of a problem with the mail server (server NC027). We are looking into it and will post an update here as soon as possible.

NC031: Explanation of 29 September outage

28 October 2016 12:59:14 +0000

Our apologies for not posting this promised update in a timely manner.

The reason server NC031 was taken offline by the data centre was because one of the websites on the server had been compromised, and was being used to attack other machines on the Internet. Coincidentally, we had changed our contact email address with the data centre only a few days previously and deleted the previous address. However, their system required us to change our email address in two different places. We were not aware of this, and so the emails sent to us warning us of the problem did not reach us. Because they didn’t hear from us that we were aware of and addressing the problem, the server was disconnected to prevent further malicious activity.

We have pointed out to the data centre how their unnecessarily redundant system caused the communication problem, and in the meantime have ensured that our contact information is fully up-to-date with them.

The specific website that was compromised was removed from the server, and a clean account was reinstated. In the process we felt it necessary in the last couple of days to suspend outbound email from the server, so automated emails sent from the server were delayed. Having addressed the root cause, outbound email service has been reinstated.

If you have any questions or concerns about this incident, please contact support and we will address the issue. Thank-you for your patience, and our apologies again for the disruption.

NinerNet home page

Systems at a Glance:


SystemStatusPing
NC020OperationalPing
NC023OperationalPing
NC024InternalPing
NC027OperationalPing
NC028InternalPing
NC031OperationalPing
NC033OperationalPing

Subscriptions:

RSS icon. RSS

Twitter icon. Twitter

General Information:

This blog provides information about the status of NinerNet Communications systems. Dates and times of posts to this blog are in the UTC time zone, and dates and times given for events are also in the UTC time zone, although conversions may be offered for some time zones common to our clients. Please use the World Time Server to ensure accurate conversion of dates and times to your own time zone.

Search:

 

Recent Posts:

Archives:

Categories:

Links

Tags:

.co.zm domains .com.zm domains .zam.co domains browser warnings connection issues database dns dos attack dot-zm domains down time email delivery ftp hardware mailing lists mail relay migration nameservers performance phplist reboot smtp spam spamassassin ssl ssl certificate tls tls certificate web server

Resources:

Unable to open ninernet_xsite: Access denied for user 'ninernet_x_site'@'173.45.228.52' to database 'ninernet_xsite'