VSCode web and local not starting on new environments

What to do

• Check whether your product depends on Gitpod. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 59m it lasted.

  Anything that failed between 2026-03-16 14:54 UTC and 2026-03-16 15:53 UTC may need a replay.

• Subscribe to Gitpod's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=gitpod works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Gitpod 4

1. investigatingMar 16, 2026, 2:54 PM UTC

   VSCode web and local not starting on new environments. We're investigating.

   provider

2. identifiedMar 16, 2026, 2:57 PM UTC

   The issue is caused by VSCode Update Service unavailability - [https://github.com/microsoft/vscode/issues/302112](https://github.com/microsoft/vscode/issues/302112 "https://github.com/microsoft/vscode/issues/302112"). We're assessing what we can do to circumvent the issue now.

   provider

3. monitoringMar 16, 2026, 3:27 PM UTC

   Upstream recovered, VSCode is available in all Ona environments again

   provider

4. resolvedMar 16, 2026, 3:53 PM UTC

   Upstream failure rate has fully recovered, all environments operational since.

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.