approveddatafeeds outage

[Phil Wieland]

Is anyone back on after this morning's planned works?  I'm still unable to connect to approveddatafeeds.networkrail.co.uk:61618.

Phil

[Peter Hicks]

On Friday, 10 April 2026 at 10:53, Phil Wieland <philw...@gmail.com> wrote:

Is anyone back on after this morning's planned works? I'm still unable to connect to approveddatafeeds.networkrail.co.uk:61618.

This is not the first time somebody's raised an outage on the list and minutes later, it's miraculously resolved itself.

Peter

[Phil Wieland]

In the unlikely event that I fixed it, you're welcome!

[Matthew Burdett]

I didn't think I'd need to post it here; an email came through about planned maintance on both feeds the other day. Came from a DSG NROD email.

Kind regards 

--
You received this message because you are subscribed to the Google Groups "A gathering place for the Open Rail Data community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openraildata-t...@googlegroups.com.
To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/ddf2eb80-73ec-4bf9-82b2-2006e340ac32n%40googlegroups.com.

[Phil Wieland]

That said a brief disruption between 10:00 and 10:30.  Which is not what happened.

[James Uppington]

I’m still unable to connect at the moment. I’ve tried switching to my alternative connection in case my exponential backoff wasn’t good enough to avoid me being blocked during the outage but to no luck.

To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/e864fba4-371d-48ab-a07a-620d59cf3ae8n%40googlegroups.com.

[Matthew Burdett]

Also still unable to connect

 Public feed fine. Kafka VSTP on rdm I also getting fine.

To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/53B45EEF-939A-47FA-9901-3229A8DC9EB6%40gmail.com.

[James Uppington]

Just switched from port 61629, which I’ve been using fine for a long time, to 61619 and it’s successfully connected.

To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/CA%2B2-wYHrbUqZyP-PuhDfvKH-H6tq4pg1rMXaghsWrJQEno7e7g%40mail.gmail.com.

[Peter Hicks]

On Friday, 10 April 2026 at 11:34, James Uppington <upp...@gmail.com> wrote:

Just switched from port 61629, which I’ve been using fine for a long time, to 61619 and it’s successfully connected.

Wasn't this the new Artemis server commissioned in 2023, swapped with the ActiveMQ server on port 61619 a while ago, and then decommissioned fairly recently?  I recall getting an email about it - I'm guessing part of this month's maintenance was to turn it off.

Peter

[Malcolm Bovey]

Hi all,

Am still having trouble logging into NROD via STOMP to approveddatafeeds (port 61628) - is anyone else still having trouble?  Are there any non-deprecated ports that are working?

thanks

Malcolm

[Peter Hicks]

Hi Malcolm

On Monday, 13 April 2026 at 09:30, Malcolm Bovey <malcol...@gmail.com> wrote:

Am still having trouble logging into NROD via STOMP to approveddatafeeds (port 61628) - is anyone else still having trouble? Are there any non-deprecated ports that are working?

61618?

Peter

[Malcolm Bovey]

No 61628 - that's the port NROD advised to use when they did the server switchover a few years ago.  Have been using it since Feb 2024 and haven't received anything saying that's no longer correct?   Have tested 61618 and it does seem to work, however.

thanks

Malcolm

[Matthew Burdett]

I received an email 16th Feb telling me to switch to 61618.

--
You received this message because you are subscribed to the Google Groups "A gathering place for the Open Rail Data community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openraildata-t...@googlegroups.com.

To view this discussion, visit https://groups.google.com/d/msgid/openraildata-talk/07578a5e-300e-4611-b648-02e11670f1f6n%40googlegroups.com.

[Peter Hicks]

Hi Malcolm

On Monday, 13 April 2026 at 09:47, Malcolm Bovey <malcol...@gmail.com> wrote:

No 61628 - that's the port NROD advised to use when they did the server switchover a few years ago. Have been using it since Feb 2024 and haven't received anything saying that's no longer correct? Have tested 61618 and it does seem to work, however.

From memory, NROD was migrated from ActiveMQ to Artemis to improve stability.  As part of this migration, it was agreed that ports 61618 and 61619 would always point to the 'live' server, and ports 616128 and 61629 would point to the previously live server.  This means that any user experiencing problems after switch-over from ActiveMQ to Artemis would be able to change their configuration and access the old server in order to investigate.

If you'd switched over to 61628 or 61629, you were initially using Artemis and testing the new configuration, and after cut-over, you were using the old ActiveMQ server as fallback.  I believe that has now been deprecated, hence you're unable to connect to it.

Peter

[Malcolm Bovey]

OK, thanks all.  I'd missed that 61628/9 were mapped to the old servevr.   Have updated my service to use 61618 now and it seems to be working