Dear customers,
We have planned a maintenance in 03 zone, causing a brief interruption in the traffic flow on some access lines. Please find the details below.
Description:
Start: 2015-03-26 06:00 AM*
End: 2015-03-26 07:00 AM*
Duration: 1 minute
Impacted services: All edpnet services (Internet, telephony, e-mail…) for the areas below.
Affected Areas: 03
We apologize for the inconvenience
The edpnet team
*All times are listed in CET, Central European Time
Dear customers,
We have planned a maintenance in 02 and 03 zone, only a brief interruption in the traffic flow should occur. Please find the details below.
Description:
Start: 2015-03-23 06:00 AM*
End: 2015-03-23 08:00 AM*
Duration: 1 minute
Impacted services: All edpnet services (Internet, telephony, e-mail…) for the areas below.
Affected Areas: 02, 03
We apologize for the inconvenience
The edpnet team
*All times are listed in CET, Central European Time
Dear customers,
Proximus has planned a maintenance in one of its data centers. Please find the details below.
Description:
Start: 2015-03-16 02:00 AM*
End: 2015-03-16 04:00 AM*
Duration: 15 minutes
Impacted services: All edpnet services (Internet, telephony, e-mail…) for the areas below.
Affected Areas: 02
We apologize for the inconvenience
The edpnet team
*All times are listed in CET, Central European Time
Dear customers,
Proximus has planned a maintenance in one of its data centers. Please find the details below.
Description: Maintenance data center Liege
Start: 2015-02-23 02:00 AM*
End: 2015-02-23 04:00 AM*
Duration: 00:15
Impacted services: All edpnet services (Internet, telephony, e-mail…) for the areas below.
Affected Areas: 019, 041, 061, 063, 080, 081, 082, 083, 084, 085, 086, 087
We apologize for the inconvenience
The edpnet team
*All times are listed in CET, Central European Time
Dear customers,
We apologize for the inconveniences.
The edpnet team
*All times are listed in CET, Central European Time
What is Phishing? Phishing emails are fraudulent messages made to look like they were sent by reputable companies in an attempt to gather your personal and financial details.
Example:
From: INFO SERVICE TELENET [mailto:<removed>]
Sent: woensdag 3 december 2014 16:30
Subject: *Chers (es) clients (es) de EDPNET,**Chers (es) clients (es) de EDPNET,*
Le service technique chargé de la maintenance des comptes de messagerie a détecté des accès illégaux à votre messagerie à travers différentes adresses IP. Au risque que votre compte ne soit suspendu dans les prochains jours, notre service de maintenance vous demande de confirmer vos accès de connexion. Au cas où les informations ne seront pas fournies, votre accès à la messagerie serait suspendu définitivement. Pour des raisons de sécurité, veuillez fournir l’intégralité des informations demandées.
Complétez les informations suivantes pour la confirmation à votre accès
* Nom d’utilisateur:………………………………….
* Mot de passe:……………………………………….* Adresse e-mail :……………………………………* Mot de passe :………………………………………
* E-mail secondaire :…………………………………* Mot de passe :……………………………………….* Date de naissance:…………………………………* Pays ou territoire:…………………………………..
* Profession:………………………………………………
* Tel:…………………………………………………………
Dès la réception de ces informations, votre messagerie serait suivie contre les accès illégaux. Merci de votre collaboration.
Webmail EDPNET*
*Cordialement,*
*L’équipe EDPNET*
Description:
Start: 2014-10-21 09:50 AM
End:2014-10-21 09:54 AM
Impacted services: All edpnet services in the mentioned regions.
We apologize for the inconvenience
The edpnet team
due to a power outage we lost connectivity towards our Brussels DSL network.
Description:
Start: 14/10/2014 19:25
End: 14/10/2014 19:37
Impacted services: DSL lines in Brussels region
We appologize for the inconvenience
The edpnet team
Update 12:25
Due to a power outage in our co-location for region of Antwerp, connections for Antwerp, Limburg and parts of Flemish Brabant en East-Flanders were disrupted. These connections came back online when the power was restored.
Our apologies for the inconvenience.
This afternoon the old supplier replaced the broken card. Our new Cisco backup equipment detected this hardware replacement and made a wrong reaction on the backup/reroute. Our NOC team is investigating with Cisco engineers why the new equipment made this ‘wrong’ detection.
Meanwhile to avoid this, our NOC team deactivated manually the old line/former supplier. In this case further interventions/changes on the former suppliers network can not intervene our backup/reroute.
Our apologies for the inconvenience.