Platform status
operational Every component answered its last probe as expected.
As of . Probes re-run at most once every 45 seconds.
| Component | Reference | Reading | Taken |
|---|---|---|---|
| Web consoleThe site and the analyst console: submitting a scan, reading a report, and the live WebSocket that streams a run as it happens. | web | operational | |
| Submission queueThe task queue that accepts a submission and carries it through to a finished report, and the scheduler behind the recurring work. | queue | operational | |
| Detonation fleetThe virtual machines samples run in, the pool of pre-restored guests waiting to take the next scan, and the live VNC view onto them. | detonation | operational | |
| Static analysisThe layer that parses and inspects a sample without running it: format parsing, rule matching, capability and string extraction, signature checks and disassembly. | static | not probed | |
| Threat intelligence feedsThe indicator, hash and reputation sources that are ingested on a schedule and queried while a scan is scored. | intel | operational | |
| Report storageWhere finished reports, samples, artifacts, screenshots and captures are kept, and what the exports and downloads are served from. | storage | operational | |
| REST APIThe bearer-token HTTP API for submitting scans by hash, URL, command or package name, polling their status, and reading a finished report. | api | operational | |
| MCP serverThe Model Context Protocol endpoint that exposes hash lookup, indicator search, scan submission, polling and report retrieval as tools. | mcp | operational |
What a reading is worth
operational means the probe reached the component and it answered as expected. degraded means it answered in a condition that can slow a scan or thin a report. unavailable means it did not answer. unknown means no usable reading was taken, which is not a claim that anything is down. not probed means no honest cheap check exists for that component. Today that is Static analysis, which runs inside a scan on the analysis workers.
There is no uptime figure, no incident history and no availability commitment anywhere on this page. Those are claims about time, and nothing here measures time: a reading says what a component was doing when it was last checked, and a measurement is not a commitment.
REST API and MCP server are served by the same process as this page and carry its reading rather than one of their own. A time in the past is normal, because readings are taken on a cycle. A reading here can disagree with what you are seeing, and when it does, what you are seeing is the better evidence: the probes check whether a component answers, not whether your scan got what it needed from it.
Seeing something this page does not show? Send the report link or scan identifier, the time you submitted it, and the reference from the table to the address on the contact page. A vulnerability goes to the disclosure address on the security page instead.