Juniper storingen
Omstreeks 13:49 heeft zich een storing voorgedaan in het netwerk, inmiddels zien wij geen problemen meer. Onze engineers hebben het probleem in onderzoek.
Er is een bottleneck aan het licht gekomen op jun1.bit-2a tijdens een specifieke actie binnen ons eigen netwerk. Uiteraard voeren we deze specifieke actie niet uit tot we deze bottleneck opgelost hebben. Het incident is opgelost.
In de nacht van maandag 19 op dinsdag 20 mei van 0:00 tot 01:00 voeren we onderhoud uit aan ons netwerk. We gaan de nieuw geleverde Juniper apparatuur aansluiten op onze core-routers. De apparatuur zal gaan meedraaien in ons netwerk, maar zal nog niet actief verkeer gaan verwerken.
Update: Wegens omstandigheden kon de engineer van Quanza niet aanwezig zijn bij het onderhoud. We plannen een nieuwe datum.
In de nacht van maandag 19 op dinsdag 20 mei van 0:00 tot 01:00 voeren we onderhoud uit aan ons netwerk. We gaan de nieuw geleverde Juniper apparatuur aansluiten op onze core-routers. De apparatuur zal gaan meedraaien in ons netwerk, maar zal nog niet actief verkeer gaan verwerken.
Startdate: June 13th 2013 05:30:00 (CEST)
Enddate: June 13th 2013 07:00:00 (CEST)
Dear Sir/Madam,
As part of our commitment to continually improve the level of service you receive from LeaseWeb we are undertaking this maintenance.
We are going to upgrade our high volume routers at EvoSwitch dataceter with the new version of Juniper software which is supposed to fix a bug which affected us several times in the past.
The maintenance will take place between 05:30 and 07:00 CEST (UTC+2) on the 13th of June 2013.
Please note there is a similar maintenance announced for 11th June. If the IP addresses of your servers match the following list, you may experience downtime on either 11th or 13th of June.
This are prefixes configured in that part of the network:
5.79.80.0/22
62.212.72.0/23
62.212.82.0/23
62.212.85.0/24
62.212.88.0/23
82.192.78.0/24
82.192.84.0/23
82.192.90.0/23
82.192.94.0/23
83.149.70.0/23
83.149.124.0/22
85.17.24.0/21
85.17.72.0/23
85.17.90.0/24
85.17.132.0/24
85.17.136.0/24
85.17.147.0/24
85.17.172.0/24
85.17.190.0/23
95.211.88.0/22
95.211.128.0/22
95.211.132.0/23
95.211.136.0/21
95.211.144.0/20
95.211.200.0/21
2001:1af8:4010::/44
2001:1af8:4600::/40
…………
46.243.0.0/22
46.243.4.0/23
146.185.0.0/23
190.105.0.0/24
212.7.204.192/26
212.7.206.128/27
212.7.212.0/23
216.59.55.0/24
216.59.59.0/24
216.59.60.0/24
[ UPDATE ]
We will combine this maintenance with the chassis swap thus we expanded the maintenance window to 90 minutes, however the actual downtime of your services shouldn't be more than 45 minutes.
[Update 13-06-2013 07:10:00 CEST]
We have completed the maintenance successfully and all circuit back online.
Should you encounter any problems, please contact [email protected]
[Update 13-06-2013 07:50:00 CEST]
We have some issues with the routing engine, some circuits are having issues, we are busy fixing it.
Further updates will be posted when done.
[Update 13-06-2013 08:20:00 CEST]
We have severe issues and had to force reload the router engine linecard.
Further updates will be posted when done.
Sorry for the inconvenience caused.
[Update 13-06-2013 08:33:00 CEST]
After reloading the router all sessions are back up again and all circuit back online.
Sorry for the inconvenience caused.
Should you encounter any problems, please contact [email protected]
Startdate: June 11th 2013 06:00:00 (CEST)
Enddate: June 11th 2013 06:30:00 (CEST)
Dear Sir/Madam,
As part of our commitment to continually improve the level of service you receive from LeaseWeb we are undertaking this maintenance.
We are going to upgrade our high volume routers at EvoSwitch dataceter with the new version of Juniper software which is supposed to fix a bug which affected us several times in the past.
The maintenance will take place between 06:00 and 06:30 CEST (UTC+2) on the 11th of June 2013.
Please note there is a similar maintenance announced for 13th June. If the IP addresses of your servers match the following list, you may experience downtime on either 11th or 13th of June.
This are prefixes configured in that part of the network:
5.79.80.0/22
62.212.72.0/23
62.212.82.0/23
62.212.85.0/24
62.212.88.0/23
82.192.78.0/24
82.192.84.0/23
82.192.90.0/23
82.192.94.0/23
83.149.70.0/23
83.149.124.0/22
85.17.24.0/21
85.17.72.0/23
85.17.90.0/24
85.17.132.0/24
85.17.136.0/24
85.17.147.0/24
85.17.172.0/24
85.17.190.0/23
95.211.88.0/22
95.211.128.0/22
95.211.132.0/23
95.211.136.0/21
95.211.144.0/20
95.211.200.0/21
2001:1af8:4010::/44
2001:1af8:4600::/40
…………
46.243.0.0/22
46.243.4.0/23
146.185.0.0/23
190.105.0.0/24
212.7.204.192/26
212.7.206.128/27
212.7.212.0/23
216.59.55.0/24
216.59.59.0/24
216.59.60.0/24
[UPDATE 06:30] The maintenance has been successfully performed, and as far as we can see the bug has been resolved by this update.
Startdate: June 13th 2013 05:30:00 (CEST)
Enddate: June 13th 2013 07:00:00 (CEST)
Dear Sir/Madam,
As part of our commitment to continually improve the level of service you receive from LeaseWeb we are undertaking this maintenance.
We are going to upgrade our high volume routers at EvoSwitch dataceter with the new version of Juniper software which is supposed to fix a bug which affected us several times in the past.
The maintenance will take place between 05:30 and 07:00 CEST (UTC+2) on the 13th of June 2013.
Please note there is a similar maintenance announced for 11th June. If the IP addresses of your servers match the following list, you may experience downtime on either 11th or 13th of June.
This are prefixes configured in that part of the network:
5.79.80.0/22
62.212.72.0/23
62.212.82.0/23
62.212.85.0/24
62.212.88.0/23
82.192.78.0/24
82.192.84.0/23
82.192.90.0/23
82.192.94.0/23
83.149.70.0/23
83.149.124.0/22
85.17.24.0/21
85.17.72.0/23
85.17.90.0/24
85.17.132.0/24
85.17.136.0/24
85.17.147.0/24
85.17.172.0/24
85.17.190.0/23
95.211.88.0/22
95.211.128.0/22
95.211.132.0/23
95.211.136.0/21
95.211.144.0/20
95.211.200.0/21
2001:1af8:4010::/44
2001:1af8:4600::/40
…………
46.243.0.0/22
46.243.4.0/23
146.185.0.0/23
190.105.0.0/24
212.7.204.192/26
212.7.206.128/27
212.7.212.0/23
216.59.55.0/24
216.59.59.0/24
216.59.60.0/24
[ UPDATE ]
We will combine this maintenance with the chassis swap thus we expanded the maintenance window to 90 minutes, however the actual downtime of your services shouldn't be more than 45 minutes.
Startdate: June 13th 2013 06:00:00 (CEST)
Enddate: June 13th 2013 06:30:00 (CEST)
Dear Sir/Madam,
As part of our commitment to continually improve the level of service you receive from LeaseWeb we are undertaking this maintenance.
We are going to upgrade our high volume routers at EvoSwitch dataceter with the new version of Juniper software which is supposed to fix a bug which affected us several times in the past.
The maintenance will take place between 06:00 and 06:30 CEST (UTC+2) on the 13th of June 2013.
Please note there is a similar maintenance announced for 11th June. If the IP addresses of your servers match the following list, you may experience downtime on either 11th or 13th of June.
This are prefixes configured in that part of the network:
5.79.80.0/22
62.212.72.0/23
62.212.82.0/23
62.212.85.0/24
62.212.88.0/23
82.192.78.0/24
82.192.84.0/23
82.192.90.0/23
82.192.94.0/23
83.149.70.0/23
83.149.124.0/22
85.17.24.0/21
85.17.72.0/23
85.17.90.0/24
85.17.132.0/24
85.17.136.0/24
85.17.147.0/24
85.17.172.0/24
85.17.190.0/23
95.211.88.0/22
95.211.128.0/22
95.211.132.0/23
95.211.136.0/21
95.211.144.0/20
95.211.200.0/21
2001:1af8:4010::/44
2001:1af8:4600::/40
…………
46.243.0.0/22
46.243.4.0/23
146.185.0.0/23
190.105.0.0/24
212.7.204.192/26
212.7.206.128/27
212.7.212.0/23
216.59.55.0/24
216.59.59.0/24
216.59.60.0/24
Startdate: June 11th 2013 06:00:00 (CEST)
Enddate: June 11th 2013 06:30:00 (CEST)
Dear Sir/Madam,
As part of our commitment to continually improve the level of service you receive from LeaseWeb we are undertaking this maintenance.
We are going to upgrade our high volume routers at EvoSwitch dataceter with the new version of Juniper software which is supposed to fix a bug which affected us several times in the past.
The maintenance will take place between 06:00 and 06:30 CEST (UTC+2) on the 11th of June 2013.
Please note there is a similar maintenance announced for 13th June. If the IP addresses of your servers match the following list, you may experience downtime on either 11th or 13th of June.
This are prefixes configured in that part of the network:
5.79.80.0/22
62.212.72.0/23
62.212.82.0/23
62.212.85.0/24
62.212.88.0/23
82.192.78.0/24
82.192.84.0/23
82.192.90.0/23
82.192.94.0/23
83.149.70.0/23
83.149.124.0/22
85.17.24.0/21
85.17.72.0/23
85.17.90.0/24
85.17.132.0/24
85.17.136.0/24
85.17.147.0/24
85.17.172.0/24
85.17.190.0/23
95.211.88.0/22
95.211.128.0/22
95.211.132.0/23
95.211.136.0/21
95.211.144.0/20
95.211.200.0/21
2001:1af8:4010::/44
2001:1af8:4600::/40
…………
46.243.0.0/22
46.243.4.0/23
146.185.0.0/23
190.105.0.0/24
212.7.204.192/26
212.7.206.128/27
212.7.212.0/23
216.59.55.0/24
216.59.59.0/24
216.59.60.0/24
Time: July 16th 2012 14:31:00
Dear Customers,
We are having some high volume router issues in our Haarlem Data Center on the following ranges:
62.212.72.0/23
62.212.82.0/24
62.212.85.0/24
62.212.88.0/23
82.192.94.0/23
82.192.84.0/23
83.149.70.0/23
85.17.24.0/21
83.149.124.0/22
95.211.136.0/21
95.211.144.0/20
We will update this page when more information is available.
[Update 14:41]
The initial cause of the problem was the routing process on the active routing engine.
The process became unresponsive and got killed by the Juniper operating system.
A newly spawned routing process also encountered issues.
We then decided to do a routing engine switchover.
This initially seemed to resolve the issue, but we are finding there are still routing issues.
[Update 14:49]
We are unable to fix the routing process issues on the second routing engine.
The primary routing engine will now be rebooted, once that is back online we will issue another switchover of active routing engine.
[Update 15:04]
We were unable to restore operations on either of the routing engine.
We have decided to initiate a hard reboot of all hardware in the chassis.
[Update 15:12]
Apparently the hard reboot fixed some issues, however the initial issue is still not solved. We are therefore still continue troubleshooting.
[Update 15:31]
Traffic is rebuilding and seems to be restoring. We are investigating the situation and will update this page as soon as there is more information.
[Update 15:42]
Traffic is almost at the same level as before the outage.
If you are still experiencing connectivity issues please open a ticket with support, and clearly mention that you are still experiencing issues.
Time: July 16th 2012 14:31:00
Dear Customers,
We are having some high volume router issues in our Haarlem Data Center on the following ranges:
62.212.72.0/23
62.212.82.0/24
62.212.85.0/24
62.212.88.0/23
82.192.94.0/23
82.192.84.0/23
83.149.70.0/23
85.17.24.0/21
83.149.124.0/22
95.211.136.0/21
95.211.144.0/20
We will update this page when more information is available.
[Update 14:41]
The initial cause of the problem was the routing process on the active routing engine.
The process became unresponsive and got killed by the Juniper operating system.
A newly spawned routing process also encountered issues.
We then decided to do a routing engine switchover.
This initially seemed to resolve the issue, but we are finding there are still routing issues.
An update will follow soon.
[Update 14:49]
We are unable to fix the routing process issues on the second routing engine.
The primary routing engine will now be rebooted, once that is back online we will issue another switchover of active routing engine.
[Update 15:04]
We were unable to restore operations on either of the routing engine.
We have decided to initiate a hard reboot of all hardware in the chassis.