PrimeXBT status history
Current state: operational — “All Systems Operational” per https://status.primexbt.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do PrimeXBT incidents last?
From 5 incidents with a vendor-posted start and resolve time. Longest on record: Chart Issue on PXTrader — 2.2 h (2025-12-05 11:46 UTC). Excluded, never estimated: nothing. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.
Incidents on record (5)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-02-05 07:47 UTC | Accessibility issues | resolved | none | 0 min |
| 2025-12-11 15:41 UTC | PXTrader Trading Issue | resolved | critical | 25 min |
| 2025-12-05 11:46 UTC | Chart Issue on PXTrader | resolved | major | 2 h 15 min |
| 2025-11-28 12:47 UTC | Industry-wide market data and liquidity issue | resolved | none | 1 h 44 min |
| 2025-11-19 22:51 UTC | Outage for PXTrader Trading Platform | resolved | critical | 1 h 36 min |
Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).
Watch PrimeXBT with the template
Put this in config.json of your fork and add a WEBHOOK_URL secret:
{
"vendors": [
"primexbt"
],
"format": "auto",
"map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
"unreachable_after": 3,
"mute_maintenance": false
}
