in that case use JPM's link, on the form and explain whats happened and they should clear up the urpn data

If there is an error on the address database then your current provider ( Shell ) need to advise Openreach via an ORDI request to align the address information with what is held by the Royal Mail , that should allow other ISP to locate your address correctly and initiate the migration process , however , presumably at some point Shell ( in the past ) managed to navigate around the address an anomaly, and raised an order to get you provided with FTTC , migrating from another ISP , , there is no reason why an alternative ISP cannot also identify the appropriate address and arrange a migration, provided you interact with them in the appropriate way .

Obviously if you feel the address data should be correct , ( and it should be ) it’s Shell that need to arrange this via Openreach with the ORDI request ( Openreach Data Integrity )
FWIW , your phone number , unless provided by BTw is not going to a provide result on the BTw checker and Shell are not BTw

Edited by Iniltous (Thu 21-Mar-24 17:13:59)

The anomaly is new. So no previous provider has had to navigate it.

I will see if Shell can help. I have already been in touch and it's not promising. Are they obliged to help? (After all, it's obvious that my motivation for this is to leave them...)

Strictly speaking the address data is correct . It's the exchange it's (purportedly) attached to which is wrong, Is that still fixable via an ORDI request? (thanks for the term I need to use, by the way!)

(I realised that was a likely explanation for the phone number search failing, I'm OK with that)

This might be causing some confusion, given your two slightly different addresses

If you e-mail [email protected] with your full details we may be able to do something. No promises.
Link to this thread and also give details of why the issue is there (re addresses)... and what the error is?

seb

Hi all, thanks for all these suggestions.
The issue is now fixed.

The link provided by @jpm prompted openreach to get in touch with me directly, and fix it.
My provider (shell) also got involved, but in the end were a day behind openreach.

I had exactly the same problem as you and had no idea why or what to do about it. I even thought it was my supplier (BT) playing silly beggers and somehow blocking me from seeing other providers deals !!!

I found this thread, completed the form and had the issue resolved within a couple of days. So thank you for the original post, thanks to all who contributed to the thread and thanks Openreach for the swift response and resolution.