Plusnet - New Network
Quote from: Webif Dedicated
Quote 1 1 ms 1 ms 2 ms dsldevice.lan [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 4 ms 6 ms 6 ms 172.17.3.205
5 11 ms 6 ms 7 ms 172.17.10.130
6 6 ms 5 ms 8 ms be2.pcn-ir01.plus.net [195.166.129.164]
7 10 ms 7 ms 8 ms core1-BE1.colindale.ukcore.bt.net [195.99.125.132]
8 7 ms 5 ms 8 ms 62.172.103.13
9 5 ms 5 ms 6 ms 194.74.65.42
10 * * * Request timed out.
11 * * * Request timed out.
12 12 ms 14 ms 24 ms ae0.er01.telhc.bbc.co.uk [132.185.254.109]
13 10 ms 53 ms 7 ms 132.185.255.148
14 6 ms 6 ms 5 ms 212.58.244.23
Quote Tracing route to ntp.plus.net [212.159.6.9]
over a maximum of 30 hops:
1 1 ms 2 ms 2 ms dsldevice.lan [192.168.1.254]
2 * * * Request timed out.
3 * * * Request timed out.
4 10 ms 17 ms 8 ms 172.17.3.205
5 6 ms 9 ms 6 ms 172.17.10.130
6 51 ms 6 ms 6 ms be2.pcn-ir01.plus.net [195.166.129.164]
7 6 ms 6 ms 6 ms gr-11-1-0.ptw-cr01.plus.net [195.166.129.185]
8 6 ms 6 ms 9 ms ae2.ptw-cr02.plus.net [195.166.129.5]
9 6 ms 6 ms 6 ms po2.ptw-gw02.plus.net [195.166.129.39]
10 * * * Request timed out.
11 7 ms 6 ms 5 ms cdns01.plus.net [212.159.6.9]
It is Dedicated WBMC.
A very detailed explanation of what is happening has been posted by Kitz on her forums:
[quote=http://forum.kitz.co.uk/index.php/topic,16711]Plusnet have started to move some of their customers over to a new Dedicated WBMC network.
Dedicated WBMC is a logical move for Plusnet to make - As their customer base increased, they have outgrown Shared WBMC and what it was originally designed for. The signs that something was brewing was first spotted on their forums on the 5th of Jan 2016.
What is WBMC?
A full explanation can be found on the main website: WBC/WBMC, but in brief it is one of the ways how your internet ...
See http://forum.kitz.co.uk/index.php/topic,16711 for the full post.
A very detailed explanation of what is happening has been posted by Kitz on her forums:
[quote=http://forum.kitz.co.uk/index.php/topic,16711]Plusnet have started to move some of their customers over to a new Dedicated WBMC network.
Dedicated WBMC is a logical move for Plusnet to make - As their customer base increased, they have outgrown Shared WBMC and what it was originally designed for. The signs that something was brewing was first spotted on their forums on the 5th of Jan 2016.
What is WBMC?
A full explanation can be found on the main website: WBC/WBMC, but in brief it is one of the ways how your internet ...
See http://forum.kitz.co.uk/index.php/topic,16711 for the full post.
The first reply to the post I've linked above is also posted by Kitz and is aimed at Plusnet:
[quote=http://forum.kitz.co.uk/index.php/topic,16711.msg308130.html#msg308130]
Comments aimed at Plusnet
It is a big mystery to me why Plusnet have with-held this information. Plusnet should be telling users what they are doing. We are not all BT/TT users and we will notice changes in our routing. It took me once glance to suspect what they were doing, and then a simple look at a tracert to be pretty damn sure what they had done. Please don't treat us as mushrooms.
This is a positive step that should proudly be announced. It would also stop what I've no doubt will be a lot of forth coming queries from some of your user base. At least officially announce things such as this on your forums beforehand so the techies will know, Joe Bloggs probably wont care.. but not all of us are stupid. There is no reason to hide something that will come out in the wash anyhow.
OK, there may be some teething problems until you gauge bandwidth correctly, but don't you think its better to warn us. That way we will understand and be patient rather than moaning if one of the nodes needs a bit more bandwidth. Talk to us, tell us and you'll be surprised at what a difference it makes when it comes to complaints.
Since last year they have known the problem was with the shared MSILs but refused to publicly state where the issue lay, if Plusnet had been more open at the time, then it would have saved a lot of grief and bad feelings on the forums.
...
[quote=http://forum.kitz.co.uk/index.php/topic,16711.msg308130.html#msg308130]
Comments aimed at Plusnet
It is a big mystery to me why Plusnet have with-held this information. Plusnet should be telling users what they are doing. We are not all BT/TT users and we will notice changes in our routing. It took me once glance to suspect what they were doing, and then a simple look at a tracert to be pretty damn sure what they had done. Please don't treat us as mushrooms.
This is a positive step that should proudly be announced. It would also stop what I've no doubt will be a lot of forth coming queries from some of your user base. At least officially announce things such as this on your forums beforehand so the techies will know, Joe Bloggs probably wont care.. but not all of us are stupid. There is no reason to hide something that will come out in the wash anyhow.
OK, there may be some teething problems until you gauge bandwidth correctly, but don't you think its better to warn us. That way we will understand and be patient rather than moaning if one of the nodes needs a bit more bandwidth. Talk to us, tell us and you'll be surprised at what a difference it makes when it comes to complaints.
Since last year they have known the problem was with the shared MSILs but refused to publicly state where the issue lay, if Plusnet had been more open at the time, then it would have saved a lot of grief and bad feelings on the forums.
...
Bob, I and a number of other people have been reporting slowdowns on mid-week evenings recently - I should hope that these changes ARE to resolve reported problems!
We're not planning on building a network that slows during the evening
The decision to do so (which has been long in the making), is not a direct response to yours or any body else's reported problems though.
The decision to do so (which has been long in the making), is not a direct response to yours or any body else's reported problems though.
Ah, Bob. It is however a direct response to throughput issues that have and increasingly would have caused customers' reported problems.