SignalOS

System status

Real, live-measured numbers — read fresh on every load, never a cached badge.

As of Nov 6, 2026, 22:01 UTC

Components

DatabaseOperational
Job queue backend (Redis)Operational
Background job queues0 waiting, 0 active, 0 failed

AI search engines

Real per-engine health, the same signal the measurement pipeline itself uses to decide whether to attempt a call.

ChatGPTDown
ClaudeDown
Microsoft Copilot / BingDown
DeepSeekDown
FireworksDown
GeminiDown
Google AI Overviews / AI ModeDown
Grok (X)Down
GroqDown
Manually Recorded ObservationOperational
MistralDown
Claude (via OpenRouter)Down
DeepSeek (via OpenRouter)Down
Gemini (via OpenRouter)Down
GPT (via OpenRouter)Down
Grok (via OpenRouter)Down
Llama (via OpenRouter)Down
Mistral (via OpenRouter)Down
Qwen (via OpenRouter)Down
PerplexityDown
QwenDown
TogetherDown

Service level objectives

Real targets, checked against real measured data below — not aspirational numbers with nothing behind them.

Measurement job success rateTarget: 99% or higher, rolling 24 hours.No measurement runs completed in the last 24 hours.
Report generation time (p95)Target: under 60s, p95 over a rolling 30 days.No reports generated in the last 30 days with timing recorded yet.
Dashboard load time (p95)Target: under 2.5s interactive, Fast-4G + throttled CPU.Checked automatically against a real staging environment before every production deploy — see the performance-gate job in .github/workflows/ci.yml. Not yet continuously monitored in production itself; see the note below.

About uptime monitoring

This page reflects this server's own live view of its own dependencies at the moment you loaded it — it cannot tell you whether the server itself was unreachable five minutes ago. Real historical uptime tracking and public incident history require an independent, external monitor (e.g. a third-party uptime-checking service) watching this app from outside its own infrastructure — not yet configured for this deployment.