Time: October 22, 2014 11:25:00 (CEST)
Dear LeaseWeb Customer,

You might have experienced a 5 minutes of interruption of your services between 11:25 and 11:30 due to a linecard reboot affecting one of our routers in the high volume network in AMS1 data center.

The following network prefixes might have been affected:

5.79.80.0/21
46.243.0.0/22
46.243.4.0/23
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.80.0/23
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
146.185.0.0/23
179.43.173.128/25
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

2001:1af8:4010::/44

We are investigating the cause of this issue.

If you need further information, please open a ticket via the LeaseWeb Self Service Center, or contact us at [email protected].

Time: October 15, 2014 21:08:00 (CEST)
Dear LeaseWeb Customer,

Due to a denial of service attack, we experienced connectivity issues in part of our network in AMS-01 between 20:55 and 21:10 CEST. During this time you might have experienced packet loss and/or higher latency.

The following network prefixes might have been affected:

31.186.170.0/24
37.48.96.0/23
46.226.192.0/22
46.182.180.0/23
46.226.196.0/23
62.212.75.128/26
82.192.64.0/23
83.149.102.0/23
85.17.66.0/25
85.17.66.192/26
92.114.86.0/23
93.176.128.0/23
94.177.98.0/23
95.211.72.0/21
95.211.106.0/23
95.211.108.0/22
95.211.112.0/20
95.211.134.0/23
95.211.160.0/23
95.211.176.0/21
95.211.216.0/21
95.211.232.0/21
109.70.12.0/22
185.19.214.0/25
185.22.4.0/24
185.24.174.0/24
185.44.22.0/23
190.105.195.0/24
2001:1AF8:4500::/40
2A02:40C0:2::/48
2A02:4900::/44

The attack has now been mitigated allowing traffic level/connectivity to return to normal.
If you notice any issues, please open a ticket via the LeaseWeb Self Service Center, or contact us directly at [email protected].

Time: October 15, 2014 00:10:00 (CEST)
Dear Leaseweb Customer,

We are experiencing issues in part of our network due to a dark fiber maintenance from our provider which affected the redundancy in AMS-11.
The second router took the load and traffic levels seem normal.

Affected prefixes:
82.150.152.128/26
85.17.0.0/22
85.17.7.0/24
85.17.8.0/24
85.17.10.0/24
85.17.18.0/23
83.149.64.0/18
91.184.46.0/23
91.184.48.0/20
94.177.146.0/24
193.239.6.0/23
195.42.134.0/24
2001:1AF8:3100::/40

If you notice any issues, please open a ticket via the LeaseWeb Self Service Center, or contact us directly at [email protected].

Time: October 7, 2014 21:24:00 (CEST)
Between 21:24 and 21:34 CEST we experienced connectivity issues in part of our network in WDC-01. The issue was caused due to high CPU load in one of our routers which in turn led BGP sessions to become unstable. During this time you might have experienced packet loss or higher latency. The following network prefixes might have been affected:

91.242.214.0/23
108.59.0.0/20
162.210.192.0/21
185.28.70.0/24
192.96.200.0/21
198.7.56.0/21
199.115.112.0/21
199.58.84.0/22
207.244.64.0/18

2604:9A00:2100::/40

Time: September 25, 2014 20:20:00 (CEST)
Dear LeaseWeb Customer,

Currently we experience packet loss and high latency in part of our network in AMS-01 due to an ongoing DDoS attack. At the moment we are working in order to mitigate the attack. We will keep updating this NOC posting.

A small section of following network prefixes may be affected:

5.79.80.0/21
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.80.0/23
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
46.243.0.0/22
46.243.4.0/23
146.185.0.0/23
179.43.173.128/25
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

2001:1AF8:4600::/40
2001:1af8:4010::/44

Time: September 25, 2014 18:30:00 (CEST)
Dear LeaseWeb Customer,

Due to a denial of service attack, we experienced connectivity issues in part of our network in AMS-01 between 18:20 and 18:40 CEST. During this time you might have experienced packet loss and/or higher latency.

The following network prefixes might have been affected:

5.79.80.0/21
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.80.0/23
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
46.243.0.0/22
46.243.4.0/23
146.185.0.0/23
179.43.173.128/25
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

2001:1AF8:4600::/40
2001:1af8:4010::/44

The attack has now been mitigated allowing traffic level/connectivity to return to normal. If you notice any issues, please open a ticket via the LeaseWeb Self Service Center, or contact us directly at [email protected].

Time: September 25, 2014 15:45:00 (CEST)
Dear LeaseWeb Customer,

Today between 15:45 and 15:55 CEST we experienced connectivity issues in part of our network in FRA-10. The issue was caused due to high CPU load in one of our routers which in turn led BGP sessions to become unstable. During this time you might have experienced packet loss or higher latency.

The following network prefixes might have been affected:

37.58.52.0/23
46.165.196.0/22
46.165.200.0/22
5.61.32.0/20
37.1.192.0/21
37.1.216.0/21

2A00:C98:2010::/44

If you notice any issues, please open a ticket via the LeaseWeb Self Service Center, or contact us directly at [email protected].

**Zie ook Security lek bash maakt Linux en Mac OS X kwetsbaar**

Time: September 25, 2014 08:00:00 (CEST)
Dear LeaseWeb customer,

We would like to inform you about a major vulnerability detected in Bash yesterday: Code Injection Vulnerability via Specially Crafted Environment Variables.

An attacker could use this flaw to override or bypass environment restrictions to execute shell commands. Certain services and applications allow remote unauthenticated attackers to provide environment variables, allowing them to exploit this issue.

For more information, visit https://access.redhat.com/security/cve/CVE-2014-6271 or https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack/

This bug affects all Linux versions running ‘bash – GNU Bourne Again SHell’, including:

– Ubuntu 10.04 LTS
– Ubuntu 12.04 LTS
– Ubuntu 14.04 LTS
– CentOS-4
– CentOS-5
– CentOS-6
– Debian 6
– Debian 7

Many distributions like CentOS, Debian and Ubuntu have already pushed updates for Bash. If you are running a supported OS version, you will be able to update Bash by running one of the following commands:

Debian and Ubuntu:
– apt-get update & apt-get upgrade

CentOS:
– yum update

If you need further assistance, please open a ticket via the LeaseWeb Self Service Center, or contact us directly at [email protected].

Time: September 24, 2014 14:08:00 (CEST)
Dear LeaseWeb Customer,

Due to a denial of service attack, we experienced connectivity issues in part of our network in AMS-01 between 13:40 and 13:50 CEST. During this time you might have experienced packet loss and/or higher latency.

The networks affected are:

62.212.78.0/23

The attack has now been mitigated allowing traffic level/connectivity to return to normal. If you notice any issues, please open a ticket via the LeaseWeb Self Service Center, or contact us directly at [email protected].

Time: September 24, 2014 10:12:00 (CEST)
Dear LeaseWeb Customer,

At the moment we experience issues with one of our primary routers in part of our network in AMS-01. Currently the standby router is handling the traffic while we are investigating the root cause of the issue. We will continue updating this page.

The following network prefixes might have been affected:

31.186.170.0/24
37.48.96.0/23
37.61.232.0/24
46.226.192.0/22
62.212.75.128/26
82.192.64.0/23
83.149.102.0/23
95.211.72.0/21
95.211.106.0/23
95.211.108.0/22
95.211.112.0/20
95.211.134.0/23
95.211.160.0/23
95.211.176.0/21
95.211.216.0/21
95.211.232.0/21
82.192.64.0/23
92.114.86.0/23
94.177.98.0/23
109.70.12.0/22
188.95.136.0/23
190.105.195.0/24
212.7.200.0/22
212.7.214.0/24

2001:1AF8:4500::/40
2A01:9400:1::/48
2A02:40C0:2::/48
2A02:4900::/44