|
|
|
Denver, Colorado is currently experiencing blizzard-like weather conditions. The NWS has issued a warning that will last until midnight tonight. We have NOC engineers on site at each of our locations and will continue to monitor all systems closely. We do not expect any service impacting issues.
You can track weather for our Denver location here - https://darksky.net/forecast/39.7479,-104.9892/us12/en
You can track weather for our DTC location here - https://darksky.net/forecast/39.618,-104.8916/us12/en
Read more »
|
|
|
|
|
Limited Support Availability 2018-12-14 2000-2259 MDT
Our staff is attending a company event and support team responses may be delayed during this time.
Thank you; we appreciate you and your understanding!
Read more »
|
|
|
|
|
[Completed, 22:07 12-16-18]: This maintenance is complete on all Nimble Storage Arrays. As expected, no impact to workloads was observed.
Date: December 16, 2018
Time: 9:00PM MT
Purpose of Work:
Nimble Storage has let us know that a couple of our storage arrays are running on a version of NimbleOS that has a bug that could result in an outage. We will be upgrading our storage arrays to newer firmware that is not impacted by this bug.
Impact of Work:
Historically, we have performed many Nimble Storage upgrades which have been completely hitless and not at all noticeable to any workloads consuming storage from our arrays. Accordingly, we do not anticipate any impact, but there is always a slim possibility that connectivity to the storage arrays will be disrupted, resulting in workloads relying on the storage to hard reboot.
Please contact us with any questions / comments / concerns.
Read more »
|
|
|
|
|
|
=Completion, Thu Nov 8 01:38:54 STD 2018
This maintenance is now finished. Further reboots for HA VMs will not be required, and all have returned to service.
=Update, Wed Nov 7 23:36:22 STD 2018
This maintenance will be extended tonight, as workflow has been slower than predicted, but impact to individual VMs is still minimal.
I will update this post when it is complete, or if we'll be dividing it into separate nights.
=Update, Wed Nov 7 21:18:28 STD 2018:
Some corrections and revisions:
This will actually impact all self-managed HA cloud servers as well. If you are not on our Hyper-V cluster, you will not be impacted.
-Servers will be updated and rebooted at the same time, with the exception of those that are part of a highly available application cluster of their own.
Servers will be updated 10 at a time, with the latency of the underlying storage monitored closely during maintenance. I still expect maintenance to be over within 1-2 hours, and individual impact will still be minimal.
We will begin, as scheduled, in 10 minutes.
===
Date: Wednesday, November 7, 2018
Time: 9:30PM - 10:30PM
Purpose of Work:
We will be updated the VM configuration version for all HA cloud servers, tomorrow night.
Impact Of Work:
Procedure will involve a graceful shutdown, a 1 minute upgrade process, and the server will then be turned back on.
Customers whose servers are being updated may notice 2-3 minutes of downtime, typically. We will be monitoring for any server that takes longer than this to boot up and regain services.
Servers will be updated and rebooted at the same time, with the exception of those that are part of a highly available application cluster of their own.
We will let you know if the maintenance ends ahead of schedule, or else update you regarding the status of this maintenance at the end of the scheduled window, with further information being forwarded to specific customers, if required.
Rescheduling:
If you would prefer to schedule your server reboot to occur at a specific alternate time, and have confirmed that you have one or more Fully-Managed Highly Available Cloud server ( that do not meet the previously specified exclusion criteria ), please reach out to support@handynetworks.com, or submit a ticket via our helpdesk, and specify your desired alternate update time before the scheduled update time.
Read more »
|
|
|
|
|
|
[Completion, Sun Aug 26 23:53:05 DST 2018]
All servers affected have been returned to service, with the majority having been rebooted without issue by 11:08.
The maintenance has concluded successfully, for the servers our update platform could reach. Servers that could not be reached by our update platform or servers that were listed as 'excluded' previously will have their updates scheduled separately, as needed.
[Update, Sun Aug 26 21:30:31 DST 2018]
We are now beginning this maintenance, and fully managed Centos 6+ servers (aside from those previously listed as excluded, and customer ID 2086) will be rebooted 5 at a time, starting now.
We'll keep you updated throughout the maintenance, and individual server owners will be updated as appropriate.
==
Date: Sunday, August 26, 2018
Time: 9:30PM - 11:30PM
Purpose of Work:
We will be updating kernels for, and rebooting all Centos 6 and Centos 7 servers under our management, excluding hypervisors, highly available clustered applications, and servers owned by customers with the following billing IDs:
1407
2171
2431
1001
This is to protect against the follow remote DOS exploit, that leverages vulnerabilities in the Linux kernel to deny services with any appropriately modified TCP packet: https://access.redhat.com/articles/3553061
Impact Of Work:
Customers whose servers are being updated may notice 2-8 minutes of downtime, typically. We will be monitoring for any server that takes longer than this to boot up and regain services.
Servers will be updated and rebooted 5 at a time.
We will let you know if the maintenance ends ahead of schedule, or else update you regarding the status of this maintenance at the end of the scheduled window, with further information being forwarded to specific customers, if required.
Rescheduling:
If you would prefer to schedule your server reboot to occur at a specific alternate time, and have confirmed that you have one of more Fully-Managed Centos 6 or 7 servers ( that do not meet the previously specified exclusion criteria ), please reach out to support@handynetworks.com, or submit a ticket via our helpdesk, and specify your desired alternate update time before the scheduled update time.
Read more »
|
|
