Operating status
Degraded as of . The status is computed when the site is built, once a day, from the bot's own run log. What the states mean.
- Last run
- Runs in last 24 h
- 7 of 24
- only 7 of 24 hourly runs in the last 24 h
| Source | OK | Slow | Down | Blocked | Rate-limited | Disallowed | State |
|---|---|---|---|---|---|---|---|
| TON Center API v2 | 7 | 0 | 0 | 0 | 0 | 0 | OK |
| TON Center API v3 | 7 | 0 | 0 | 0 | 0 | 0 | OK |
| TON API | 7 | 0 | 0 | 0 | 0 | 0 | OK |
| dTON (site) | 7 | 0 | 0 | 0 | 0 | 0 | OK |
| Tonscan | 7 | 0 | 0 | 0 | 0 | 0 | OK |
| Tonviewer | 7 | 0 | 0 | 0 | 0 | 0 | OK |
| TON Stat | 7 | 0 | 0 | 0 | 0 | 0 | OK |
| TON Explorer | 7 | 0 | 0 | 0 | 0 | 0 | OK |
| TON Console | 7 | 0 | 0 | 0 | 0 | 0 | OK |
What it does
Pulse sends one plain HTTP request per hour to a short list of TON APIs and explorers, then records whether the answer came back and how long it took.
What it collects
- Status of each check: up, slow, down or blocked by bot protection
- Time to full response in milliseconds
- For APIs, the masterchain block number (seqno) and how far it lags behind the freshest API in the same run
Sources
- TON Center API v2, toncenter.com/api/v2/getMasterchainInfo
- TON Center API v3, toncenter.com/api/v3/masterchainInfo
- TON API, tonapi.io/v2/blockchain/masterchain-head
- dTON (site), dton.io/
- Tonscan, tonscan.org/
- Tonviewer, tonviewer.com/
- TON Stat, tonstat.com/
- TON Explorer, explorer.toncoin.org/
- TON Console, tonconsole.com/
Method
- One GET request per target and hour, sent with the user agent shown on this page.
- Timeout 10 seconds. A response slower than 3 seconds counts as slow, not as down.
- API checks parse the JSON body, site checks read the whole HTML body. Latency is the time to the full response.
- Runs on a GitHub-hosted runner in the US, so every figure describes the path from a US data centre, not from your location.
- The checked pages are a curated list. A project is added only when it is already in the directory.
Limits and caveats
- One check per hour cannot see outages shorter than an hour, so the uptime figure is a sample, not a continuous record.
- A bot-protection page (403, 429 or 503 with a challenge) is stored as blocked. Blocked checks are left out of uptime and shown separately.
- Some services answer our user agent with a challenge. They are measured on the homepage only, or not at all.
- History keeps 90 days. Until a window is full, the page says data since its first check.
Pages this bot maintains
The list is built from the pages that show this bot's data, so it always matches the site. 8 pages at the moment.