Thursday 27th April 2017 00:01 – 07:00
During the above window we will be performing maintenance on our Broadband Platform.
This work is not expected to be customer affecting.
There will be multiple changes to the routing inside the Broadband platform, some customers may see minor packet loss while the network re-converges after each change.
We are currently improving capacity and resiliency of our Broadband network. As a result of this we are making some changes to the LTS pool serving our wholesale customers.
The LTS subnet 78.33.252.0/23 will be split into two parts
Connections will be from multiple addresses in the subnets and additional LTS can be added at any time as the number of connections increases, please make sure that your configuration allows connections from all of the IP addresses on the subnets.
Please make any changes required to your configuration ASAP You will start to see connections from the new LTS in the next 2 weeks.
We will also be retiring all of the LTS in 62.249.255.128/27 over the next few months. We will update you further when you can remove this range from your configuration.
Tuesday 12 April 2016 0:00 ~ 8:00
During the above window we will be making some changes to the DSL network to reduce the packet loss some users have been reporting.
The work may cause some users to disconnect/reconnect
No other impact is expected.
Steve Lalonde says: This work was completed at approx 8:30
Tuesday 18th November 22:00 – Wednesday 19th November 04:00
Entanet Wholesale Broadband Customers.
During the above maintenance window we will be replacing the following routers with new much more powerful devices
All 3 routers have not been accepting new connections for several weeks and it is expected that there will be less than 100 users still connected across these routers at the start of the work. Those users will reconnect to alternative routers during the work.
No disruption to any other broadband users is expected.
Following the LTS upgrades we will also be moving several servers to make room for additional hardware no impact is expected as these are all redundant systems.
Ming-Yu Hsieh says: Wrong date was entered which have been corrected now.
Steve Lalonde says: This work is now complete.
Thursday 30th January 2014 00:00-01:00
During the above window we will be correcting a routing issue that is causing performance degradation on some parts of our DSL platform.
A small number of EWCS end user connections (approximately 0.01% of users) may be forced to reconnect by this work
Steve Lalonde says: This work is now complete
We wish to advise our EWCS partners that they may soon start to see sessions from additional LTS IP addresses. All addresses used will be within the previously announced ranges of:
Radius: 62.249.192.160/27, 78.33.48.32/28
LTS: 62.249.255.128/27, 78.33.252.0/23
The actual addresses that will be in use are
62.249.255.128/30 = WBC
62.249.255.136/30 = WBC
62.249.255.144/30 = WBC
62.249.255.148/30 = WBC
78.33.253.32/30 = WBC (new)
78.33.253.36/30 = WBC (new)
78.33.253.40/30 = WBC (new)
78.33.253.44/30 = WBC (new)
78.33.253.48/30 = WBC (new)
78.33.253.52/30 = WBC (new)
78.33.253.56/30 = WBC (new)
78.33.253.60/30 = WBC (new)
78.33.253.64/30 = WBC (new)
78.33.253.68/30 = WBC (new)
78.33.253.72/30 = WBC
78.33.253.76/30 = WBC
78.33.253.80/30 = WBC
78.33.253.84/30 = WBC
62.249.255.132/30 = IPSC
62.249.255.152/30 = IPSC
62.249.255.140/30 = IPSC
62.249.255.156/30 = IPSC
As these ranges have previously been announced, this notification is for information only as no config changes should be required by our partners. We would ask that you verify your configurations to make sure that traffic is poining to the correct LTS for the technology in use.
We are aware of an network incident affecting WBC connectivity this morning at approximately 10:00. Traffic was rerouted across alternative paths and service was reinstated minutes after.
Our initial investigations have suggested this may be a third party related issue however this is still being validated. Further updates will be provided as and when they become available.
Richard Partridge says: We are aware of a repeat of the same issue experienced earlier this morning. We have identified a line card issue which we are expecting to rectify shortly. We will update again once we have further information.
Richard Partridge says: Services has now been stabilised following the rerouting of connectivity away from the affected line card. We are continuing to work on rectifying the underlying issue. We are aiming to update this every 30 minutes until the problem is fully resolved.
Following further investigation, the subject of this post has been modified to more accurately reflect the nature of this incident.
Richard Partridge says: We believe the line card issue has been rectified, and it is now ready for normal operation once again. However, we are only passing minimal traffic through the card to give us an opportunity to monitor it before returning it to full service.
As per the previous update, customer traffic continues to be routed around this card for the time being.
We will update again in approximately 30 minutes.
Richard Partridge says: The line card has remained stable since our last update. We are continuing to monitor the line card at the moment and customer traffic is still being routed around it.
We will update again in approximately 30 minutes.
Richard Partridge says: Our engineers are still monitoring the line card at the moment, and it has continued to remain stable since the previous update.
We will update again in approximately one hour.
Richard Partridge says: We are gradually increasing the amount of traffic routing through the original path and the service has remained stable as expected.
We will continue to monitor the traffic and we will aim to provide another update at approximately 17:00 today.
Richard Partridge says: The line card has remained stable, however the underlying cause which triggered this incident in the first place warrants further investigation with Cisco. As a result of this, the line card will remain running on a reduced workload and we will continue monitoring it’s status for the time being.
Once the case is fully investigated and concluded an incident report will be published. We expect to be able to provide the next update on Monday 25th March.
Wayne Hawtin says: The service has been monitored closely and remained stable as expected over the weekend. We will continue to reroute traffic until we are satisfied the risk is fully removed.
Richard Partridge says: An incident report has been made available for this issue. It can be found here.
Our suppliers have advised that they are experiencing a sudden drop in connections in the South of the UK, particularly around Kingston upon Thames. They are currently investigating and have advised that service will be resumed as soon as possible. Consequently a number of our users have lost connection and will be unable to reconnect.
We will continue to keep you updated as more information becomes available.
Neil Watson says: BT have now advised that all users should be able to reconnect. We are requesting further information as to the cause of the problem and will advise when we have it.
We have noticed a number of EWCS customers are denying radius and L2TP connections from some of our LTS and radius ranges. This will result in failed authentication attempts and dropped L2TP sessions.
For Clarification the ranges are:
Radius: 62.249.192.160/27, 78.33.48.32/28
LTS: 62.249.255.128/27, 78.33.252.0/23
This work is now complete.