We had a problem with our telephone switches this night that has caused edpnet Telephony to be unreachable for some time. This was resolved at 1:58AM last night.
However a backend problem still lingered, this should be solved at around 9:30AM today.
SIP Trunk and Cloud PBX users were not affected.
If you still have issues, please reboot your modem.
– The edpnet team
We currently have an outage in the Liege area. We are trying to resolve this issue as soon as possible.
Update 11:06: Our technician has arrived onsite.
Update 11:43: Power issue in the whole Belgacom colocation. Systems should be back online soon.
Update 11:49: Customers are coming back online.
Update 11:59: All systems are up and stable again.
If you still have no connection to the internet, please restart your modem and router first.
We appologize for the inconvience
We are investigating the cause and apologize for the inconvenience.
It was possible that you couldn’t reach some websites.
We apologize for any inconvenience.
Our DNS servers are currently being used in a DNS amplification attack. Our NOC is currently doing its best to block off as much as possible.
You may have issues reaching some websites during this attack. It’s best to retry again when a lookup fails.
We apologize for the inconvenience.
In order to execute the final step in improving our mail servers, we have planned a scheduled maintenance on the 16th of March, at 01:00 CET.
Affected services: E-Mail
Maintenance window: 01:00 – 02:00 CET
Downtime: 1 hour
During the maintenance our mail servers will not be reachable. Your emails will not be lost.
We apologize for any inconvenience.
Betreft: E-mails
Onderhoudstijdstip: 01:00 – 02:00
Duurtijd: 1 uur
Gedurende dit onderhoud zullen onze mailservers niet bereikbaar zijn. Uw e-mails zullen niet verloren gaan.
Wij excuseren ons voor het ongemak.
A fiber cut in London and a planned maintenace in Rotterdam cause internet connectivity issues. We try to resolve these as soon as possible. Sorry for the inconvenience.
Dear customers,
Since 2:30 we are having a problem with Voip and SIP trunks, including our own telephone systems. We are currently not or difficult to reach via telephone.
Our network team is currently trying to resolve this issue as soon as possible.
More news will follow.
Update 18/02/2014 – 10h15
Update 17/02/2014 – 16h47
12 individual spamhaus listings are blocked. 8 are acknowledged by Spamhaus. We are waiting for the last 4 listings remaining. After we surely hope Spamhaus can deblock our entire IP range.
Dear customer,
Spamhaus.org listed our IP ranges, due to 2 customers who seems to be spammers. Meanwhile our NOC team took the necessary steps to block these spammers, but you are unable to send mails to people who use spamhaus.org as a filter to receive e-mail.
As we already communicated in the past, spamhaus.org always take extreme measurments by blocking entire IP ranges, instead of the one specific spamming IP address.
As an ISP we do not do any filtering of traffic and we do allow fixed IP users to have their own mail servers, but we try to pro-actively scan as much traffic as we can for possible abuse. We already redefined our policy regarding traffic filtering to prevent such issues, but it seems now that we need to protect ourselves and our customers even more.
We still believe that over the years we already took quite a lot of measurements to get the internet free from abuse and spam as we closed port 25 for all our dynamic IP users and we implemented a state of the art Cisco Iron Port mail system.
Nevertheless we still do not do any traffic filtering and we don’t want to.
We are in contact with Spamhaus.org in order to delist our IP-ranges as soon as possible.