All Systems Operational

About This Site

This is the status page for gitpod.io. For incidents prior to April 30th 2021 head over to our previous status page here.

Website ? Operational
90 days ago
100.0 % uptime
Today
Dashboard ? Operational
90 days ago
99.25 % uptime
Today
Workspaces ? Operational
90 days ago
99.62 % uptime
Today
Prebuilds ? Operational
90 days ago
99.98 % uptime
Today
Image Builds ? Operational
90 days ago
99.92 % uptime
Today
Desktop IDE Access ? Operational
90 days ago
99.93 % uptime
Today
Third parties services Operational
90 days ago
99.19 % uptime
Today
Google Cloud Platform Google Container Registry Operational
Google Cloud Platform Google Cloud DNS Operational
Google Cloud Platform Google Kubernetes Engine Operational
Google Cloud Platform Google Compute Engine Operational
GitHub Webhooks Operational
GitHub Git Operations Operational
GitHub API Requests Operational
Open VSX Registry Operational
90 days ago
99.19 % uptime
Today
Netlify Content Distribution Network Operational
GitLab API Requests Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Past Incidents
Aug 17, 2022

No incidents reported today.

Aug 16, 2022

No incidents reported.

Aug 15, 2022
Resolved - Since Saturday we no longer see issues with logins using gitlab.com. We will follow up with GitLab to identify the root cause and improve on our end if possible.
Aug 15, 10:59 UTC
Monitoring - We did not see the GitLab login error for at least two hours, and we'll keep monitoring it.
Aug 13, 14:27 UTC
Update - Please follow up the GitHub issue https://github.com/gitpod-io/gitpod/issues/12114
Aug 13, 08:58 UTC
Identified - It seems like GitLab issue, so we will file an issue to Gitlab to ask for further help. Unfortunately, there is nothing we can do at this point, so we keep the incident open to continue monitoring the situation. Worst case, it's probably okay to leave this as is until Monday and investigate this problem further.
Aug 13, 06:54 UTC
Update - Logging in to Gitpod with a GitLab account started failing at around 2022-08-13 @ 01:45 UTC. Our logs indicate that "the provided authorization grant is invalid, expired, revoked, does not match the redirection URI used in the authorization request, or was issued to another client". While we're actively investigating this problem, a workaround is to log in with a GitHub or Bitbucket account instead.
Aug 13, 05:27 UTC
Investigating - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Aug 13, 04:51 UTC
Resolved - All workspaces are accessible again.
Aug 15, 09:59 UTC
Monitoring - We identified and resolved the issue. Workspaces should be accessible again.
Aug 15, 08:22 UTC
Investigating - We've spotted that something has gone wrong. We're currently investigating the issue, and will provide an update soon.
Aug 15, 07:06 UTC
Aug 14, 2022

No incidents reported.

Aug 13, 2022
Aug 12, 2022

No incidents reported.

Aug 11, 2022
Resolved - Some workspaces could not be started, showing various errors like 'cannot find backup' or 'maximum parallel workspaces limit reached.
Aug 11, 08:00 UTC
Aug 10, 2022

No incidents reported.

Aug 9, 2022

No incidents reported.

Aug 8, 2022

No incidents reported.

Aug 7, 2022

No incidents reported.

Aug 6, 2022

No incidents reported.

Aug 5, 2022
Resolved - We deployed the fix. Local companion should be available again. VS Code users still please try new connectivity mode for better stability: https://www.gitpod.io/docs/ides-and-editors/vscode#connecting-to-vs-code-desktop-ssh
Aug 5, 18:03 UTC
Update - We found a reason and fixing it. VS Code Desktop users can switch to a new connectivity mode https://www.gitpod.io/docs/ides-and-editors/vscode#connecting-to-vs-code-desktop-ssh to resolve.
Aug 5, 17:39 UTC
Identified - We found a reason and fixing it. VS Code Desktop users can switch to a new connectivity mode https://www.gitpod.io/docs/ides-and-editors/vscode#connecting-to-vs-code-desktop-ssh to resolve.
Aug 5, 17:33 UTC
Resolved - We finished rolling out the fix to both regions yesterday, August 4th, and have confirmed this is resolved.
Aug 5, 12:00 UTC
Identified - Good news! We've got a promising fix, and plan to deploy and monitor in the US region on Wednesday. The deploy to the EU region will be contingent on success in the US region.
Aug 3, 00:24 UTC
Update - We're still seeing this issue intermittently manifest itself in `eu54`, and are working on a fix. A couple potential solutions were tested today in `us58`, but, they did not perform well enough. We'll share an update again tomorrow!
Aug 1, 21:51 UTC
Monitoring - We've released a fix for stuck workspaces and prebuilds in the US region; we will monitor this fix over the weekend to verify this issue has been resolved. Once we've confirmed everything's working as expected we'll deploy this change to the EU region.
Jul 29, 22:53 UTC
Update - We have isolated an issue with workspace prebuilds and are preparing a test to fix the issue.
Jul 29, 19:55 UTC
Update - We are continuing to investigate this issue.
Jul 29, 18:47 UTC
Update - We are continuing to investigate this issue.
Jul 29, 18:44 UTC
Investigating - Some users have reported that they're having trouble starting workspaces in the EU region, and when this happens the error indicates image pull trouble. We're investigating, more updates to follow!
Jul 29, 18:43 UTC
Aug 4, 2022

No incidents reported.

Aug 3, 2022