Vendor Status Watch

← all vendors

CoinJar status history

Current state: operational — “All Systems Operational” per https://status.coinjar.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

0incidents, last 30 days
1incidents, last 90 days
4incidents on record

How long do CoinJar incidents last?

93 minmedian incident duration4 measured
117 min90th percentile1 in 10 ran longer
72 minmedian, major/critical only3 incidents

From 4 incidents with a vendor-posted start and resolve time. Longest on record: Incident: Delays With Cryptocurrency - ADA, DOGE, ETH, ERC-20, SOL, and SPL tokens — 117 min (2026-06-04 01:58 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 (4)

StartedIncidentStatusImpactDuration
2026-06-23 07:16 UTCDelays with Identity Verification (CoinJar Australia)resolvedmajor1 h 12 min
2026-06-04 01:58 UTCIncident: Delays With Cryptocurrency - ADA, DOGE, ETH, ERC-20, SOL, and SPL tokensresolvedmajor1 h 57 min
2025-12-23 22:55 UTCUnplanned CoinJar Exchange Outageresolvedmajor56 min
2025-08-26 07:01 UTCIncident: Delays With SUI Deposits and Withdrawalsresolvedminor1 h 55 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 CoinJar with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "coinjar"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}