Due to a critical issue, the legacy Teleport version 7 service provided through jump.ecmwf.int will be decommissioned on Monday 16 June 2025. After that date, it will no longer be possible to use jump.ecmwf.int to connect to our computing resources. Teleport version 17 - jump-17.ecmwf.int - has been running in parallel for several months and is now the primary Teleport service.

If you have not migrated to the new Teleport version 17, you must do so urgently. Please see our Teleport SSH Access documentation which has been updated to provide instructions for using the new jump-17.ecmwf.int.

  • We strongly recommend that you use a tsh client version 17.x to connect. If you already have a version 17.x client, we also recommend that update it to the latest version available (17.5.2 or above).
  • You will need to update your ssh config file (found in $HOME/.ssh/config) to provide the necessary configuration for connecting via jump-17.ecmwf.int as this is different to that used for connecting via jump.ecmwf.int. The changes needed are described in our Teleport SSH Access documentation.
  • If you are using Visual Studio Code with the Remote SSH extension, you may also need to make changes to your settings. Again, these changes are documented in our Teleport SSH Access.

If you cannot migrate in time, you may use these alternative methods to connect to our computing resources:

If you have any questions, encounter any problems or need help with migrating to Teleport version 17 then please open a Software and Computing issue in the ECMWF Support Portal. If there is an error, please provide in the issue the information requested under Troubleshooting in the Teleport SSH Access documentation.

We sincerely apologise for the inconvenience this may cause and appreciate your understanding and cooperation in this matter.

  • No labels