Namespace Status
System status
Incident overview
Total incidents
47
Active now
0
Resolved
47
Avg. resolution
1h 52m
Recent incidents
View all →Ingress disruption in iad
Elevated queue time for GitHub Jobs
Increased error rate when starting Remote Builders, Bazel Clusters and Devboxes
Elevated queue time on GitHub jobs
Increased queue time for jobs using macOS runners
Delayed events from GitHub leading to increased queueing time
Degraded registry and artifact performance in Western Europe region
Increased queue time for subset of jobs
Failing instance lists and a subset of RPCs
Increased queue time
Frequently asked questions
Is Namespace down right now?
Namespace is currently operational. DevHelm monitors Namespace's official status page continuously and updates this page every 5 minutes.
What is Namespace's current uptime?
Namespace has a measured 30-day uptime of 99.99%. Over the last 24 hours, uptime is 100.00%, and over 7 days it is 99.99%. These figures are computed from Namespace's official status page data.
How many incidents has Namespace had recently?
Namespace has experienced 47 incidents in the recent monitoring window. Resolved incidents were fixed in an average of 1h 52m. All incidents are currently resolved.
What components does Namespace monitor?
DevHelm tracks 26 individual components for Namespace, including Artifacts, Container Registry, GitHub Runners, Previews, Remote Builders, and 21 more. Each component has its own status and 90-day uptime history shown above.
How can I get notified about Namespace outages?
You can subscribe to Namespace's incident feed via Atom/RSS at devhelm.io/status/namespace/feed.xml for use in any feed reader. For real-time alerts via Slack, email, PagerDuty, or webhooks, add Namespace as a dependency in your DevHelm workspace.
About Namespace status monitoring
This page provides real-time operational status for Namespace, powered by DevHelm's continuous monitoring infrastructure. We track Namespace's official status page and aggregate component-level data into uptime percentages, incident timelines, and historical trends.
Namespace status data is refreshed every 5 minutes. We currently track 26 individual components, each with its own operational status and 90-day uptime history.
Uptime percentages represent the proportion of time all monitored components reported operational status. Incident data comes from vendor-published incident timelines and includes status updates, affected components, and resolution times.
Track Namespace in your stack
Get alerted when Namespace has issues — before your users notice. Set up in 30 seconds.