Radar
rpcxworkerWatch a URL
~/radar❯status

Radar status

Is Radar itself running well? This page shows our own checkers — not the projects you watch.

Checking…

Loading… · Solana mainnet-beta

Website checks…

No data from the worker yet.

Solana lookups…

No RPC data yet.

X posts…

No X data yet.

Alert delivery…

No delivery data yet.

Slow checker ≠ site down

If our checker is slow, projects show "monitoring delayed" — never "site down".

The project's site
site up
≠
Our checker
monitoring delayed
How this works

"Site down" needs 3 scheduled checks in a row failing with 5xx or a timeout. 403 / challenge / CAPTCHA is "blocked", not down. While our worker is late or stopped, no "site down" alert is sent and missing data is never read as deletion.

For operators

Technical details

Worker, queues and providers behind the tiles above. You don't need this to use Radar.

Workerunknown
last heartbeat
—

The worker writes a heartbeat to Redis. Older than 45 s → late; older than 2 min → stopped.

Job queues (BullMQ)no data

The server did not report queue counts.

Providers0 / 5 ok
Solana RPCunknown
mainnet-beta
Read-only. On-chain type is a fact, not a safety rating.
Helius (transaction history)unknown
Not set: history is read over plain Solana RPC (slower, rate-limited). Dev, sniper, sell and fee-claim tracking still work.
TwitterAPI.iounknown
Telegram botunknown
Web pushunknown
VAPID keys present.
Storage—
Postgres
not reported
Redis
not reported
Health endpoints
GET /health/liveprobing…
GET /health/readyprobing…

Probed from your browser. ready = Postgres, Redis and queues ok. It never depends on other people's sites.

Raw statusGET /api/status
…