Forge tunnels are not functional - requests are not being routed to the tunnel

We have successfully released new version of forge tunnel docker image (atlassian/forge-tunnel:latest) with a fix.
All newly started tunnels should function as expected.

There is small chance that developers using custom docker mirrors will still experience tunnel failure if mirror is stuck on old image. In such case pulling image (docker pull atlassian/forge-tunnel:latest) with mirror disabled should help to get latest version of this image (with checksum 6e1894a8cd92).

The impact window was from 2023-06-27 21:00 UTC until 2023-06-27 11:40 UTC.

Please note that Runtime V2 which is in Early Access Program requires additional mitigation and is still impacted. We will provide dedicated communication about progress of fixing this problem for Runtime V2 in dedicated slack channel.

This incident is now resolved.

We have found the root cause of problem which is causing Forge apps to be unable to connect via development tunnel.

We are working on the solution which requires release of new forge-tunnel version. Once the release is completed newly started tunnels should be able to connect correctly.

We have identified that tunnels started in US should not be impacted by this incident.

Next update will be posted around 14:00 UTC.

We are investigating problem with Forge tunnels - requests are being routed to the Forge infrastructure (to deployed version of the App) even when tunnel is active.

Tunnel doesn't show any logs. No errors are shown in the tunnel console.

This problem does not affect regular production traffic - it's only related to Forge tunnel functionality used during development.

We will post next update around 10:00 UTC.