Vendor Status Watch

← all vendors

Uphold status history

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

0incidents, last 30 days
3incidents, last 90 days
25incidents on record
Incidents per week, last 12 weeks:

How long do Uphold incidents last?

3.1 hmedian incident duration25 measured
34.9 h90th percentile1 in 10 ran longer
2.4 hmedian, major/critical only6 incidents

From 25 incidents with a vendor-posted start and resolve time. Longest on record: Service Disruption: Uphold Card — 6.0 days (2026-04-24 08:27 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 (25)

StartedIncidentStatusImpactDuration
2026-07-23 16:28 UTCService Disruption: Transactionsresolvedminor2 h 22 min
2026-07-14 16:04 UTCService Disruption: Customer Identity Verification and Transactionsresolvedminor16 min
2026-06-25 17:30 UTCTemporary Base Network unavailableresolvedmajor16 h 41 min
2026-05-29 08:43 UTCService Disruption: DAG & COQresolvednone3 d 1 h
2026-05-19 13:04 UTCService Disruption: Uphold Cardresolvedminor1 h 08 min
2026-04-24 08:27 UTCService Disruption: Uphold Cardresolvedmajor6 d 0 h
2026-03-26 23:41 UTCService Disruption: Ethereum Networkresolvedminor1 h 17 min
2026-02-03 16:50 UTCTemporary Service Issueresolvedmajor23 min
2026-02-03 16:01 UTCTemporary Service Issueresolvedcritical1 h 13 min
2025-12-18 22:21 UTCTemporary Service Issueresolvednone1 h 06 min
2025-12-18 17:31 UTCService Disruption: XRPL Networkresolvednone1 h 40 min
2025-12-06 12:23 UTCTemporary Service Disruptionresolvednone5 h 29 min
2025-11-18 12:04 UTCService Disruptionresolvedmajor3 h 32 min
2025-11-07 15:00 UTCService Disruption: Solana withdrawalsresolvednone2 h 58 min
2025-10-26 02:39 UTCDelayed Crypto Transactionsresolvedminor31 h 52 min
2025-10-20 09:50 UTCAmazon Web Services (AWS) Disruption.resolvedminor13 h 13 min
2025-10-10 22:11 UTCService Disruptionresolvedminor1 h 13 min
2025-10-07 09:52 UTCService Disruption | Deposits on TON networkresolvednone3 h 33 min
2025-10-01 18:40 UTCService Disruption | Topperresolvedmajor1 h 11 min
2025-09-30 10:30 UTCDeposits & Withdrawals via Crypto Networksresolvedminor3 h 04 min
2025-09-26 11:20 UTCStaking Rewards payout delaysresolvednone34 h 51 min
2025-09-26 10:32 UTCService Disruption | Transactions on Bittensor (TAO) networkresolvednone3 h 14 min
2025-09-14 06:56 UTCCard Transaction Issues for UK Usersresolvedminor1 h 47 min
2025-08-28 17:03 UTCSMS Delivery Issues Affecting 2FA Verificationresolvedminor16 h 56 min
2025-08-21 17:39 UTCRestricted Accessresolvedminor3 h 14 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 Uphold with the template

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

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