Vendor-reported status observed by INTERNETMON
GitLab status
GitLab · Status Io
Status.io reports 23 component(s), 0 active incident(s), 0 active maintenance window(s), and 0 upcoming maintenance window(s).
GitLab.com and related services
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
23
Retained
23
Affected retained
0
Projection scope: complete · 23 retained of 23 reported components across 5 source groups.
Website
Group: Google Compute Engine
Operational
API
Group: Google Compute Engine
Operational
Git Operations
Group: Google Compute Engine
Operational
Package Registry
Group: Google Compute Engine
Operational
Container Registry
Group: Google Compute Engine
Operational
GitLab Pages
Group: Google Compute Engine
Operational
CI/CD
Group: Google Compute Engine
Operational
CI/CD - Hosted runners on Linux
Group: Google Compute Engine
Operational
CI/CD - Hosted runners on Windows
Group: Google Compute Engine
Operational
CI/CD - Hosted runners on macOS
Scope: Google Compute Engine (Operational) · Scope: AWS (Operational)
Operational
CI/CD - Hosted runners for GitLab community contributions
Group: Google Compute Engine
Operational
CI/CD - Self-managed runners
Group: Self-Managed Runner Connectivity
Operational
SAML SSO - GitLab SaaS
Group: Google Compute Engine
Operational
Background Processing
Group: Google Compute Engine
Operational
GitLab Customers Portal
Group: Google Compute Engine
Operational
Support Services
Group: Zendesk
Operational
packages.gitlab.com
Group: AWS
Operational
version.gitlab.com
Group: AWS
Operational
forum.gitlab.com
Group: Digital Ocean
Operational
docs.gitlab.com
Group: Google Compute Engine
Operational
Showing 20 of 23 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 · 470.89 ms feed latency
Operational
HTTP 200 · 528.38 ms feed latency
Operational
HTTP 200 · 637.69 ms feed latency
Operational
HTTP 200 · 535.46 ms feed latency
Operational
HTTP 200 · 711.24 ms feed latency
Operational
HTTP 200 · 670.87 ms feed latency
Operational
HTTP 200 · 368.24 ms feed latency
Operational
HTTP 200 · 799.45 ms feed latency
Operational
HTTP 200 · 493.17 ms feed latency
Operational
HTTP 200 · 492.24 ms feed latency
Collection details
Provider adapter
Status Io
Feed response
HTTP 200
Feed latency
647.54 ms
JSON source