topic Re: Peak time latency spikes - TAP3 Test failure in Community Announcements

Re: Peak time latency spikes - TAP3 Test failure

AndyH — Thu, 14 Mar 2013 11:40:33 GMT

There seems to be no consistency of those affected in terms of product (ADSL/FTTC/FTTP/20CN/21CN) and geographic location.
Is the TAP3 test using the BT test login (still not working btw ) the only way of knowing if the problem is in the BT or PN network?
[Moderator's note by Jim (Oldjim) Title changed after split ]

Re: Peak time latency spikes

Anotherone — Thu, 14 Mar 2013 11:46:50 GMT

[cynic hat]That's probably why it's broken[/cynic hat]

Re: Peak time latency spikes

Finguz — Thu, 14 Mar 2013 11:57:59 GMT

Quote from: AndyH
Is the TAP3 test using the BT test login (still not working btw ) the only way of knowing if the problem is in the BT or PN network?

Not as far as I know know. I could only get it to run by using by Pnet username and password in the router ( so connected to my standard account ).
Of course doing this returns an error at the end of the test.
Using the speedtest@speed e.t.c login either times out, or returns a DNS error. I tried multiple DNS configurations, both in the router and in winblows, all to no avail
Edit: Sorry, misread your post /facepalm

Re: Peak time latency spikes

Pettitto — Thu, 14 Mar 2013 12:04:36 GMT

I'm currently investigating the TAP 3 Test problem.
Would it be possible for you to provide a screenshot of the Tap 3 Test not working/failing?

Re: Peak time latency spikes

AndyH — Thu, 14 Mar 2013 12:23:05 GMT

@ Chris
See the attached

Re: Peak time latency spikes

Pettitto — Thu, 14 Mar 2013 12:29:41 GMT

If I need to report this issue, I need evidence to support it.
I appreciate that other providers may be having similar problems, however, from a Plusnet perspective, we need to provide our own information and supporting documentation.
There is some information that I've got on our end, I was just wanting to get a few screen grabs so I can send them as well.
Thanks AndyH

Re: Peak time latency spikes

Pettitto — Thu, 14 Mar 2013 12:31:23 GMT

@Finguz
I would like to hope that no customers would ever need to use any TAP Test.
Not an ideal world though 😕

Re: Peak time latency spikes

Bright — Thu, 14 Mar 2013 12:35:04 GMT

Quote from: Chris
If I need to report this issue, I need evidence to support it.

AndyH's screenshots are exactly what I was getting. Are you happy with one set of screen grabs? Don't really want to disconnect from a gateway that has been reliable for the past week...

Re: Peak time latency spikes

Pettitto — Thu, 14 Mar 2013 12:36:33 GMT

@Bright
They will be fine thanks. I don't want you to hop gateways!

Re: Peak time latency spikes

Oldjim — Thu, 14 Mar 2013 12:58:28 GMT

TAP3 Test split off
If any are in the wrong place please PM me

Re: Peak time latency spikes

Oldjim — Thu, 14 Mar 2013 13:18:20 GMT

TAP3 part merged back in again as it appears to require a bit more thought judging by the number of reported posts and PM's received
Will have a closer look once I have got back in from planting out my parsnips

Re: Peak time latency spikes

Finguz — Thu, 14 Mar 2013 13:23:13 GMT

Can anybody confirm what I should be using as a password with the speedtest@speedtest_domain login?
Someone suggested 'testing' but I can't find any information anywhere to back this up.

Re: Peak time latency spikes

Anotherone — Thu, 14 Mar 2013 13:23:52 GMT

Jim, you'd better move that and this post as well, otherwise you'll be accused of having dirt on your hands

Re: Peak time latency spikes

Anotherone — Thu, 14 Mar 2013 13:25:09 GMT

Finguz, Chris Purvey said it was testing.

Re: Peak time latency spikes

Finguz — Thu, 14 Mar 2013 13:31:21 GMT

Thanks Anotherone!

Re: Peak time latency spikes - TAP3 Test failure

Oldjim — Thu, 14 Mar 2013 14:02:23 GMT

I think I have got it almost right this time despite losing broadband twice while doing it
But I am sure you will tell me otherwise

Re: Peak time latency spikes - TAP3 Test failure

AndyH — Thu, 14 Mar 2013 14:12:41 GMT

Here's the original details (for reference):

Quote from: chrispurvey
Hi,
If anybody experiences any performance issues, would it be possible for you to perform a Tap3 test?
To run the TAP3 test you will need to change the Username and Password you are connecting to in the router. The details are as below:
USERNAME: speedtest@speedtest_domain
PASSWORD: testing
Once successfully logged in, you can then access the Speed Tester server by typing http://217.32.105.42 in your browser.
Once you have completed the speed test you will then need to change the details in your router back to your standard Plusnet Username and Password.
If you could post your results it would be appreciated.

Re: Peak time latency spikes - TAP3 Test failure

Pettitto — Thu, 14 Mar 2013 14:24:56 GMT

Thanks for the merge.
I've got some screenshots to take to our suppliers now. I'll update this thread if I need anything further.
Thanks for your input already

Re: Re: Peak time latency spikes - TAP3 Test failure

Anotherone — Thu, 14 Mar 2013 15:00:13 GMT

FYI (for me) it seems that the only IP addresses that now go direct to the new tester at speedtest.btwholesale.com are 217.32.105.42 & 217.35.209.142
Those IP addresses used to go to the old tester.
The last time I ran it (several days ago perhaps) the old tester address (url) went straight to the new btwholesale tester, that and the other IP addresses that have appeared at various times 193.113.4.153 & 193.113.4.154 & 193.113.8.194 also went direct
Today (for me on pcl-ag06) all these latter ones are going to a 10 second redirect to the btwholesale tester. So whether it's Gateway or routing dependant, I don't know.

Re: Peak time latency spikes

spraxyt — Thu, 14 Mar 2013 15:45:22 GMT

Quote from: Finguz
Can anybody confirm what I should be using as a password with the speedtest@speedtest_domain login?

My understanding is that the tester does not require a password, but some routers will not allow the password field to be left empty. The solution is to enter any letters you like, eg test, testing, .... The tester accepts whatever you enter so it doesn't matter. However I'd avoid numerical values like 0, 1,… since somewhere along the line those might get interpreted as something different (boolean false or true for the technically minded).