Configuration to TLS 1.2 & 1.3 – Timings Confirmed

Following my previous post on January 19, I can now confirm specific dates and timings for the implementation of our new configuration to TLS 1.2 and 1.3.

We've rolled back our change, giving open data users extra time to update their tooling to support modern TLS versions (1.2 and 1.3)
We’re implementing our new configuration to TLS 1.2 and 1.3 as a phased approach, starting at 10.30 tomorrow morning

We will be implementing this as a phased approach starting at 10.30 tomorrow morning (Thursday 26 January). Between 10:30 and 16:00 we’ll turn this on, and will be monitoring its performance.

If this goes as planned, we will make the permanent switch on Tuesday 31 January at 10:30.

To prevent any issues with using our data feeds, please could you make sure you have updated your tooling to support the newer versions of TLS by 10.30 tomorrow morning.

Again, if you need to test against our new configuration, please click the below URL:

Details on supported cypher suites and related toolsets & browsers can be found at

1 Comment

  1. I can no longer get Next Bus or Journey Planner information on my SamsungTab 3 or Galaxy Y phone. Do improvements for users of more recent software justify denial of service to myself and others, perhaps of limited means, using older software?

Comments are closed.