Uphold status history
Current state: operational — “All Systems Operational” per https://status.uphold.com (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.
How long do Uphold incidents last?
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)
| Started | Incident | Status | Impact | Duration |
|---|---|---|---|---|
| 2026-07-23 16:28 UTC | Service Disruption: Transactions | resolved | minor | 2 h 22 min |
| 2026-07-14 16:04 UTC | Service Disruption: Customer Identity Verification and Transactions | resolved | minor | 16 min |
| 2026-06-25 17:30 UTC | Temporary Base Network unavailable | resolved | major | 16 h 41 min |
| 2026-05-29 08:43 UTC | Service Disruption: DAG & COQ | resolved | none | 3 d 1 h |
| 2026-05-19 13:04 UTC | Service Disruption: Uphold Card | resolved | minor | 1 h 08 min |
| 2026-04-24 08:27 UTC | Service Disruption: Uphold Card | resolved | major | 6 d 0 h |
| 2026-03-26 23:41 UTC | Service Disruption: Ethereum Network | resolved | minor | 1 h 17 min |
| 2026-02-03 16:50 UTC | Temporary Service Issue | resolved | major | 23 min |
| 2026-02-03 16:01 UTC | Temporary Service Issue | resolved | critical | 1 h 13 min |
| 2025-12-18 22:21 UTC | Temporary Service Issue | resolved | none | 1 h 06 min |
| 2025-12-18 17:31 UTC | Service Disruption: XRPL Network | resolved | none | 1 h 40 min |
| 2025-12-06 12:23 UTC | Temporary Service Disruption | resolved | none | 5 h 29 min |
| 2025-11-18 12:04 UTC | Service Disruption | resolved | major | 3 h 32 min |
| 2025-11-07 15:00 UTC | Service Disruption: Solana withdrawals | resolved | none | 2 h 58 min |
| 2025-10-26 02:39 UTC | Delayed Crypto Transactions | resolved | minor | 31 h 52 min |
| 2025-10-20 09:50 UTC | Amazon Web Services (AWS) Disruption. | resolved | minor | 13 h 13 min |
| 2025-10-10 22:11 UTC | Service Disruption | resolved | minor | 1 h 13 min |
| 2025-10-07 09:52 UTC | Service Disruption | Deposits on TON network | resolved | none | 3 h 33 min |
| 2025-10-01 18:40 UTC | Service Disruption | Topper | resolved | major | 1 h 11 min |
| 2025-09-30 10:30 UTC | Deposits & Withdrawals via Crypto Networks | resolved | minor | 3 h 04 min |
| 2025-09-26 11:20 UTC | Staking Rewards payout delays | resolved | none | 34 h 51 min |
| 2025-09-26 10:32 UTC | Service Disruption | Transactions on Bittensor (TAO) network | resolved | none | 3 h 14 min |
| 2025-09-14 06:56 UTC | Card Transaction Issues for UK Users | resolved | minor | 1 h 47 min |
| 2025-08-28 17:03 UTC | SMS Delivery Issues Affecting 2FA Verification | resolved | minor | 16 h 56 min |
| 2025-08-21 17:39 UTC | Restricted Access | resolved | minor | 3 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
}