Skip to main content
Gitpod

Degraded performance for agent session starts, VS Code Browser, services, and tasks

Degraded Lasted 4h 37m · started · Gitpod's page

Level
confirmed
Worst impact
Degraded
Down Index
21of 100

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 4h 37m it lasted.

    Anything that failed between 2026-06-18 12:59 UTC and 2026-06-18 17:36 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 6

  1. investigating

    We're seeing an increase in start duration for agent sessions. The environment starts normally but agents are taking a while to start. We're actively investigating the issue

    provider

  2. investigating

    We've observed that VS Code Browser, services, and tasks are also suffering from degraded performance.

    provider

  3. monitoring

    We scaled messaging infrastructure to address a capacity issue, and have observed performance is now normal. We'll continue to monitor to ensure the problem is resolved.

    provider

  4. monitoring

    Degraded performance is ongoing, we'll pursing a follow-up fix to mitigate, and will update the incident in 30m.

    provider

  5. monitoring

    We shipped a fix to shift traffic to the newly scaled up infrastructure and have observed an improvement in performance. We'll continue to monitor the situation.

    provider

  6. resolved

    Performance continues to remain quick and stable.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

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

Questions about DWN-13049223df

Is Gitpod still down?

No, this incident was resolved 2026-06-18 17:36 UTC. For Gitpod's live state, see https://down.guide/gitpod.

How long did it last?

4h 37m, from 2026-06-18 12:59 UTC to 2026-06-18 17:36 UTC, by the times Gitpod posted.

What caused it?

Gitpod hasn't published a root cause. If it does, it shows here.

Where does this come from?

Gitpod's official status page, https://onastatus.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.