Gateway Check Issues.

[#1]

@Mandeep37  plusnet chat staff have been putting people on a static IP, a static IP will bypass the colindale gateway and your connection should improve... give that a try, and you could also reset your router (pin in the little reset button for some seconds)

it's not an ideal situation at all, i'm wanting to be put on a static IP myself because i'm still connecting through the colindale gateway and my downstream has taken quite a hit (went from 37 to 31)

[#2]

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) 5.379 ms

Last time that I checked my gateway - about 10 days ago - the tool reported Colindale point of access rather than giving an error message; I imagine that I am still on the new network.

[#3]

A bit more information on my post above reporting a gateway not being found.

That check was from address 51.6.199.xxx and - as the message shows - failed to identify the gateway. I have since restarted my (Technicolor) router and got address 51.6.195.xxx from which the gateway checker works.

I have the two full addresses, if knowing them would be helpful.

[#4]

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.764 ms

From 146.198.239.xxx on new network

[#5]

Thanks for the reports. The problem with some of the internet (gateway) routers not identifying themselves is known to Plusnet and down for investigation. However the task is low priority since the problem does not affect the router's primary task.

Even within the 146.198.239.* range a connection on a different IP and following a different path can return a successful result, eg

You are currently connected to gateway pcn-ir01.

This is located in Colindale Point of Presence.

[#6]

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.523 ms * be2.psb-ar02.plus.net (195.166.129.183) 4.095 ms

[#7]

Thanks for the report. You are on the new network with access via the Southbank Point of Presence. However your Internet (Gateway) Router is one that currently does not identify itself.

[#8]

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) 6.036 ms
• *
• be2.pcn-ar01.plus.net (195.166.129.165) 4.838 ms

[#9]

Thanks.

I have updated the checker so that the Access Router (pcn-ar01 in your case) should show as your gateway.

[#10]

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) 6.934 ms
• *
• *
• *

Incidentally, I have problems accepting inbound connections that previously worked, and as a result, I'm considering moving to a different supplier. See: https://community.plus.net/t5/Fibre-Broadband/We-don-t-compromise-on-value-or-service-HA-SSH-inbound...

[#11]

Thanks for the report. That hop is followed by an Internet Router which does not identify itself. Plusnet need to investigate this but it is a low priority issue since it does not interfere with the router doing its primary task.

[#12]

I am also getting the same problem

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

[#13]

The error has come back and the NEW checker can no longer identify my gateway.

I was on the Colindale point of presence before.

Which gateway

Custom diagnostic check on IP 51.9.241.45

Array

[1] => 7 core2-hu0-18-0-0.colindale.ukcore.bt.net (62.172.103.16) 5.431 ms

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) 5.431 ms

[#14]

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) 9.612 ms

[#15]

I get this right now:

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.071 ms

My net dropped twice this afternoon that I noticed. And once wouldn't come back til rebooted router. Speed has dropped and SNR margin doubled:

7 - Data rate:	1164/7199
8 - Maximum data rate:	1188/9128
9 - Noise margin:	6.8/11.7

I'm usually 12000 data rate down. Is plusnet moving people around and cutting speeds after recent problems with dropped packets on network. My speed hasn't gone below 11mb/s in a loooong time. I see I'm not only one reporting it.