Namespace logo

Is Namespace Down?

OtherLive status, outages, and incident history

No. Namespace is up right now.

Every monitored Namespace system is operational as of November 14, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 7m agoLive · every 60s

Know the moment Namespace breaks

Namespace is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

Free, no password, no card. Unsubscribe in one click.

Official Namespace status page
How we know: the official Namespace status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Namespace Status Summary

As of 17:49 UTC on 14 November 2026, Namespace is operational. PulsAPI checked Namespace's official status page and found 25 of 25 components operational, with no active incidents. The latest incident, "Partial log availability", was on Nov 12, 2026 and lasted 4h 38m.

Cite as: PulsAPI, “Namespace status”, checked 14 November 2026, 17:49 UTC. https://www.pulsapi.com/services/namespace

Namespace Component Status

The main Namespace systems on this page. All 25 are operational right now.

25operational
Artifacts
Operational
Bazel
Operational
Buildkite Agents
Operational

22 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking Container Registry, Dashboard, Devboxes, GitHub Runners, Illinois, US, Linux amd64, Linux arm64, Linux arm64 on Apple Silicon, Logging, MacOS arm64, Metrics, Northern Virginia, US, and 10 more.

See all of them free

Component statuses may change independently during partial outages.

Recent Namespace Outages & Incidents

Incident history from the official Namespace status page, including resolution updates.

Partial log availabilityResolved Nov 12, 2026 · 4h 38mResolved

All systems are operational. --- [2026-11-12T21:25:57Z] (monitoring) We're starting to see recovery. --- [2026-11-12T19:23:52Z] (identified) Some of the instance logs may not be available to queries. Our team is working through this.

Elevated queue time for GitHub JobsResolved Nov 11, 2026 · 40 minResolved

All systems are operational. --- [2026-11-11T21:33:37Z] (monitoring) The upstream incident has been resolved. --- [2026-11-11T20:53:03Z] (identified) Upstream incident <https://www.githubstatus.com/incidents/dvy0t3mvh1lg>

DNS resolution failures for Ubuntu archives Resolved Nov 11, 2026 · 3h 18mResolved

Our telemetry shows the mitigations were effective and we've seen error rate drop since applying them. Upstream DNS resolution has also recovered. --- [2026-11-11T15:24:47Z] (monitoring) The upstream incident remains ongoing. We have deployed a mitigation to address DNS resolution failures for Ubuntu archives and are monitoring its effectiveness. --- [2026-11-11T14:50:30Z] (monitoring) We're seeing an increased rate of DNS resolution failures for Ubuntu archives, leading to `apt-get` failures. This is related to an upstream incident tracked at <https://status.canonical.com/#/incident/KNms6QK9ewuzz-7xUsPsNylV20jEt5kyKsd8A-3ptQFX-3WclTLkuMGEkQ0cQPf-nRNYHaA8K7mU9EKLLx1dRw%3D%3D>

Namespace Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a Namespace incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history3 days observed
Nov 12100.00% average · 2 days with incidentsNov 14

Live Namespace Outage Reports

Problems reported by engineers using Namespace. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow

No Namespace problems reported yet.

Something wrong with Namespace on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About Namespace

Namespace posts its status at namespace-status.com. The page covers 25 components, among them Artifacts, Bazel and Container Registry. Past incidents and uptime for Namespace stay on this page, which helps when you want to know how often it has trouble.

Namespace Status FAQ

Is Namespace down right now?

The verdict at the top of this page comes from the latest poll of the official Namespace status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks it every 60 seconds.

What should I do if Namespace is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until Namespace recovers.

How do I check Namespace uptime history?

PulsAPI tracks Namespace uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Namespace changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Namespace outages?

PulsAPI reads the official Namespace status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Namespace components?

Yes. PulsAPI monitors 25 individual Namespace components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Namespace goes down?

Yes. Create a free account and subscribe to Namespace: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with Namespace to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot Namespace problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Namespace?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Namespace plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track Namespace with the rest of your stack

4372+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services