Gateway Check Issues.

[#1]

Another three disconnects. And broadband speed dropping through the floor:

Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.

Posting the following information as a reply to the Gateway Checker Issues topic in the Community forums will

help us to diagnose the problem.

core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 5.378 ms

7 - Data rate: 999/3680
8 - Maximum data rate: 884/3952
9 - Noise margin: 4.6/9.1

Turned off router for 10 minutes to try get off this damn gateway. Doesn't seem it will let me.

[#2]

As requested: core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 3.495 ms

No problems, just interested.

[#3]

Thanks for the report. That entry should be followed by an Internet Router but unfortunately this does not identify itself. Plusnet are aware of this but fixing the problem is low priority.

Your result implies you are on the new network presently accessing the Internet through the Colindale Point of Presence.

[#4]

I just tried to check my gateway and it asked me to post this:

Which gateway

Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.

Posting the following information as a reply to the Gateway Checker Issues topic in the Community forums will help us to diagnose the problem.

• core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 4.606 ms

From the other posts I take it this is ok and I am on a new network, whatever that means? I also noticed that when I do a speedtest using speedtest.net the IP address shows as BT and not Plusnet.

Thanks for any reply.

[#5]

Yes, this is a known problem but nothing to worry about. There will be an Internet Router (in the Colindale Point of Presence) after that ukcore line which is your gateway but that IR doesn't identify itself.

You will be on the new network. This simply reflects a different path followed by your connection to the internet.

The IP you have will now belong to Plusnet, though previously it will have been assigned to BT, Speedtest.net have yet to update their records.

[#6]

core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 5.222 ms
*
*
*
*

Seeing as their is no obvious 'NEW POST' button on purpose to prevent new users posting their issue, I've had to post a reply to this message so that I can ask... Why is DOTA 2 spiking during games on my connection, when we are meant to be on high speed broadband and I'm using a high-end PC.

[#7]

Trying to get my gateway info to raise an issue regarding the FTTC 40/2 upload issue, but the gateway checker fails, and asked me to post this info here for some reason.

So here is the info, and I await further instructions 🙂

• core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 4.275 ms

[#8]

Thanks for the report. A small number of gateways don't identify themselves when the checker asks, so the checker can only report identification failure.

Plusnet have correcting the gateway identification problem on the "to do" list but unfortunately it's a low priority task. This problem doesn't prevent the gateway from doing its primary task (network routing), Plusnet don't need the information for fault diagnostics.

[#9]

I got the error from the checker and advice to post here - details below:

• core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 5.626 ms

[#10]

Got this message just now after a brief disconnect while I repositioned my modem:- Not a problem, but previously had been connected to a PSB-IR01 in Southbank, 

Sorry, the tool failed to identify your gateway; this does not mean that anything is wrong with your connection.

Posting the following information as a reply to the Gateway Checker Issues topic in the Community forums will help us to diagnose the problem.

• core2-hu0-18-0-0.southbank.ukcore.bt.net (62.172.103.24) 4.854 ms

[#11]

Thanks for the report. Your Internet Router/Gateway is probably still one of the psb-ir01 family but still on the Plusnet "to do" list to make it identify itself.

This doesn't affect its ability to do its primary job of routing traffic.

[#12]

i just did a reboot Power off and

Posting the following information as a reply to the Gateway Checker Issues topic in the Community forums will help us to diagnose the problem.

• core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 6.203 ms
• *
• *
• *

[#13]

My Gateway checker fail is:-

    core4-te0-8-0-1.faraday.ukcore.bt.net (62.6.201.196) 5.918 ms
    core2-hu0-0-0-0.colindale.ukcore.bt.net (195.99.127.67) 8.064 ms

BTW Colindale is less than 5 miles from me...

[#14]

Gateway checker failure 

• 62.172.103.10 (62.172.103.10) 5.818 ms

My WAN IP sits within this AS

route: 51.6.0.0/15
origin: AS6871
descr: PlusNet plc.
mnt-by: MAINT-AS6871
created: 2016-04-11T12:23:56Z
last-modified: 2016-04-11T12:23:56Z
source: RIPE

[#15]

Thanks. Unfortunately your current gateway router doesn't identify itself. Tha's on the list to be fixed but unfortunately it's a low priority task.