Realm: nwas.nhs.uk Full
nwas.nhs.uk/nwas-nhs-uk-0/NRPS: roaming0.govroam.uk
(212.219.190.139) -
Unknown Client
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
Port 1812 Drop
/
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 3.07 ms
- Last State Change
- Tue Jul 7 08:45:54 2026
- Last Check
- Thu Jul 16 04:45:45 2026
- Next Check
- Thu Jul 16 04:55:45 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jul 14 18:35:18 2026
- Last Check
- Thu Jul 16 04:45:16 2026
- Next Check
- Thu Jul 16 04:55:16 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Jul 7 08:46:59 2026
- Last Check
- Thu Jul 16 04:44:57 2026
- Next Check
- Thu Jul 16 04:54:57 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Jul 7 08:50:30 2026
- Last Check
- Thu Jul 16 04:48:26 2026
- Next Check
- Thu Jul 16 04:58:26 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
nwas.nhs.uk/nwas-nhs-uk-0/roaming0.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Tue Jul 7 08:49:51 2026
- Last Check
- Thu Jul 16 04:47:49 2026
- Next Check
- Thu Jul 16 04:57:49 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
nwas.nhs.uk/nwas-nhs-uk-0/NRPS: roaming1.govroam.uk
(212.219.209.43) -
Unknown Client
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
Port 1812 Drop
/
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 2.76 ms
- Last State Change
- Tue Jul 7 08:45:35 2026
- Last Check
- Thu Jul 16 04:45:25 2026
- Next Check
- Thu Jul 16 04:55:25 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jul 14 18:37:52 2026
- Last Check
- Thu Jul 16 04:47:52 2026
- Next Check
- Thu Jul 16 04:57:51 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Jul 7 08:44:19 2026
- Last Check
- Thu Jul 16 04:52:16 2026
- Next Check
- Thu Jul 16 05:02:16 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Jul 7 08:43:00 2026
- Last Check
- Thu Jul 16 04:50:56 2026
- Next Check
- Thu Jul 16 05:00:56 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
nwas.nhs.uk/nwas-nhs-uk-0/roaming1.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Wed Jul 15 08:43:03 2026
- Last Check
- Thu Jul 16 04:53:02 2026
- Next Check
- Thu Jul 16 05:03:02 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
nwas.nhs.uk/nwas-nhs-uk-0/NRPS: roaming2.govroam.uk
(212.219.247.59) -
Unknown Client
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
Port 1812 Drop
/
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 9.29 ms
- Last State Change
- Wed Jul 15 02:45:38 2026
- Last Check
- Thu Jul 16 04:45:28 2026
- Next Check
- Thu Jul 16 04:55:28 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Wed Jul 15 02:45:23 2026
- Last Check
- Thu Jul 16 04:45:21 2026
- Next Check
- Thu Jul 16 04:55:21 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Jul 7 08:38:45 2026
- Last Check
- Thu Jul 16 04:46:43 2026
- Next Check
- Thu Jul 16 04:56:43 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Jul 7 08:38:15 2026
- Last Check
- Thu Jul 16 04:46:12 2026
- Next Check
- Thu Jul 16 04:56:12 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
nwas.nhs.uk/nwas-nhs-uk-0/roaming2.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Mon Jul 13 09:48:09 2026
- Last Check
- Thu Jul 16 04:48:08 2026
- Next Check
- Thu Jul 16 04:58:08 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
nwas.nhs.uk/nwas-nhs-uk-0/NRPS: roaming3.govroam.uk
(195.194.21.203) -
Unknown Client
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
Port 1812 Drop
/
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 9.21 ms
- Last State Change
- Tue Jul 7 08:31:02 2026
- Last Check
- Thu Jul 16 04:50:52 2026
- Next Check
- Thu Jul 16 05:00:52 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jul 7 08:33:52 2026
- Last Check
- Thu Jul 16 04:53:50 2026
- Next Check
- Thu Jul 16 05:03:50 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Jul 7 08:35:44 2026
- Last Check
- Thu Jul 16 04:53:43 2026
- Next Check
- Thu Jul 16 05:03:42 2026
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Jul 7 08:32:02 2026
- Last Check
- Thu Jul 16 04:49:59 2026
- Next Check
- Thu Jul 16 04:59:58 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
nwas.nhs.uk/nwas-nhs-uk-0/roaming3.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Sat Jul 11 22:02:59 2026
- Last Check
- Thu Jul 16 04:52:58 2026
- Next Check
- Thu Jul 16 05:02:58 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
nwas.nhs.uk/nwas-nhs-uk-1/NRPS: roaming0.govroam.uk
(212.219.190.139) -
Unknown Client
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
Port 1812 Drop
/
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 2.44 ms
- Last State Change
- Tue Jul 14 18:35:23 2026
- Last Check
- Thu Jul 16 04:45:13 2026
- Next Check
- Thu Jul 16 04:55:13 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jul 14 18:36:45 2026
- Last Check
- Thu Jul 16 04:46:43 2026
- Next Check
- Thu Jul 16 04:56:43 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Jul 7 08:48:05 2026
- Last Check
- Thu Jul 16 04:46:02 2026
- Next Check
- Thu Jul 16 04:56:02 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Jul 7 08:48:21 2026
- Last Check
- Thu Jul 16 04:46:18 2026
- Next Check
- Thu Jul 16 04:56:18 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
nwas.nhs.uk/nwas-nhs-uk-1/roaming0.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Tue Jul 7 08:48:53 2026
- Last Check
- Thu Jul 16 04:46:52 2026
- Next Check
- Thu Jul 16 04:56:51 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
nwas.nhs.uk/nwas-nhs-uk-1/NRPS: roaming1.govroam.uk
(212.219.209.43) -
Unknown Client
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
Port 1812 Drop
/
nwas.nhs.uk/nwas-nhs-uk-1/roaming1.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 2.42 ms
- Last State Change
- Tue Jul 14 18:35:54 2026
- Last Check
- Thu Jul 16 04:45:43 2026
- Next Check
- Thu Jul 16 04:55:43 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming1.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jul 14 18:35:31 2026
- Last Check
- Thu Jul 16 04:45:29 2026
- Next Check
- Thu Jul 16 04:55:29 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming1.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Jul 7 08:43:44 2026
- Last Check
- Thu Jul 16 04:51:42 2026
- Next Check
- Thu Jul 16 05:01:42 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming1.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Jul 7 08:42:44 2026
- Last Check
- Thu Jul 16 04:50:40 2026
- Next Check
- Thu Jul 16 05:00:40 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
nwas.nhs.uk/nwas-nhs-uk-1/roaming1.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Fri Jul 10 21:20:47 2026
- Last Check
- Thu Jul 16 04:50:46 2026
- Next Check
- Thu Jul 16 05:00:46 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
nwas.nhs.uk/nwas-nhs-uk-1/NRPS: roaming2.govroam.uk
(212.219.247.59) -
Unknown Client
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
Port 1812 Drop
/
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 7.41 ms
- Last State Change
- Tue Jul 14 18:36:09 2026
- Last Check
- Thu Jul 16 04:45:59 2026
- Next Check
- Thu Jul 16 04:55:59 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jul 14 18:45:31 2026
- Last Check
- Thu Jul 16 04:45:30 2026
- Next Check
- Thu Jul 16 04:55:30 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Jul 7 08:41:04 2026
- Last Check
- Thu Jul 16 04:49:02 2026
- Next Check
- Thu Jul 16 04:59:02 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Jul 7 08:38:43 2026
- Last Check
- Thu Jul 16 04:46:39 2026
- Next Check
- Thu Jul 16 04:56:39 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
nwas.nhs.uk/nwas-nhs-uk-1/roaming2.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Wed Jul 15 14:14:55 2026
- Last Check
- Thu Jul 16 04:44:53 2026
- Next Check
- Thu Jul 16 04:54:53 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
nwas.nhs.uk/nwas-nhs-uk-1/NRPS: roaming3.govroam.uk
(195.194.21.203) -
Unknown Client
/
Bad Client Shared Secret
/
Dropping Auth Requests
/
Port 1812 Drop
/
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
Ping
- Output
- PING OK - Packet loss = 0%, RTA = 8.29 ms
- Last State Change
- Tue Jul 14 18:37:37 2026
- Last Check
- Thu Jul 16 04:47:28 2026
- Next Check
- Thu Jul 16 04:57:26 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
RADIUS Port
- Output
- OK: Port 1812 is probably open, unless there's a DROP firewall
- Last State Change
- Tue Jul 14 18:38:27 2026
- Last Check
- Thu Jul 16 04:48:25 2026
- Next Check
- Thu Jul 16 04:58:25 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
Server Shared Secret
- Output
- UNKNOWN: No Data. No logs to check for last day
- Last State Change
- Tue Jul 7 08:34:45 2026
- Last Check
- Thu Jul 16 04:52:43 2026
- Next Check
- Thu Jul 16 05:02:43 2026
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
Simple Authentication
- Output
- WARNING: Timeout. No response from RADIUS server
- Last State Change
- Tue Jul 7 08:35:04 2026
- Last Check
- Thu Jul 16 04:52:59 2026
- Next Check
- Thu Jul 16 05:02:59 2026
- Meaning:
- An authentication attempt has been made using generic credentials and no response was received. It's expected that a RADIUS server would respond to non-existent credentials with an Access-Reject and if it didn't then there might be a problem. It's not part of the Tech Spec that all requests should be responded to but it's desirable. It would help us keep better track of your system state. However, be aware that all proxied/EAP requests MUST be responded to.
- Solution:
- Check your RADIUS logs to see what's happening to these requests. The username is 'jisctest' so should stand out. If you can, please ensure that your RADIUS server responds to the requests (with an Access-Reject). Alternatively, enable Status-Server (FreeRADIUS, RADIATOR and radsecproxy support it).
nwas.nhs.uk/nwas-nhs-uk-1/roaming3.govroam.uk/
Zombie
- Output
- CRITICAL: Marked as down within the last day
- Last State Change
- Fri Jul 10 17:49:39 2026
- Last Check
- Thu Jul 16 04:49:38 2026
- Next Check
- Thu Jul 16 04:59:37 2026
- Meaning:
- Over the last day, the ORPS has been marked as 'down' by the NRPS. A server is marked as 'down' (or a Zombie) if it doesn't respond to an authentication query within 30s. If the ORPS is serving a Federation then the chances are that one of the Federation members isn't responding to a proxied query. If the ORPS isn't serving a Federation then it's a problem with the local configuration.
- Solution:
- An independently connected site needs to fix the configuration to ensure that the ORPS is sending a response to ALL auth requests. A Federation Operator nedds to check their logs to determine which members aren't sending responses and help them correct their configuration.
Called Station ID Check
- Output
- UNKNOWN: No Data
- Last State Change
- Tue Jul 7 08:20:42 2026
- Last Check
- Thu Jul 16 04:45:40 2026
- Next Check
- Thu Jul 16 05:00:39 2026
Calling Station ID Check
- Output
- UNKNOWN: No Data
- Last State Change
- Tue Jul 7 08:21:37 2026
- Last Check
- Thu Jul 16 04:46:35 2026
- Next Check
- Thu Jul 16 05:01:35 2026
Operator Check
- Output
- UNKNOWN: No data
- Last State Change
- Tue Jul 7 08:22:12 2026
- Last Check
- Thu Jul 16 04:47:11 2026
- Next Check
- Thu Jul 16 05:02:09 2026
Realm Syntax Check
- Output
- UNKNOWN: No data
- Last State Change
- Tue Jul 7 08:21:25 2026
- Last Check
- Thu Jul 16 04:46:23 2026
- Next Check
- Thu Jul 16 05:01:22 2026
VLAN Check
- Output
- UNKNOWN: No Data
- Last State Change
- Tue Jul 7 08:23:10 2026
- Last Check
- Thu Jul 16 04:48:05 2026
- Next Check
- Thu Jul 16 05:03:04 2026