Router Maintenance Window Friday Dec 1st, 12:01am EST

Stephen

Stephen

US Operations
Staff member
Maintenance Window - 12:01 AM until 12:31 AM EST, Friday Dec 1

Hardware: Core Router

Reason: We will be making some routing changes that are purely software. There will be a momentary loss of connectivity as the routes reload after the configuration change.

There should be no more than 5 minutes of outage in this change, but we are allocating a 30 minute window if there is any problem in the process.

If connectivity is lost, we maintain jodopulse.com as an external contact point, and the Live Chat is provided by a 3rd party and will be up during this time as well. The links to reach our techs over live chat are available on both Jodohost.com and Jodopulse.com.
 
Dated: Thursday Nov 30 7:25PM EST

We have been told by our upstream providers that we should wait an additional 24 hours before making these routing changes. That will move the maintenance to Saturday Dec 2nd, 12:01am until 12:31am EST.

We will be emailing this update as well.
 
Due to critical technical issue at DC, there has been a delay in the scheduled uptime of network services. We are working with upstream providers to get this up and working as fast as possible.
 
All IPs are up, at the point Prakash posted many IPs were up and alive, but some 30-40% of IPs were not routing fully.

This was scheduled maintenance gone bad, it was not bad on our part but upstream there were to be some changes with the providers and the changes were, as sour as can be. They were reverted within 20 minutes and the problems continued.
In fact in this whole process no changes were made on our part, it was all on the upstream providers. We were told to expect a 30 second connection blip, that turned into 3 hours for some IP addresses. I am personally unhappy about the situation and will not be allowing such changes in the future without knowing exactly what commands they will be running to evaluate if it will affect us or not.
 
Everything has been back up for a while now
This maintenance has been a total disaster, and part of the blame is some poor practices by our outstream (internap)
We apologise for the downtime. We will come up with an explaination for this once all facts are revealed
 
You must log in or register to reply here.
Back
Top