Claude Code is down.Is it just me?

Check official status, community reports, and opt-in client signals in one place,then decide whether an AI service issue is local or widespread.

Source-aware AI status

Official status, manual reports, and installed-client signals stay separatedso users can see whether others are experiencing the same issue before deciding what to do next.

Official status

Provider feeds are shown separately from Not Just You signals.

Community reports

Manual browser reports remain available as a fallback signal.

Installed signals

Opt-in clients send metadata-only failure signals from real workflows.

Privacy boundary by default

Installed clients send service-level metadata only. Prompt text, provider bodies, headers, API keys, file paths, and account identifiers are outside the collection boundary.

Collected metadata

Service id, symptom, status code when available, duration, short error code, source, and observed time.

Excluded payloads

Prompts, messages, request or response bodies, headers, API keys, cookies, file paths, exact IP addresses, usernames.

{
  "serviceId": "anthropic-claude-api",
  "source": "api_middleware",
  "symptom": "network_error",
  "durationMs": 5500,
  "errorCode": "timeout"
}

Dashboard

Live status cards keep official status, community reports, and installed-client signals separated by source.

Claude Code

recent signals
0
Official status
Unknown
Community reports
Loading
Installed signals
Loading
Manual community reportFallback

Claude.ai

recent signals
0
Official status
Unknown
Community reports
Loading
Installed signals
Loading
Manual community reportFallback

Claude Cowork

recent signals
0
Official status
Unknown
Community reports
Loading
Installed signals
Loading
Manual community reportFallback

Claude API

recent signals
0
Official status
Unknown
Community reports
Loading
Installed signals
Loading
Manual community reportFallback

Docs

Install the clients, wire provider calls, and check supported service ids without leaving this page.

CLI

Use the CLI for quick status checks and explicit local reporting setup.

npm install -g @notjustyou/cli
njy status
njy status anthropic-claude-code
njy status openai-api --watch

MCP

Register the stdio MCP server in clients that support MCP tools.

npm install -g @notjustyou/mcp

Configure `notjustyou-mcp` as a stdio server in your client. The MCP tools read public status summaries and can guide explicit local reporting setup where supported.

Plugins

Plugins keep status lookup close to the AI client you are already using.

Claude Code

/plugin marketplace add dobbylee/notjustyou
/plugin install notjustyou@notjustyou

Codex

codex plugin marketplace add dobbylee/notjustyou
codex plugin add notjustyou@notjustyou

Cursor and Antigravity plugins are published as packages and currently use manual local plugin installation. Package READMEs remain the source of truth for client-specific setup.

SDK

Wrap AI provider calls to contribute opt-in metadata-only failure signals.

njy setup --service openai-api
npm install @notjustyou/sdk-js

Supported SDK service ids are `openai-api`, `anthropic-claude-api`, and `google-gemini-api`.

Supported surfaces

Surface ids are stable identifiers for dashboard lookup, CLI commands, MCP tools, and SDK setup.

Anthropic

  • Claude Codeanthropic-claude-code
  • Claude.aianthropic-claude-ai
  • Claude Coworkanthropic-claude-cowork
  • Claude APIanthropic-claude-api

OpenAI

  • Codex CLIopenai-codex-cli
  • Codex Appopenai-codex-app
  • ChatGPTopenai-chatgpt
  • OpenAI APIopenai-api

Google

  • Antigravity CLIgoogle-antigravity-cli
  • Antigravity 2.0google-antigravity
  • Antigravity IDEgoogle-antigravity-ide
  • Gemini Webgoogle-gemini-web
  • Gemini Developer APIgoogle-gemini-api
  • Vertex Gemini APIgoogle-vertex-gemini-api

Cursor

  • Cursor IDEcursor-ide
  • Cursor CLIcursor-cli

Privacy boundary

Not Just You collects service-level status metadata, not user content.

It does not store prompt text, request or response bodies, headers, API keys, cookies, source files, diffs, file paths, clipboard content, exact IP addresses, account emails, machine names, local usernames, or workspace identifiers.

Package docs

Detailed package setup remains in the package README files.