NinerNet Communications™
System Status

Server and System Status

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: Outgoing mail may be delayed

31 July 2017 04:29:48 +0000

An email account on server NC027 was compromised in the last few hours, and it was used to send spam. This problem has been addressed by suspending the account, but the result is that outgoing email from the server may be delayed for the next few hours until automated anti-spam systems around the Internet react to our cleaning up the problem.

We apologise for this problem, and remind everyone to ensure that their computers are scanned regularly for viruses.

If you have any questions about this, please contact support. 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.

NC027: Mail server back online

23 November 2016 07:28:27 +0000

The mail server (NC027) has been restarted after cleaning up after a spammer. It was down for eight minutes between 07:09 and 07:17 UTC.

As a result of this incident, our mail server is being blocked by some mail services. We will work to have those blocks removed before they expire, but this will take some time.

These incidents usually arise after a computer has been infected with a virus. The virus then sends the email password back to the person or organisation controlling the virus, and they then use that information to compromise that email account on the mail server, using it to send thousands of spams from the account. Please ensure that you install, use and update an anti-virus program on your computer to ensure that this doesn’t happen to your email account.

We again apologise for this incident. Please contact us if you have any questions. Thank-you.

NC027: Mail server shut down

23 November 2016 07:11:41 +0000

We have temporarily shut down server NC027 to clean up after a spammer. It will be back up in a few minutes. We apologise for the inconvenience.

Chromium certificate issue resolved

17 November 2016 20:08:44 +0000

The issue with the Google Chromium web browser reporting valid certificates as “unsafe” has been resolved today with an update to Chromium.


Update, 2016-11-20: We’ve posted a commentary about this on our blog.

Issues with *.niner.net certificate

16 November 2016 10:34:52 +0000

We are aware that s small subset of users of the Chromium web browser may receive the following error when trying to access websites and control panels via HTTPS that use the *.niner.net certificate:

Your connection is not private

Attackers might be trying to steal your information from cp31.niner.net (for example, passwords, messages or credit cards). NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED

(cp31.niner.net will be replaced by whatever domain you are trying to access.)

If you click the “ADVANCED” link you will see the following additional information:

The server presented a certificate that was not publicly disclosed using the Certificate Transparency policy. This is a requirement for some certificates, to ensure that they are trustworthy and protect against attackers.

This is a bug in Google Chromium, not a problem with our certificate.

Until Google fixes this bug we recommend using a better web browser (e.g., Firefox), or clicking the “Proceed to cp31.niner.net (unsafe)” link that is revealed when you click “ADVANCED” as described above. Clicking the “unsafe” link is indeed safe in this case. Even very big and very busy websites — such as Yahoo and Flickr for example — are currently affected by this bug.

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: