Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
   Glossary   Glossary
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 ... 7 8 [9] 10 11 ... 16

Author Topic: Peak time throughput issues Plusnet's or a BTWholesale fault  (Read 72245 times)

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33881
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #120 on: March 15, 2015, 06:06:55 AM »

Quote
I guess it's donkeys old but still interesting:

The diagram is old, but newer than mine here which was from back in the days when I was bang up to date with things like centrals and what equipment PN had. I lost track some time around 2009 mostly because I wasn't with PN and lost interest in keeping up to date with what they were doing... it was also a bit harder to get info because they were now owned by BT and most of my contacts had moved on. 

Quote
I assume the following from the gateway names:

Yep - they've always used that type of naming convention.

PTW = Plusnet Telehouse West
PTN = Plusnet Telehouse North

I always thought that CL = City/Central London. iirc 'PCL' first started when they took over Metronets pipes circa '06.  I cant recall for certain, but I think it originally may have been Telecity, Central London. Whatever way City Lifeline also fits nicely now.   
Prior to that they also had PTH which originally was Telehouse East, later changed to PTE to match the others.  PTH (PTE) was the terminating colo for their original centrals when they first started selling adsl.

Quote
AG and BNG are presumably two different types of router.

No, the second part (AG/BNG) isnt specific to the make & model of Edge Router.
 
'AG' simply denoted 'Aggregator' which was followed by the number at that particular location.  These were Juniper ERX 1440s (x6) and iirc by about '09 they also had x8 what were at the time shiny new E320's.  Going back even further in history, a couple of Redbacks were the original pth-ag1 & pth-ag2.  To be more exact their full name as advertised by their manufacturers was Redback SMS 10000 Broadband Aggregator.

BNG = Broadband Network Gateway. Unsure exactly what model they are, but yes Juniper MX is the route they headed after ERX became EOL (end of life).
 
From a quick scan of the specs for all the MX models then it would have to be at least an MX960, but it could also be an MX2010/2020. 
Depends on how how much they budget, what model was available at which date, and when they bought them.  PN always used to go for top of the range capacity model when it came to their edge routing.  Makes sense I suppose, they have a lot of customers so the larger models work out more economical in the long term as they can cope with more sessions and multiple endpoints.  No point having to buy 2 of the cheaper models when you can save a bit of money by purchasing just one of the higher spec.

As regards to the ERX/E320's - Just because a product is EOL doesnt mean that the ISP will replace them.  These are very expensive & sturdy bits of kit and have many replacement slot-in parts.  Both the E320s and ERX1440's were top of the range in their time designed to last for years and still have plenty of life in them.  Because they were top of the range kit in their time, then they will still happily cope with multiple endpoints and be supported by JunOS.    I tried to cost up the price of an ERX many years ago and iirc you're easily looking in the region of £500,000.  Not something an ISP is going to replace every few years and why there is a market for powerful second-hand edge routers.  As an indication Zen have only just replaced their Redbacks (PN replaced theirs 8/9yrs ago).


Quote
my extrapolation is BNG = DPI

Procera as you say is into Deep Packet Inspection.  This is a bit of a weird one. Arbor Networks aquired Ellacoya Networks, yet there's quite a lot of same staff at Procera who used to work at Ellacoya. Arbor doesnt seem to be into DPI and Procera quote themselves as being the only company that delivers 'Internet Intelligence'.  Ellacoya used to be the most advanced and intelligent when it came to DPI.

Plusnet have for years (since 2006) used Ellacoyas for DPI on their E/ERX's and since Procera was recently awarded a major contract with BT for DPI then I would imagine that they are simply using Procera on the 2 new BNGs because you cant buy 'Ellacoyas' any more.


Quote
increased latency once load is greater than n

No - The whole idea of using Ellacoyas/Procera, is so that when things do get busy latency does not suffer.

The Ellacoyas are very intelligent, if the network is busy latency should not be affected at all, instead it will start to throttle back on other protocols such as p2p or nttp.  Latency is usually given priority over all other protocols because its essential for gaming and VoIP. HTTP (web browsing) and web based speedtests would also not suffer, as http is usually given priority after latency affecting apps such as VOiP and gaming.  You'd notice it on p2p for sure though.   The intelligence part of DPI is that you cant fool them by changing ports and attempting to make p2p look like http... and why the name Ellacoya is hated by certain communities.   

I'd much rather be on a busy network controlled by Ellacoyas than one without.  When on Be* there was one episode when we were waiting for our exchange backhaul to be upgraded.   Latency goes to pot without proper traffic shaping, http speeds go to pot..  but heck I could still max out nttp by opening 6 threads.

Hmm you have a point there.. it took PN ages to get the ellacoya configs right... I wonder if there could be something in the fact they are now using Procera its another new learning curve..  I dunno. 
hmmm  again..  I think if it was a config issue then again it would be all users on the BNGs and they'd be complaining about something other than latency and http. :hmm:

Quote
the PN xconnects between PTN/PTW/PCL for any site specific transit.

It had actually crossed my mind the other day, but I soon discarded it because far more users would be complaining - ie all those connected at any PCL or at any PTW gateways would get rubbish speedtests at TBB (Linx @ THN), or out to the Internet via 'x' routing.  It would be much easier to spot as it would become more site specific.  You'd start seeing silly things like good TBB speeds but poor speedtest.net results and vice versa depending upon location of the gateway you are connected via and which transit/peer was at that location.

Quote
found this forum post:
 

lol it's no surprise that their naming convention is the same... because I know who that is  ;)

Gawd am I a mine of useless information or what.  :-X
I also just surprised myself that I can remember half this stuff, yet can't recall what I had for tea yesterday.  :lol:
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #121 on: March 16, 2015, 09:37:29 PM »

rizla this may interest you.

Both these graphs are from my FTTC plusnet line, one is my ipv6 ip and the other is ipv4. Date today.





traceroute to google is same as before, but to thinkbroadband.com the last hop has the higher latency as below.

Code: [Select]
root@TomatoAC66:/tmp/home/root# traceroute6 thinkbroadband.com
traceroute to thinkbroadband.com (2a02:68:1::4), 30 hops max, 16 byte packets
 1  2a02:16c8:0:1::15 (2a02:16c8:0:1::15)  284.556 ms  487.026 ms  449.783 ms
 2  2a02:16c8:1:2::17 (2a02:16c8:1:2::17)  32.167 ms  22.587 ms  20.722 ms
 3  2a02:16c8::c (2a02:16c8::c)  16.868 ms  23.390 ms  17.799 ms
 4  2a02:16c8:1:2::6 (2a02:16c8:1:2::6)  16.611 ms  16.208 ms  16.225 ms
 5  40ge1-3.core1.lon2.he.net (2001:7f8:4::1b1b:1)  16.178 ms  28.860 ms  28.231 ms
 6  linx-gw1.thn.ncuk.net (2001:7f8:4::5394:1)  20.170 ms  22.619 ms  22.609 ms
 7  2a02:68:0:9::4 (2a02:68:0:9::4)  23.786 ms  24.590 ms  25.896 ms
 8  2a02:68:0:31::9 (2a02:68:0:31::9)  26.573 ms  48.195 ms  37.812 ms


Code: [Select]
root@TomatoAC66:/tmp/home/root# ping6 2a02:68:0:31::9
PING 2a02:68:0:31::9 (2a02:68:0:31::9): 56 data bytes
64 bytes from 2a02:68:0:31::9: seq=0 ttl=58 time=16.796 ms
64 bytes from 2a02:68:0:31::9: seq=1 ttl=58 time=18.505 ms
64 bytes from 2a02:68:0:31::9: seq=2 ttl=58 time=18.763 ms
64 bytes from 2a02:68:0:31::9: seq=3 ttl=58 time=18.501 ms
64 bytes from 2a02:68:0:31::9: seq=4 ttl=58 time=21.735 ms
64 bytes from 2a02:68:0:31::9: seq=5 ttl=58 time=17.542 ms
64 bytes from 2a02:68:0:31::9: seq=6 ttl=58 time=18.507 ms
64 bytes from 2a02:68:0:31::9: seq=7 ttl=58 time=17.058 ms
64 bytes from 2a02:68:0:31::9: seq=8 ttl=58 time=19.280 ms
64 bytes from 2a02:68:0:31::9: seq=9 ttl=58 time=17.475 ms
64 bytes from 2a02:68:0:31::9: seq=10 ttl=58 time=17.444 ms
64 bytes from 2a02:68:0:31::9: seq=11 ttl=58 time=17.483 ms
64 bytes from 2a02:68:0:31::9: seq=12 ttl=58 time=17.477 ms
64 bytes from 2a02:68:0:31::9: seq=13 ttl=58 time=23.331 ms
64 bytes from 2a02:68:0:31::9: seq=14 ttl=58 time=20.234 ms
64 bytes from 2a02:68:0:31::9: seq=15 ttl=58 time=17.842 ms
64 bytes from 2a02:68:0:31::9: seq=16 ttl=58 time=45.961 ms
64 bytes from 2a02:68:0:31::9: seq=17 ttl=58 time=40.590 ms
64 bytes from 2a02:68:0:31::9: seq=18 ttl=58 time=56.443 ms
64 bytes from 2a02:68:0:31::9: seq=19 ttl=58 time=50.415 ms
64 bytes from 2a02:68:0:31::9: seq=20 ttl=58 time=26.425 ms
64 bytes from 2a02:68:0:31::9: seq=21 ttl=58 time=38.023 ms
64 bytes from 2a02:68:0:31::9: seq=22 ttl=58 time=43.218 ms
64 bytes from 2a02:68:0:31::9: seq=23 ttl=58 time=53.897 ms
64 bytes from 2a02:68:0:31::9: seq=24 ttl=58 time=38.276 ms
64 bytes from 2a02:68:0:31::9: seq=25 ttl=58 time=25.761 ms
64 bytes from 2a02:68:0:31::9: seq=26 ttl=58 time=22.187 ms
64 bytes from 2a02:68:0:31::9: seq=27 ttl=58 time=29.394 ms
64 bytes from 2a02:68:0:31::9: seq=28 ttl=58 time=24.202 ms
64 bytes from 2a02:68:0:31::9: seq=29 ttl=58 time=22.211 ms
64 bytes from 2a02:68:0:31::9: seq=30 ttl=58 time=18.581 ms
64 bytes from 2a02:68:0:31::9: seq=31 ttl=58 time=18.182 ms
64 bytes from 2a02:68:0:31::9: seq=32 ttl=58 time=18.165 ms
64 bytes from 2a02:68:0:31::9: seq=33 ttl=58 time=17.454 ms
64 bytes from 2a02:68:0:31::9: seq=34 ttl=58 time=17.584 ms
64 bytes from 2a02:68:0:31::9: seq=35 ttl=58 time=18.757 ms
64 bytes from 2a02:68:0:31::9: seq=36 ttl=58 time=48.572 ms
64 bytes from 2a02:68:0:31::9: seq=37 ttl=58 time=39.984 ms
64 bytes from 2a02:68:0:31::9: seq=38 ttl=58 time=17.549 ms
64 bytes from 2a02:68:0:31::9: seq=39 ttl=58 time=19.549 ms
64 bytes from 2a02:68:0:31::9: seq=40 ttl=58 time=27.534 ms
64 bytes from 2a02:68:0:31::9: seq=41 ttl=58 time=26.952 ms
64 bytes from 2a02:68:0:31::9: seq=42 ttl=58 time=38.555 ms
64 bytes from 2a02:68:0:31::9: seq=43 ttl=58 time=24.021 ms
64 bytes from 2a02:68:0:31::9: seq=44 ttl=58 time=21.322 ms
64 bytes from 2a02:68:0:31::9: seq=45 ttl=58 time=20.929 ms
64 bytes from 2a02:68:0:31::9: seq=46 ttl=58 time=18.510 ms
64 bytes from 2a02:68:0:31::9: seq=47 ttl=58 time=22.118 ms
64 bytes from 2a02:68:0:31::9: seq=48 ttl=58 time=50.610 ms
64 bytes from 2a02:68:0:31::9: seq=49 ttl=58 time=37.506 ms
64 bytes from 2a02:68:0:31::9: seq=50 ttl=58 time=23.484 ms
64 bytes from 2a02:68:0:31::9: seq=51 ttl=58 time=20.307 ms
64 bytes from 2a02:68:0:31::9: seq=52 ttl=58 time=25.092 ms
64 bytes from 2a02:68:0:31::9: seq=53 ttl=58 time=20.556 ms
64 bytes from 2a02:68:0:31::9: seq=54 ttl=58 time=20.272 ms
64 bytes from 2a02:68:0:31::9: seq=55 ttl=58 time=19.093 ms
64 bytes from 2a02:68:0:31::9: seq=56 ttl=58 time=18.497 ms
64 bytes from 2a02:68:0:31::9: seq=57 ttl=58 time=26.461 ms
64 bytes from 2a02:68:0:31::9: seq=58 ttl=58 time=50.483 ms
64 bytes from 2a02:68:0:31::9: seq=59 ttl=58 time=35.262 ms
64 bytes from 2a02:68:0:31::9: seq=60 ttl=58 time=54.871 ms
64 bytes from 2a02:68:0:31::9: seq=61 ttl=58 time=18.453 ms
64 bytes from 2a02:68:0:31::9: seq=62 ttl=58 time=19.031 ms
64 bytes from 2a02:68:0:31::9: seq=63 ttl=58 time=27.531 ms
64 bytes from 2a02:68:0:31::9: seq=64 ttl=58 time=17.831 ms
64 bytes from 2a02:68:0:31::9: seq=65 ttl=58 time=17.040 ms
64 bytes from 2a02:68:0:31::9: seq=66 ttl=58 time=17.825 ms
64 bytes from 2a02:68:0:31::9: seq=67 ttl=58 time=19.043 ms
64 bytes from 2a02:68:0:31::9: seq=68 ttl=58 time=18.253 ms
64 bytes from 2a02:68:0:31::9: seq=69 ttl=58 time=23.087 ms
64 bytes from 2a02:68:0:31::9: seq=70 ttl=58 time=26.628 ms
64 bytes from 2a02:68:0:31::9: seq=71 ttl=58 time=30.224 ms
64 bytes from 2a02:68:0:31::9: seq=72 ttl=58 time=26.001 ms
64 bytes from 2a02:68:0:31::9: seq=73 ttl=58 time=18.687 ms
64 bytes from 2a02:68:0:31::9: seq=74 ttl=58 time=27.202 ms
64 bytes from 2a02:68:0:31::9: seq=75 ttl=58 time=18.010 ms
64 bytes from 2a02:68:0:31::9: seq=76 ttl=58 time=17.203 ms
64 bytes from 2a02:68:0:31::9: seq=77 ttl=58 time=39.170 ms
64 bytes from 2a02:68:0:31::9: seq=78 ttl=58 time=23.968 ms
64 bytes from 2a02:68:0:31::9: seq=79 ttl=58 time=17.186 ms
64 bytes from 2a02:68:0:31::9: seq=80 ttl=58 time=19.404 ms
64 bytes from 2a02:68:0:31::9: seq=81 ttl=58 time=17.914 ms
64 bytes from 2a02:68:0:31::9: seq=82 ttl=58 time=17.906 ms
64 bytes from 2a02:68:0:31::9: seq=83 ttl=58 time=17.491 ms
64 bytes from 2a02:68:0:31::9: seq=84 ttl=58 time=17.897 ms
64 bytes from 2a02:68:0:31::9: seq=85 ttl=58 time=17.887 ms
64 bytes from 2a02:68:0:31::9: seq=86 ttl=58 time=18.700 ms
64 bytes from 2a02:68:0:31::9: seq=87 ttl=58 time=16.276 ms
64 bytes from 2a02:68:0:31::9: seq=88 ttl=58 time=30.138 ms
64 bytes from 2a02:68:0:31::9: seq=89 ttl=58 time=17.283 ms
64 bytes from 2a02:68:0:31::9: seq=90 ttl=58 time=16.902 ms
64 bytes from 2a02:68:0:31::9: seq=91 ttl=58 time=22.886 ms
64 bytes from 2a02:68:0:31::9: seq=92 ttl=58 time=26.857 ms
64 bytes from 2a02:68:0:31::9: seq=93 ttl=58 time=17.240 ms
64 bytes from 2a02:68:0:31::9: seq=94 ttl=58 time=37.279 ms
64 bytes from 2a02:68:0:31::9: seq=95 ttl=58 time=28.038 ms
64 bytes from 2a02:68:0:31::9: seq=96 ttl=58 time=37.471 ms
64 bytes from 2a02:68:0:31::9: seq=97 ttl=58 time=28.241 ms
64 bytes from 2a02:68:0:31::9: seq=98 ttl=58 time=17.455 ms
64 bytes from 2a02:68:0:31::9: seq=99 ttl=58 time=16.238 ms
64 bytes from 2a02:68:0:31::9: seq=100 ttl=58 time=18.232 ms

--- 2a02:68:0:31::9 ping statistics ---
101 packets transmitted, 101 packets received, 0% packet loss
round-trip min/avg/max = 16.238/25.068/56.443 ms

however the traceroute was just bad timing as I pinged the last 2 hops both have the varying latency.

Code: [Select]
root@TomatoAC66:/tmp/home/root# ping6 2a02:68:0:31::4
PING 2a02:68:0:31::4 (2a02:68:0:31::4): 56 data bytes
64 bytes from 2a02:68:0:31::4: seq=0 ttl=59 time=44.281 ms
64 bytes from 2a02:68:0:31::4: seq=1 ttl=59 time=40.867 ms
64 bytes from 2a02:68:0:31::4: seq=2 ttl=59 time=38.696 ms
64 bytes from 2a02:68:0:31::4: seq=3 ttl=59 time=35.081 ms
64 bytes from 2a02:68:0:31::4: seq=4 ttl=59 time=43.096 ms
64 bytes from 2a02:68:0:31::4: seq=5 ttl=59 time=31.101 ms
64 bytes from 2a02:68:0:31::4: seq=6 ttl=59 time=23.424 ms
64 bytes from 2a02:68:0:31::4: seq=7 ttl=59 time=49.443 ms
64 bytes from 2a02:68:0:31::4: seq=8 ttl=59 time=37.058 ms
64 bytes from 2a02:68:0:31::4: seq=9 ttl=59 time=31.081 ms
64 bytes from 2a02:68:0:31::4: seq=10 ttl=59 time=18.849 ms
64 bytes from 2a02:68:0:31::4: seq=11 ttl=59 time=27.111 ms
64 bytes from 2a02:68:0:31::4: seq=12 ttl=59 time=24.823 ms
64 bytes from 2a02:68:0:31::4: seq=13 ttl=59 time=56.432 ms
64 bytes from 2a02:68:0:31::4: seq=14 ttl=59 time=62.446 ms
64 bytes from 2a02:68:0:31::4: seq=15 ttl=59 time=55.654 ms
64 bytes from 2a02:68:0:31::4: seq=16 ttl=59 time=31.513 ms
64 bytes from 2a02:68:0:31::4: seq=17 ttl=59 time=37.619 ms
64 bytes from 2a02:68:0:31::4: seq=18 ttl=59 time=48.229 ms
64 bytes from 2a02:68:0:31::4: seq=19 ttl=59 time=30.740 ms
64 bytes from 2a02:68:0:31::4: seq=20 ttl=59 time=61.021 ms
64 bytes from 2a02:68:0:31::4: seq=21 ttl=59 time=56.097 ms
64 bytes from 2a02:68:0:31::4: seq=22 ttl=59 time=65.411 ms
64 bytes from 2a02:68:0:31::4: seq=23 ttl=59 time=65.017 ms
64 bytes from 2a02:68:0:31::4: seq=24 ttl=59 time=61.809 ms
64 bytes from 2a02:68:0:31::4: seq=25 ttl=59 time=53.004 ms
64 bytes from 2a02:68:0:31::4: seq=26 ttl=59 time=43.879 ms
64 bytes from 2a02:68:0:31::4: seq=27 ttl=59 time=63.178 ms
64 bytes from 2a02:68:0:31::4: seq=28 ttl=59 time=43.978 ms
64 bytes from 2a02:68:0:31::4: seq=29 ttl=59 time=43.579 ms
64 bytes from 2a02:68:0:31::4: seq=30 ttl=59 time=51.989 ms
64 bytes from 2a02:68:0:31::4: seq=31 ttl=59 time=50.631 ms
64 bytes from 2a02:68:0:31::4: seq=32 ttl=59 time=57.180 ms
64 bytes from 2a02:68:0:31::4: seq=33 ttl=59 time=70.356 ms
64 bytes from 2a02:68:0:31::4: seq=34 ttl=59 time=55.752 ms
64 bytes from 2a02:68:0:31::4: seq=35 ttl=59 time=44.956 ms
64 bytes from 2a02:68:0:31::4: seq=36 ttl=59 time=40.818 ms
64 bytes from 2a02:68:0:31::4: seq=37 ttl=59 time=65.758 ms
64 bytes from 2a02:68:0:31::4: seq=38 ttl=59 time=44.956 ms
64 bytes from 2a02:68:0:31::4: seq=39 ttl=59 time=48.547 ms
64 bytes from 2a02:68:0:31::4: seq=40 ttl=59 time=33.757 ms
64 bytes from 2a02:68:0:31::4: seq=41 ttl=59 time=42.762 ms
64 bytes from 2a02:68:0:31::4: seq=42 ttl=59 time=57.110 ms
64 bytes from 2a02:68:0:31::4: seq=43 ttl=59 time=61.917 ms
64 bytes from 2a02:68:0:31::4: seq=44 ttl=59 time=67.100 ms
64 bytes from 2a02:68:0:31::4: seq=45 ttl=59 time=155.497 ms
64 bytes from 2a02:68:0:31::4: seq=46 ttl=59 time=42.994 ms
64 bytes from 2a02:68:0:31::4: seq=47 ttl=59 time=38.289 ms
64 bytes from 2a02:68:0:31::4: seq=48 ttl=59 time=34.284 ms
64 bytes from 2a02:68:0:31::4: seq=49 ttl=59 time=37.718 ms
64 bytes from 2a02:68:0:31::4: seq=50 ttl=59 time=31.677 ms
64 bytes from 2a02:68:0:31::4: seq=51 ttl=59 time=30.774 ms
64 bytes from 2a02:68:0:31::4: seq=52 ttl=59 time=26.873 ms
64 bytes from 2a02:68:0:31::4: seq=53 ttl=59 time=50.877 ms
64 bytes from 2a02:68:0:31::4: seq=54 ttl=59 time=76.876 ms
64 bytes from 2a02:68:0:31::4: seq=55 ttl=59 time=58.071 ms
64 bytes from 2a02:68:0:31::4: seq=56 ttl=59 time=69.542 ms
64 bytes from 2a02:68:0:31::4: seq=57 ttl=59 time=62.654 ms
64 bytes from 2a02:68:0:31::4: seq=58 ttl=59 time=34.259 ms
64 bytes from 2a02:68:0:31::4: seq=59 ttl=59 time=16.285 ms
64 bytes from 2a02:68:0:31::4: seq=60 ttl=59 time=26.631 ms
64 bytes from 2a02:68:0:31::4: seq=61 ttl=59 time=20.094 ms
64 bytes from 2a02:68:0:31::4: seq=62 ttl=59 time=15.829 ms
64 bytes from 2a02:68:0:31::4: seq=63 ttl=59 time=38.631 ms
64 bytes from 2a02:68:0:31::4: seq=64 ttl=59 time=17.033 ms
64 bytes from 2a02:68:0:31::4: seq=65 ttl=59 time=16.806 ms

--- 2a02:68:0:31::4 ping statistics ---
66 packets transmitted, 66 packets received, 0% packet loss
round-trip min/avg/max = 15.829/45.754/155.497 ms

now pings to google dns

Code: [Select]
root@TomatoAC66:/tmp/home/root# ping6 2001:4860:4860::8888
PING 2001:4860:4860::8888 (2001:4860:4860::8888): 56 data bytes
64 bytes from 2001:4860:4860::8888: seq=0 ttl=55 time=25.855 ms
64 bytes from 2001:4860:4860::8888: seq=1 ttl=55 time=21.788 ms
64 bytes from 2001:4860:4860::8888: seq=2 ttl=55 time=34.174 ms
64 bytes from 2001:4860:4860::8888: seq=3 ttl=55 time=22.926 ms
64 bytes from 2001:4860:4860::8888: seq=4 ttl=55 time=21.800 ms
64 bytes from 2001:4860:4860::8888: seq=5 ttl=55 time=28.988 ms
64 bytes from 2001:4860:4860::8888: seq=6 ttl=55 time=22.202 ms
64 bytes from 2001:4860:4860::8888: seq=7 ttl=55 time=21.770 ms
64 bytes from 2001:4860:4860::8888: seq=8 ttl=55 time=27.778 ms
64 bytes from 2001:4860:4860::8888: seq=9 ttl=55 time=38.740 ms
64 bytes from 2001:4860:4860::8888: seq=10 ttl=55 time=31.605 ms
64 bytes from 2001:4860:4860::8888: seq=11 ttl=55 time=27.152 ms
64 bytes from 2001:4860:4860::8888: seq=12 ttl=55 time=21.961 ms
64 bytes from 2001:4860:4860::8888: seq=13 ttl=55 time=21.971 ms
64 bytes from 2001:4860:4860::8888: seq=14 ttl=55 time=23.164 ms
64 bytes from 2001:4860:4860::8888: seq=15 ttl=55 time=21.927 ms
64 bytes from 2001:4860:4860::8888: seq=16 ttl=55 time=21.532 ms
64 bytes from 2001:4860:4860::8888: seq=17 ttl=55 time=36.936 ms
64 bytes from 2001:4860:4860::8888: seq=18 ttl=55 time=21.730 ms
64 bytes from 2001:4860:4860::8888: seq=19 ttl=55 time=29.310 ms
64 bytes from 2001:4860:4860::8888: seq=20 ttl=55 time=21.167 ms
64 bytes from 2001:4860:4860::8888: seq=21 ttl=55 time=22.928 ms
64 bytes from 2001:4860:4860::8888: seq=22 ttl=55 time=22.096 ms
64 bytes from 2001:4860:4860::8888: seq=23 ttl=55 time=21.309 ms
64 bytes from 2001:4860:4860::8888: seq=24 ttl=55 time=22.125 ms
64 bytes from 2001:4860:4860::8888: seq=25 ttl=55 time=22.266 ms
64 bytes from 2001:4860:4860::8888: seq=26 ttl=55 time=21.956 ms
64 bytes from 2001:4860:4860::8888: seq=27 ttl=55 time=34.273 ms
64 bytes from 2001:4860:4860::8888: seq=28 ttl=55 time=21.896 ms
64 bytes from 2001:4860:4860::8888: seq=29 ttl=55 time=22.279 ms
64 bytes from 2001:4860:4860::8888: seq=30 ttl=55 time=22.930 ms
64 bytes from 2001:4860:4860::8888: seq=31 ttl=55 time=21.833 ms
64 bytes from 2001:4860:4860::8888: seq=32 ttl=55 time=22.077 ms
64 bytes from 2001:4860:4860::8888: seq=33 ttl=55 time=26.448 ms
64 bytes from 2001:4860:4860::8888: seq=34 ttl=55 time=22.863 ms
64 bytes from 2001:4860:4860::8888: seq=35 ttl=55 time=22.022 ms
64 bytes from 2001:4860:4860::8888: seq=36 ttl=55 time=21.671 ms
64 bytes from 2001:4860:4860::8888: seq=37 ttl=55 time=25.261 ms
64 bytes from 2001:4860:4860::8888: seq=38 ttl=55 time=22.061 ms
64 bytes from 2001:4860:4860::8888: seq=39 ttl=55 time=22.458 ms
64 bytes from 2001:4860:4860::8888: seq=40 ttl=55 time=22.113 ms
64 bytes from 2001:4860:4860::8888: seq=41 ttl=55 time=23.830 ms
64 bytes from 2001:4860:4860::8888: seq=42 ttl=55 time=21.825 ms
64 bytes from 2001:4860:4860::8888: seq=43 ttl=55 time=22.208 ms
64 bytes from 2001:4860:4860::8888: seq=44 ttl=55 time=21.809 ms
64 bytes from 2001:4860:4860::8888: seq=45 ttl=55 time=28.628 ms
64 bytes from 2001:4860:4860::8888: seq=46 ttl=55 time=21.835 ms
64 bytes from 2001:4860:4860::8888: seq=47 ttl=55 time=21.805 ms
64 bytes from 2001:4860:4860::8888: seq=48 ttl=55 time=22.000 ms
64 bytes from 2001:4860:4860::8888: seq=49 ttl=55 time=22.786 ms
64 bytes from 2001:4860:4860::8888: seq=50 ttl=55 time=22.034 ms
64 bytes from 2001:4860:4860::8888: seq=51 ttl=55 time=22.965 ms
64 bytes from 2001:4860:4860::8888: seq=52 ttl=55 time=22.006 ms
64 bytes from 2001:4860:4860::8888: seq=53 ttl=55 time=35.206 ms
64 bytes from 2001:4860:4860::8888: seq=54 ttl=55 time=21.973 ms
64 bytes from 2001:4860:4860::8888: seq=55 ttl=55 time=21.148 ms
64 bytes from 2001:4860:4860::8888: seq=56 ttl=55 time=22.191 ms
64 bytes from 2001:4860:4860::8888: seq=57 ttl=55 time=22.023 ms
64 bytes from 2001:4860:4860::8888: seq=58 ttl=55 time=22.021 ms
64 bytes from 2001:4860:4860::8888: seq=59 ttl=55 time=23.589 ms
64 bytes from 2001:4860:4860::8888: seq=60 ttl=55 time=24.392 ms
64 bytes from 2001:4860:4860::8888: seq=61 ttl=55 time=21.832 ms
64 bytes from 2001:4860:4860::8888: seq=62 ttl=55 time=21.985 ms
64 bytes from 2001:4860:4860::8888: seq=63 ttl=55 time=21.593 ms
64 bytes from 2001:4860:4860::8888: seq=64 ttl=55 time=22.195 ms
64 bytes from 2001:4860:4860::8888: seq=65 ttl=55 time=22.169 ms
64 bytes from 2001:4860:4860::8888: seq=66 ttl=55 time=22.138 ms
64 bytes from 2001:4860:4860::8888: seq=67 ttl=55 time=21.748 ms
64 bytes from 2001:4860:4860::8888: seq=68 ttl=55 time=21.781 ms
64 bytes from 2001:4860:4860::8888: seq=69 ttl=55 time=22.138 ms
64 bytes from 2001:4860:4860::8888: seq=70 ttl=55 time=22.165 ms
64 bytes from 2001:4860:4860::8888: seq=71 ttl=55 time=22.036 ms
64 bytes from 2001:4860:4860::8888: seq=72 ttl=55 time=21.569 ms
64 bytes from 2001:4860:4860::8888: seq=73 ttl=55 time=22.214 ms
64 bytes from 2001:4860:4860::8888: seq=74 ttl=55 time=21.921 ms
64 bytes from 2001:4860:4860::8888: seq=75 ttl=55 time=21.518 ms
64 bytes from 2001:4860:4860::8888: seq=76 ttl=55 time=22.333 ms
64 bytes from 2001:4860:4860::8888: seq=77 ttl=55 time=26.738 ms
64 bytes from 2001:4860:4860::8888: seq=78 ttl=55 time=21.926 ms
64 bytes from 2001:4860:4860::8888: seq=79 ttl=55 time=21.883 ms
64 bytes from 2001:4860:4860::8888: seq=80 ttl=55 time=22.126 ms
64 bytes from 2001:4860:4860::8888: seq=81 ttl=55 time=28.071 ms
64 bytes from 2001:4860:4860::8888: seq=82 ttl=55 time=22.478 ms
64 bytes from 2001:4860:4860::8888: seq=83 ttl=55 time=22.091 ms
64 bytes from 2001:4860:4860::8888: seq=84 ttl=55 time=34.082 ms
64 bytes from 2001:4860:4860::8888: seq=85 ttl=55 time=22.508 ms
64 bytes from 2001:4860:4860::8888: seq=86 ttl=55 time=22.087 ms
64 bytes from 2001:4860:4860::8888: seq=87 ttl=55 time=27.856 ms
64 bytes from 2001:4860:4860::8888: seq=88 ttl=55 time=22.264 ms
64 bytes from 2001:4860:4860::8888: seq=89 ttl=55 time=22.291 ms
64 bytes from 2001:4860:4860::8888: seq=90 ttl=55 time=22.664 ms
64 bytes from 2001:4860:4860::8888: seq=91 ttl=55 time=22.661 ms
64 bytes from 2001:4860:4860::8888: seq=92 ttl=55 time=27.276 ms
64 bytes from 2001:4860:4860::8888: seq=93 ttl=55 time=22.239 ms
64 bytes from 2001:4860:4860::8888: seq=94 ttl=55 time=23.429 ms
64 bytes from 2001:4860:4860::8888: seq=95 ttl=55 time=22.212 ms
64 bytes from 2001:4860:4860::8888: seq=96 ttl=55 time=22.836 ms
64 bytes from 2001:4860:4860::8888: seq=97 ttl=55 time=21.504 ms
64 bytes from 2001:4860:4860::8888: seq=98 ttl=55 time=22.240 ms
64 bytes from 2001:4860:4860::8888: seq=99 ttl=55 time=26.050 ms
64 bytes from 2001:4860:4860::8888: seq=100 ttl=55 time=22.044 ms
64 bytes from 2001:4860:4860::8888: seq=101 ttl=55 time=24.020 ms
64 bytes from 2001:4860:4860::8888: seq=102 ttl=55 time=23.046 ms

--- 2001:4860:4860::8888 ping statistics ---
103 packets transmitted, 103 packets received, 0% packet loss
round-trip min/avg/max = 21.148/23.724/38.740 ms
« Last Edit: March 16, 2015, 09:46:08 PM by Chrysalis »
Logged

loonylion

  • Reg Member
  • ***
  • Posts: 723
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #122 on: March 16, 2015, 09:45:51 PM »

maybe it's time for Plusnet to offer Kitz a brown envelope and keys to the equipment cabinets :P
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #123 on: March 16, 2015, 11:24:11 PM »

According to tech support from an isp other than mine  there are these 3 21CN-BRAS-RED4-MR-DH, 21CN-BRAS-RED2-PR
and 21CN-ACC-ALN1-SP 2 are ok and one has had a slight issue with latency at peak times
The svlan report shows that some regrades are due, but basically that's all they can tell me without knowing which IPSV  im connected to , what does IPSV stand for and what is it?  I tonight after finding the IP address for one of the 3 bras the one that was suspect  have monitored it from an external source, and there doesn't appear to be any real changes in base latency or any jitter going on,
Where as tonight my latency  reached 90ms at one point  which to me shouts serious issues that so far have been ignored basically
« Last Edit: March 16, 2015, 11:27:01 PM by tommy45 »
Logged

boost

  • Reg Member
  • ***
  • Posts: 768
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #124 on: March 17, 2015, 08:39:52 AM »

Which gws are you on chrys?
Logged

boost

  • Reg Member
  • ***
  • Posts: 768
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #125 on: March 17, 2015, 08:42:39 AM »

what does IPSV stand for

This is almost certainly another made up word that bears no resemblance to networking as anyone knows it.
Logged

les-70

  • Kitizen
  • ****
  • Posts: 1254
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #126 on: March 17, 2015, 10:05:34 AM »

  Not being on Plusnet I have not been following this closely but in the last month I have noted TalkTalk Business FTTC (Which may be just the same or TT home or not?) show a bit more sign of evening congestion with TBB pings showing up 3-10ms of blue and up to 10-30ms of yellow.   There has always been some signs of this but it has increased this year.  Along with the ping, TBB speed test has shown single thread variations but normal speed with multi-thread.  I don't notice any impact other than in these tests so it not a worry to me. 

  I have tended to wonder whether with, ever increasing use of on demand TV and films, things are simply getting stretched towards their limits in parts of the networks?  In some case it is also not clear to me how to tell how much of the issue lies outside your ISP's part of the network?

  That said some peoples Plusnet issues do look quite bad.
Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33881
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #127 on: March 17, 2015, 10:10:48 AM »

what does IPSV stand for

IPSVs are BT's VLANs for copper products. More specifically what used to be the IPStream VLANs
SFBBs are BT's FTTC VLANs - presumably Superfast BroadBand?

You will be on an SFBB SVLAN.... as the IPSVs are just for adsl1/adsl2+ VP backhauls.

Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33881
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #128 on: March 17, 2015, 10:22:43 AM »

Quote
That said some peoples Plusnet issues do look quite bad.

It's a weird one.   I havent read the whole PN thread, but it appears that there's about a dozen people affected?   Some people are saying 'me too' but I dont think they are seeing the same issue and its something else different.    There is something though because I've seen it myself,  but I dont see it now.

Saying that there was something last night, but I wasnt here to be able to do any speedtests to see if and how it affected my connection.



I'd love to know what those 2 hr blips are as well.

Previously Ive been like this for weeks.





Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 43467
  • Penguins CAN fly
    • DSLstats
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #129 on: March 17, 2015, 10:56:22 AM »

This morning my internet access was so sluggish it was almost unusable. I dropped the PPP connection and let it reconnect, and immediately pages were snapping into place again. This was about 07:15, so definitely not a peak time, but it does seem to be related to the routing of the connection.
Logged
  Eric

boost

  • Reg Member
  • ***
  • Posts: 768
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #130 on: March 17, 2015, 11:40:36 AM »

What gw you on? :)
PN DNS?
Logged

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 43467
  • Penguins CAN fly
    • DSLstats
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #131 on: March 17, 2015, 11:54:46 AM »

I don't use the PN DNS servers.

Gateway is currently
lo0.11.Central11.ptw-bng02.plus.net (195.166.130.204)
« Last Edit: March 17, 2015, 12:02:14 PM by roseway »
Logged
  Eric

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #132 on: March 17, 2015, 12:02:32 PM »

I don't use the PN DNS servers.
I'm not actually sure how to find out what gateway I'm on.


Here you go:-

http://usertools.plus.net/@gateway


This is mine:-

Which gateway

You are currently connected to gateway ptn-bng02.

This is located in Telehouse North.
Logged

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 43467
  • Penguins CAN fly
    • DSLstats
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #133 on: March 17, 2015, 12:43:45 PM »

Thanks BE1. As it happens, I realised I could get it from a traceroute, and I edited my message.
Logged
  Eric

tommy45

  • Reg Member
  • ***
  • Posts: 627
Re: Peak time throughput issues Plusnet's or a BTWholesale fault
« Reply #134 on: March 17, 2015, 01:28:21 PM »

Quote
That said some peoples Plusnet issues do look quite bad.

It's a weird one.   I havent read the whole PN thread, but it appears that there's about a dozen people affected?   Some people are saying 'me too' but I dont think they are seeing the same issue and its something else different.    There is something though because I've seen it myself,  but I dont see it now.

Saying that there was something last night, but I wasnt here to be able to do any speedtests to see if and how it affected my connection.



I'd love to know what those 2 hr blips are as well.

Previously Ive been like this for weeks.


there may well be a lot more people affected by this, as not everyone will post on internet forums about it, or even be aware that what they are experiencing isn't normal
Logged
Pages: 1 ... 7 8 [9] 10 11 ... 16