Pikoman status
Every five minutes our own server connects to Pikoman, publishes a message through the HTTP API and times how long it takes to arrive. This is what it found.
Checking the status…
Loading the latest checks.
- Uptime, 24 hours
- –
- Uptime, 7 days
- –
- Uptime, 90 days
- –
- Delivery, 24 h
- – median
- – p95
- Publish, 24 h
- – median
- – p95
Live
Connecting to status-probe…
Last 9030 days
- No failed checks
- 1–2 failed
- 3 or more failed
- No data
Show the days as a table
| Day (UTC) | Checks | Failed | Delivery median | Delivery p95 |
|---|
Latency, last 24 hours
- Delivery: publish sent → event received
- Publish: the HTTP request
- Failed check
No checks in the last 24 hours yet.
Show the checks as a table
| Time | Result | Connect | Publish | Delivery |
|---|
What we measure
Every five minutes, pikoman.se's own backend does what your app does, with the same Rust client library:
-
Connect. It opens a real WebSocket to Pikoman and waits for the server's
connected. The time it takes is the connect time. - Join. It joins the public channel
status-probe. - Publish. It sends one event with a random value to that channel, as a real signed request to the HTTP API. Publish is the request's round trip: how long your backend waits for the answer.
- Delivery. It waits for that event to arrive on its own socket. Delivery is the time from sending the publish request until the event is received: what your users wait for.
A check that has not finished after 10 seconds counts as failed, at the step it was on. Uptime is the share of checks that went all the way through. The median is the typical time; p95 means 95 of 100 checks were at least that fast.
The checks run from the server that hosts pikoman.se, in the same data centre region as the Pikoman API (Frankfurt). So the numbers show how the API itself is doing, not anyone's internet connection: from your users' devices, add the time it takes to reach Frankfurt.
The server was restarted recently and keeps its history in memory for now, so the longer periods only cover the time since then.