GitHub incident is causing elevated error rate for 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 2h 46m it lasted.

  Anything that failed between 2026-08-17 15:02 UTC and 2026-08-17 17:47 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. investigatingAug 17, 2026, 3:02 PM UTC

   GitHub originated incident is resulting in environments being unable to checkout content, webhooks for automations are not being delivered.

   provider

2. monitoringAug 17, 2026, 4:02 PM UTC

   GitHub continues to be affected with many of their services degraded - [https://www.githubstatus.com/incidents/zkxwbgr0cnmx](https://www.githubstatus.com/incidents/zkxwbgr0cnmx "https://www.githubstatus.com/incidents/zkxwbgr0cnmx"). Ona environments and agent sessions using GitHub are impacted.

   provider

3. monitoringAug 17, 2026, 5:06 PM UTC

   GitHub has indicated the issue has been resolved, we're seeing improvements to the error rate and continue to observe.

   provider

4. resolvedAug 17, 2026, 5:47 PM UTC

   We're no longer seeing degradation when interacting with GitHub.

   provider

Corrections

None so far.

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