There is https://status.gitpod.io/ but it doesn’t mention capacity, only if the performance is currently degraded or some services are down.
Gitpod is expected to operate as fast as possible at all times. If it doesn’t, that’s a bug we need to fix (or at least investigate and document, e.g. if the problem is with the user’s connectivity / hardware / browser).
It would be helpful if you can provide more details on the performance symptoms you observe.
For example, here are a few common performance problems we occasionally see:
If the user is located far away from the nearest Gitpod cluster, the higher latency may slow down Gitpod page loads & Terminal responsiveness. (We’re considering adding new regional clusters in the coming months, notably to improve APAC latencies.)
If you start a workspace during regional cluster scale-up (e.g. during “morning rush-hour” when many people are starting workspaces at the same time) you may see prolonged “Acquiring Node” and “Pulling Docker Images” times during your workspace start-up. (This is something we’re currently working on fixing with predictive cluster scale-up.)
If your workflow requires multiple vCPUs to run at maximum speed for several minutes (e.g. compilation), you may see Gitpod’s CPU fair-use policy kick in, temporarily limiting your workspace to fewer vCPUs.