Site status
Is PolyConsensus working right now, and how fresh is its data? Updated every minute.
All systems normal
As of 13:41 UTC
Right now
- WebsiteNormal · as of 13:34 UTC
The site is up and answering quickly.
- Home pageanswered in 0.4 s
- Server checkanswered in 0.3 s
Whether polyconsensus.com loads. Checked every minute from a server in another country, so outages show here even when the site's own server is down.
- Market dataNormal · as of 13:40 UTC
Up to date: data as of just now.
- Prices refreshedjust now
- Traders' trades indexedup to date (0 sec behind the blockchain)
- Lists fully recountednot since the last restart
- Closed markets watchchecked 32 sec ago; closed markets show within about 1 min
How fresh the numbers on the site are: prices, the trades of the tracked traders, and the market lists.
- Background workerNormal · as of 13:40 UTC
Running: last checked in just now.
The background program that reads the blockchain and Polymarket and keeps the site's data current.
- Bots APINormal · as of 13:41 UTC
Working: last bot report just now.
Trading bots connected to the site send a status report about once a minute. This shows that reports are arriving.
Live data
Delayed · as of 13:41 UTCIs new data arriving in real time? Each line is measured on the server at the time shown and refreshed every minute.
- Newest trade seen5 s ago
- Latest position update19 s ago
- Trade to market cardtypically 1 s, 95 % within 8 s (last 10 min)
- Prices refreshed2 s ago
- Large trades list updated53 s ago
- Background worker heartbeat5 s ago
- Website responsiveness1 freeze over 1 s in the last 10 min, longest pause 1 s
- Traders tracked2,381
- Open markets with a consensusunknown
Uptime
100.00 % (30 days) · 100.00 % (90 days)
Tap a day to see its uptime. Grey = no checks that day.
Incidents (last 30 days)
No outages or slow periods in the last 30 days.
How this page works
- A server in Germany, outside the site's own server, loads the site every minute and reports what it saw every 5 minutes. When the site is down it keeps the results and sends them once it is back, so outages appear here afterwards too.
- Two or more failed checks in a row (2 minutes or more) count as an outage; answers slower than 5 seconds for 2 minutes or more count as slow. A single failed check lowers the day's uptime but is not listed.
- Market data: prices are refreshed every few seconds and new trades of the tracked traders are read from the blockchain within about 30 seconds. The full recount of every list runs about every 75 minutes; holders and prices change live in between.
- The same information as JSON: /api/status (see the API docs). Last report from the outside checker: 13:34 UTC.