Can't reach NS&I login page

[#1]

I still think there may be something wrong the other end.

https://kinsta.com/tools/redirect-checker/

HTTP Status and Redirect Checker
Check the HTTP status of any URL instantly with our free HTTP status & redirect checker. Review all response headers, client errors, and redirects.

https://secure.nsandi.com CHECK

"There was an error processing your website"

https://www.isitdownrightnow.com

Website Name: Nsandi
URL Checked: www.nsandi.com/login
Response Time: 162.24 ms.
Last Down: More than a week ago

UP
Nsandi.com is UP and reachable by us.
Please check and report on local outages below ...

Website Name: SecureURL Checked: secure.nsandi.com
Response Time: no response
Last Down: unknown

DOWN
Secure.nsandi.com is DOWN for everyone.
It is not just you. The server is not responding...

[#2]

But why is there no problem using EE4G network?

[#3]

...Different IP address range? Same reason people can get in via a VPN.

[#4]

https://kinsta.com/tools/redirect-checker/

http://www.nsandi.com/login CHECK

secure.nsandi.com/thc/policyenforcer/pages/loginB2C.jsf?chainingAction=true&MENU=true&forceLogin=true&q=a38962b3-9357-4d4e-a00b-7f82521cb808&p=30c9a2c9-969d-46bd-8992-929cd29c31d2&ts=1721083957&c=nsandi&e=nsisecure23&rt=Safetynet&h=2af8ec7195a5313c6f0ed5080e9df37f

Redirect overview

URL
http://www.nsandi.com/login
STATUS MESSAGE Moved Permanently

Response headers
....
"Expires Sun, 19 Nov 1978 05:00:00 GMT"

URL
https://queuing.nsandi.com?c=nsandi&e=nsisecure&t=https%3A//secure.nsandi.com/thc/policyen...
STATUS MESSAGE Found

URL
https://secure.nsandi.com/thc/policyenforcer/pages/loginB2C.jsf?chainingAction=true&MENU=true&#...
STATUS MESSAGE OK

[#5]

So, are you saying that NS&I are only accepting access requests to their secure login page from selected IP ranges and PN are using a different IP range?  Sorry if I'm being naïve/stupid etc.

If the above is what you're saying could be the problem, who's in the right and wrong here?  Is this some kind of Mexican stand off with PN customers in the firing line?

[#6]

Sorry @marktewk, MTR is is the Linux equivalent of Microsoft's tracert - i.e. the route over the myriad servers it takes.

[#7]

@pvmb the login seems to be redirecting through a queueing site.

[#8]

@jab1 

as far as I can make out secure.nsand.com does not respond to ping, so in this case mtr (my trace route) will not be of any use for anyone for tracing a route.

[#9]

Fair enough @Dan_the_Van - but my mtr in post #77 goes so far, and the hits something which is clearly not a valid server address?

[#10]

@jab1 

Which one is invalid?

1. fritz.box                         0.0%     5    1.4   2.3   1.4   3.8   1.0
 2. lo0-0.bng4.wh-man.zen.net.uk      0.0%     5    9.2   8.9   7.5  10.4   1.3
 3. lag-8.p2.wh-man.zen.net.uk        0.0%     5    7.6   7.3   6.5   7.7   0.6
 4. 195.66.244.191                    0.0%     5    9.1   8.0   7.7   9.1   0.6
 5. 94.31.33.78.IPYX-124905-ZYO.zip.  0.0%     5   27.8  13.1   8.9  27.8   8.2
 6. (waiting for reply)

A Trace route  using Vodafone

C:\>tracert secure.nsandi.com

Tracing route to secure.nsandi.com [157.203.60.156]
over a maximum of 30 hops:

  1     5 ms     6 ms     7 ms  192.168.105.41
  2     *        *        *     Request timed out.
  3   121 ms    41 ms    43 ms  192.168.174.2
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6    80 ms    51 ms    53 ms  172.21.251.233
  7   148 ms     *      458 ms  63.130.172.45
  8   256 ms    42 ms   129 ms  ae13-100-xcr1.ltw.cw.net [195.2.23.77]
  9    83 ms    63 ms    67 ms  zayo-6461.ltw.cw.net [195.2.12.90]
 10     *        *        *     Request timed out.
 11   250 ms    53 ms   184 ms  ae6.mpr1.man1.uk.zip.zayo.com [64.125.23.131]
 12    57 ms    58 ms    53 ms  94.31.33.78.IPYX-124905-ZYO.zip.zayo.com [94.31.33.78]
 13     *        *        *     Request timed out.

Compare hop 5 and hop 12 in the two results

Edit: it fails to complete as the next devices do not respond to ICMP

[#11]

Valid point, @Dan_the_Van  - but we both get bocked on the mtr at that point, although the tracert nearly completes. Just that the '.zip' extension there looked very strange to me. However, this is my last post on this topic, although I do think the issue is somwhere close  to the NS&I site.

[#12]

I think we've established there is a problem and there's no work around for the the users so what can we do ?

NS&I have respnded with a quote from their book of standard replies and Plusnet comments are noticeably absent .

[#13]

This thread is now very long with many opinion's of it's cause

From what I see there are two issues

1) https://secure.nsandi.com no longer works for ANY internet user;  the correct link now is https://www.nsandi.com/Login

2) A number of plusnet users dependant on network range can not login to their NS&I using https://www.nsandi.com/Login

To bypass this plusnet network issue would be to use a VPN or a mobile data hotspot.

This thread was started Wednesday 10th with no resolution which is very poor who ever is responsible for the fix

[#14]

I've escalated this thread to try and get better traction

[#15]

@Dan_the_Van 

"as far as I can make out secure.nsand.com does not respond to ping, so in this case mtr (my trace route) will not be of any use for anyone for tracing a route."

Yes, correct and people using ping, mtr, traceroute to secure.nsandi.com won't get conclusive results.

However proshipping.royalmail.com is on the same network as secure.nsandi.com and DOES respond to ping so can be used for such tests.

There's clearly a fault in a router that these sites connect through (loss of BGP routes to certain ranges) and started exactly at 00:00 on 9th July. Until the ultimate correct entity and person responsible for that equipment can be notified, it's not going to get fixed outside of any further routine maintenance which would be of an indefinite timeframe.