Per-consumer backlog on JetStream. A consumer falling behind here means data is queued and delayed, not lost or wrong — but the longer it sits, the staler live charts and API responses get for that feed. Auto-refreshes every 15s.
Stream
Consumer
Pending
Delivered Seq
Ack Floor Seq
Status
Telegram Bot
@PipDataRobot's own health: whether it can reach Telegram through the relay, its outgoing-message backlog, and every alert / watchlist event / scheduled report of the last 24 h followed through to delivery. Lost = recorded but never queued (must be 0). Late = delivered more than 10 min after it fired.
Kind (24 h)
Fired
Lost
Failed
Late
p95 delivery
Create API Key
Requests per minute
Requests per day
Uncheck all to block data access (key still valid for /v1/config)
Customer Dashboard Access (optional)
If provided, the customer can log in at client.pipdata.net with these credentials.
Manage Dashboard Access
Loading…
Set or reset customer dashboard credentials. This allows the customer to log in at client.pipdata.net.
Save your API key
⚠ This key will NOT be shown again. Copy it now.
Store it securely. If lost, create a new key and deactivate this one.