NinerNet Communications™
System Status

Server and System Status

NC027: Upgrade complete

24 July 2016 02:33:21 +0000

The upgrade of server NC027 was completed at 02:22 UTC, and the server is up and running. Thanks for your patience.

NC027: Upgrade in progress

24 July 2016 01:56:01 +0000

The upgrade of NC027 started at 01:47 UTC and is currently in progress.

NC027: Upgrade update

24 July 2016 00:08:15 +0000

We’re going to continue holding back the upgrade of NC027 for another two hours and re-evaluate at that time. Our apologies for the delays.

NC027: Server upgrade postponed

23 July 2016 23:17:27 +0000

Due to the possibility of significant delays, we are postponing the upgrade of NC027 scheduled for this time for another hour. We’ll reassess the situation at that time and re-evaluate. Updates will be posted here.

Thanks for your patience.

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.

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.

NC027: Hotmail delivery update 4

20 April 2016 01:48:58 +0000

As of this moment, the NC027 IP address is no longer blocked by Microsoft on their Hotmail / Outlook.com / Windows Live service. Additionally, test messages we’ve sent have been delivered to the in box of the test account. We have removed the workaround.

NC027: Hotmail delivery update 3

19 April 2016 10:04:35 +0000

As I was hitting the “publish” button on the last update, another email came in from Microsoft that contradicted the email we had received just 68 minutes earlier. The latest email states, “Our investigation has determined that the [NC027 IP address does] not qualify for mitigation.”

We will continue to jump through Microsoft’s hoops, but in the meantime the workaround is still in place.

NC027: Hotmail delivery update 2

19 April 2016 09:47:19 +0000

After literally begging for a review of the situation and making three submissions to Microsoft, they have finally granted the IP address of server NC027 a “conditional mitigation”. This means that they have removed the block on this mail server’s IP address, but will put it back the second they see any reason to do so. Because they say that it will take 24-48 hours for this to propagate throughout their system we will leave the workaround in place for at least that long.

Two things have become clear from this and the Yahoo situation:

  • Dealing with megalithic entities like the all-powerful, large, free webmail providers — Yahoo, Hotmail, Gmail and their ilk — and their drone-like employees who are only allowed to copy and paste canned responses, is supremely frustrating.
  • We have a growing problem on our hands as a result of their huge footprint and their lack of concern for the many other companies like NinerNet on the Internet.

On the latter point, as stated in our first post on this issue with Hotmail, if you’re running a mailing list by blind-copying (or, even worse, simply cc’ing!) any more than about a dozen email addresses (of close friends or family or colleagues), we suspect that this may be the cause of the recent problems. Within the next 30 days — and hopefully much sooner than that — we will be implementing limits on the number of email addresses that can be cc’d or bcc’d in a single message. If you’re doing this, please contact us as soon as possible for options to ensure that your mailing list can continue to operate. It would be better to contact us as now in order to avoid disruptions to your mailing lists later.

Thank-you for your patience.

NC027: Hotmail delivery update

19 April 2016 01:39:45 +0000

We are still waiting for a response form Microsoft on this issue. In the meantime we have implemented a workaround that we developed during the Yahoo situation that will get email through to Hotmail and their domains, but there is a high likelihood that email to Hotmail domains will end up in the recipients’ “junk” or “spam” folders.

We will post further updates here as they become available.

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: