NinerNet Communications™
System Status

Server and System Status

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.

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.

NC031: Server back online

29 September 2016 05:22:50 +0000

Server NC031 is back online. We are investigating the reason that it was taken offline, and will report our findings here within 24 hours.

We apologise for the inconvenience.

NC031: Server offline

29 September 2016 05:01:19 +0000

Server NC031 has been disconnected from the Internet by the data centre. This affects most website hosted with us, but not email.

We are working with them to get in back online and will post further updates here as they become available. We apologise for the inconvenience.

NC020: Web server problem

4 June 2016 06:49:09 +0000

The web server on server NC020 experienced a problem at 04:45 UTC on 4 June 2016, and shut itself down. The problem was rectified at 06:00.

We apologise for the problem, and will resume migration of the websites on NC020 to NC031 this coming week. If you have asked us to delay the migration of your website, please contact us if you still need a further delay.

Server NC031 update

7 April 2016 08:33:44 +0000

We are moving the problem website to a new server. In the meantime it will be suspended to avoid further disruptions.

Capacity issues on server NC031

7 April 2016 07:42:20 +0000

We are experiencing problems with server NC031. These are caused by a very busy website that we transferred to this server about 48 hours ago.

We are assessing the situation and will post updates here. We apologise for the problem.

London network restored

27 December 2015 10:17:45 +0000

The data centre informs us that connectivity on their network was restored at 09:24 UTC.

We have been able to confirm this by accessing all of our servers in this data centre:

  • Incoming mail is once again being processed immediately by server NC027, although any incoming mail sent during the disruption may be delayed a little longer until the sending mail servers try again. This is not under our control.
  • Server NC023 is also processing email immediately.

We apologise for this interruption. Denial of service attacks (especially distributed denial of service attacks) are extremely difficult and expensive to fight. We have confidence that the data centre did everything they could as quickly as they could to combat this attack.

London data centre DDoS update

27 December 2015 08:30:17 +0000

We have been updated that the denial of service attack against the London data centre is actually a large distributed denial of service (DDoS) attack, and it is still underway. Efforts are being made at multiple levels on the network to combat this attack, and we are seeing some movement of email through server NC027, although it took an hour and forty-seven minutes for a test message to get through. This indicates, as mentioned earlier, that the server is up and processing email, but that other servers (and our clients, obviously) are having problems connecting to the server.

We apologise for these problems, but this is affecting a wide range and large number of companies hosted at this data centre, not just NinerNet.

Updates will continue to be posted here as we learn more.

Connectivity issue at London data centre

27 December 2015 06:52:18 +0000

The London data centre has been suffering from the effects of a couple of denial of service (DoS) attacks over the last 12 or so hours. The attack late yesterday (26 December) lasted about an hour and a half. Today’s attack started at 05:37 UTC and is currently ongoing. The data centre staff assure us that they have identified the problem and are implementing a fix for it.

This affects server NC023 (the relay server) and server NC027 (the main mail server), as well as virtual private servers hosted in London. As far as we know, the servers themselves are up and connected to the network, but the attack is causing them to be inaccessible.

We’ll update here as soon as we know more.

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 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'@'nc020.ninernet.net' to database 'ninernet_xsite'