Voidly / Status
Know what’s
up.
Service checks. Source freshness.
Seen from your network.
Checking services…
Checking public endpoints…
Service health
30-second refresh · 5-second timeout
01Worker APIUnknown—
Public API routing and upstream health response.
This check has not returned a result.
Unavailable
Source response ↗02IntelligenceUnknown—
Classifier service health. This check does not measure model accuracy.
This check has not returned a result.
Unavailable
Source response ↗03Country dataUnknown—
Public country index through the Worker. dataAsOf describes ingestion; generated_at_utc is response generation.
This check has not returned a result.
Unavailable
Source response ↗Newest source ingestion: Unavailable
04Pay stagingUnknown—
Legacy zero-value Private Sessions staging config. Separate from the current Pay release and Proofs.
This check has not returned a result.
Unavailable
Source response ↗Current Pay release →Proofs →05Sentinel forecastUnknown—
Forecast health and upstream freshness. A response alone is not a prediction-quality result.
This check has not returned a result.
Unavailable
Source response ↗06Probe networkUnknown—
Source-reported active nodes. The existing warning policy applies a minimum of 10; this threshold is not a fleet count.
This check has not returned a result.
Unavailable
Source response ↗07Incident corpusUnknown—
Incident and evidence totals. Includes disruption and suspected records; not a count of confirmed censorship.
This check has not returned a result.
Unavailable
Source response ↗Green requires the expected response within 1,500 ms. Slow or unexpected responses are degraded; HTTP 5xx is an error. A timeout, blocked request or CORS failure is unknown—not evidence of a global outage.
When data last moved.
Source timestamps, separate from this browser’s check time.
Thresholds come from Sentinel health. Missing flags stay unknown. Dates without a timezone remain explicitly unspecified.
Data health and staging details
Latest incident date: Unavailable. Latest probe result: Unavailable.
Legacy Pay staging response: amount unavailable; paid authorizations —; settlements —. These fields describe that staging service only.
Corpus totals include censorship, mixed and disruption records with different evidence and status levels.
Inspect records →Data quality →Operations, in the open.
Source status: unavailable
Watchdog Unavailable
Automation, limits and source code
The public log reports watchdog checks, triage decisions, playbook runs and budget state. Its “healthy” status uses the last watchdog run and open warnings; it does not prove every automated action succeeded.
Last triage: Unavailable. Playbook runs / 24h: —.
Probe credit accrual is distinct from an executed payout. These code paths and log counters do not establish payment or end-to-end release capability.
Operations JSON ↗Probe operator entry →Uptime history and reporting limits
90-day uptime and total requests served are unavailable here. This page has no rolling public probe history; a check is a point-in-time observation.
The original status page contains an empty, manually maintained incident section without a dated archive. This preview cannot establish that no incidents occurred or supply a tracking start date.
Checks run in your browser against public endpoints. The operations log is a separate server-reported source. Upstream caches and your network can affect results.
Back to service checks →Public source repository ↗Something broken?
Send the signal.
Include the surface, timestamp and steps to reproduce.