NinerNet Communications™
System Status

Server and System Status

Migration of websites

17 July 2017 07:36:44 +0000

We are moving the remaining websites on server NC018 to server NC031. This will result in automated emails with important configuration information going out to the designated contact for each domain. Please save these emails for future reference.

If you have any questions, please contact us. Our own website will also be moving, so if you have trouble with our contact form please email us at migration201707@niner.net. Thank-you.

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.

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.

NC031 upgrade complete

16 July 2016 23:28:00 +0000

The upgrade of server NC031 was completed at 23:16 UTC, and the server is up and running. Thanks for your patience.

In light of this much faster upgrade we’re going to suggest that the bigger upgrade of server NC027 next weekend shouldn’t take nearly as long as is currently scheduled.

NC031 upgrade in progress

16 July 2016 23:10:01 +0000

The upgrade of NC031 started at 23:06 UTC and is currently in progress.

NC027 and NC031: Server upgrades

13 July 2016 22:02:41 +0000

The above two servers — the primary mail (NC027) and web (NC031) servers — will undergo hardware upgrades during our regular weekend maintenance windows this weekend and next:

* 16 July, 23:00 UTC: NC031, duration approximately 2 hours
* 23 July, 23:00 UTC: NC027, duration approximately 7 hours

Please click on the above dates and times to use the World Time Server website to convert to your local time zone. The above durations are only estimates. Down time will be slightly less, as some of the work can be done while the servers are still up, and there’s always the possibility that the work will finish more quickly. However, please plan for the servers to be down for the entire durations stated above.

Incoming email during the maintenance of server NC027 on the weekend of 23 July will be held on the sending servers and delivered once the server is back online. No email will be lost.

During the maintenance this status website will be available, and we will post updates when the maintenance starts and ends, as well as during if necessary.

If you have any questions or concerns, please contact us to let us know. Thanks for your patience and understanding as we work to improve our service to you.

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.

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: