Gitpod · Operational
Observed by INTERNETMON
← All status pages
Vendor-reported status observed by INTERNETMON

Gitpod status

Gitpod · Atlassian Statuspage
Operational
Atlassian Statuspage reports All Systems Operational.
Official service health, components and incident updates
Checked Poll cadence every 60 seconds Feed state fresh
Official signal: this is the provider's own report, collected and retained inside INTERNETMON. Compare it with independent regional monitoring when troubleshooting.

Active incidents

No active incidents were included in this vendor report.

Maintenance

No active or upcoming maintenance was included in this vendor report.

Component health

Reported
22
Retained
22
Affected retained
0
Projection scope: complete · 22 retained of 22 reported components across 1 source group.
Google Cloud Platform Google Container Registry Group: Third parties services Operational
Website Operational
Google Cloud Platform Google Cloud DNS Group: Third parties services Operational
[PAYG] Dashboard Operational
[PAYG] Workspaces Operational
Google Cloud Platform Google Kubernetes Engine Group: Third parties services Operational
Google Cloud Platform Google Compute Engine Group: Third parties services Operational
[PAYG] Prebuilds Operational
GitHub Webhooks Group: Third parties services Operational
[PAYG] Image Builds Operational
GitHub Git Operations Group: Third parties services Operational
[PAYG] Desktop IDE Access Operational
GitHub API Requests Group: Third parties services Operational
[FLEX] Dashboard Operational
Open VSX Registry Group: Third parties services Operational
[FLEX] Environments Operational
Netlify Content Distribution Network Group: Third parties services Operational
[FLEX] Runners Operational
GitLab API Requests Group: Third parties services Operational
[FLEX] Gateway Operational
Showing 20 of 22 retained components in the compact HTML summary. The JSON projection and interactive view contain the full bounded sample.

Recent observed status changes and checkpoints

These are sparse stored checkpoints—state changes plus hourly samples—not an uptime calculation or an exact incident duration.

Operational
HTTP 200 · 203.9 ms feed latency
Operational
HTTP 200 · 342.15 ms feed latency
Operational
HTTP 200 · 313.61 ms feed latency
Operational
HTTP 200 · 329.21 ms feed latency
Operational
HTTP 200 · 339.66 ms feed latency
Operational
HTTP 200 · 267.52 ms feed latency
Operational
HTTP 200 · 310.33 ms feed latency
Operational
HTTP 200 · 222.68 ms feed latency
Operational
HTTP 200 · 292.46 ms feed latency
Operational
HTTP 200 · 188.65 ms feed latency

Collection details

Provider adapter
Atlassian Statuspage
Feed response
HTTP 200
Feed latency
286.01 ms