Status
How current btcintel is
Each part has its own light, set by the rule written under it, with its numbers and the time of the reading. Read at . There is no light for the whole: one part can be down while the others work.
- green: working
- amber: working, but behind or partly failing
- red: not working
- grey: not known, or off on this deployment
Node and indexok
- node
- 972,920 · answering
- index
- 972,920
- lag
- 0 blocks
- read at
- 2026-10-24 12:49:39 UTC
Green while the node answers and the index is at most 2 blocks behind it. Amber from 3 blocks behind. Red when the node does not answer, or when the index stays more than 3 blocks behind for 10 minutes (the lag alert). From /v1/status and /metrics.
Mempool engineok
- state
- synced with the node
- transactions
- 54,477
- last event from the node
- 0 s before the reading
- read at
- 2026-10-24 12:49:39 UTC
Green while it is synced and hears from the node. Amber while it rebuilds its mirror after a start. Red when it has heard nothing from the node for 5 minutes. From /v1/status.
Live stream and relayok
- stream clients
- 9
- relay connections
- 0
- relay mode
- normal
- Community writes
- on
Green while the stream and the relay answer. Amber while the relay is in attack mode, asking more proof of work, or while the stream is full. Red when either does not answer. Community writes on or off is a setting, so it never changes the light. From /metrics, /v1/status and a probe of each.
Sourcesok
| source | cadence | checked | content from | records |
|---|---|---|---|---|
| off: btcintel rules | push only | no check recorded yet | never fetched | — |
| not known: MISP Galaxy: ransomware | weekly | no check recorded yet | 2,179 | |
| not known: MISP Galaxy: threat actors | weekly | no check recorded yet | 1,097 | |
| not known: MITRE ATT&CK Enterprise | weekly | no check recorded yet | 1,634 | |
| ok: OFAC SDN List | every 6 h | 533 | ||
| ok: bitcoin-data mining pools | daily | 149 | ||
| not known: mempool mining pools | daily | no check recorded yet | 171 | |
| ok: Ransomwhere | daily | 30,088 |
Grey: no check recorded yet. It is known from the source's next check.
Green while every source was checked within twice its cadence and its last check worked. Amber when one or more were not; the table names them. Red when the scheduler is off, or no source was checked within twice its cadence. “Checked” is the last time btcintel asked the source; “content from” is when the source last changed. A late source's claims are not wrong: they are as of its content's date. From /v1/sources.