Crypto Payment Gateway Uptime 2026: We Audited 9
We audited nine crypto payment gateway status pages on 2 October 2026. Four publish one, two publish an uptime figure, and none promise an SLA.
Key Takeaways
- Four of nine gateways publish a status page; two publish a number. CoinGate and BlockBee report uptime percentages. BitPay and Coinbase Commerce publish incident histories with no percentage anywhere. NOWPayments, Plisio, Cryptomus and OxaPay publish nothing.
- Not one of the nine offers an uptime SLA, and two disclaim it in writing. CoinGate's merchant terms say operation will not necessarily be “uninterrupted or error free”; BitPay's say the services may not be “available, uninterrupted or secure”.
- Coinbase Commerce has its own status page, and it has been quiet for 196 days. Its last published incident opened 20 March 2026. Over the 50 days to 1 October the main Coinbase page published 50 incidents.
- Our measurement: BlockBee's monitors recorded a correlated dip across six chains on 16 September 2026 while its status feed published nothing. Bitcoin fell to 99.645% and Litecoin to 99.441%; its 30-day event feed returns zero entries.
- CoinGate's API went down on three consecutive days — 27, 28 and 29 September 2026 — and its 90-day API uptime still reads 99.990%, because that is only 13 minutes out of 129,600.
Table of Contents
- Which of the nine publish a status page
- A 200 is not a status page
- The only two uptime numbers, in minutes
- CoinGate's API went down three days running
- BlockBee's monitors saw 16 September; its feed did not
- Coinbase Commerce's page has been quiet for 196 days
- What the status page does not cover
- Nobody owes you uptime: what the terms say
- What to monitor yourself
- FAQ
Which of the nine publish a status page
Your checkout stops taking payments and you do not know whose fault it is. The first thing you want is the gateway's status page, and for five of the nine processors we audited there is not one to open — so you are left refreshing your own logs and guessing. Crypto payment gateway uptime is the one number in this market that nobody is obliged to publish, so on 2 October 2026 we went looking for what each processor actually reports: we probed every status-page hostname pattern we could think of for nine gateways, pulled the raw status APIs behind the four that have one, and read the merchant terms to see what, if anything, is promised.
Four publish a status page. Two publish a percentage. None publishes an SLA. Here is the full audit.
The “none found” rows are a negative claim, so they deserve a method. For each we tried the subdomain, the path (nowpayments.io/status returns 404), and the three big hosted-status vendors' own subdomains, then checked each homepage for an uptime claim. NOWPayments advertises “30 Million+ finished transactions per month” with no reliability figure anywhere; OxaPay's terms say only that “The Services are available 24/7” while reserving the right to suspend them “without prior notice or compensation”.
BTCPay Server is a fair exception rather than an omission: it is software you run, so the only uptime that exists is your server's. The ceiling is yours to raise, as is the outage.
A 200 is not a status page
Checking whether a status page exists sounds like a job for a status code, and it is not. Every hosted-status vendor answers HTTP 200 for a subdomain that was never registered, serving its own marketing page instead of a 404. Go by the response code and you will conclude that four gateways with no status page have one.
The giveaway is that the bytes are identical for every brand:
The last two rows are the nastiest, because the path looks like an API and the response is a web page: the document opens with a HTML doctype and the string id="magnolia", which is Atlassian's own marketing site. A check that asks only whether the request succeeded will record a healthy Statuspage API for a gateway that has never had one.
Parse the body, not the status line. A genuine Atlassian Statuspage answers /api/v2/status.json with a JSON object containing a page key whose name is the company. A genuine Better Stack page contains per-component uptime text. A genuine UptimeRobot page carries psp- prefixed CSS classes and an api/getMonitorList/ endpoint. If two brands return byte-identical responses, neither has a status page.
The only two uptime numbers, in minutes
A percentage is a bad unit for a decision. The gap between 99.9% and 99.99% reads like rounding and is the difference between 8.8 hours of outage a year and 53 minutes. So here is every published crypto payment gateway uptime figure we found, converted into the minutes it allows over the 90-day window the pages display — 129,600 of them.
Both are good numbers, and the spread inside each gateway is wider than the gap between them. BlockBee's best monitor is 48 times more reliable than its worst, and the worst is the EVM endpoint — the one most merchants depend on, because it carries Ethereum and every ERC-20 stablecoin. An average across monitors flatters it. Read the row you will actually call.
For context, what each extra nine is worth — the table to keep when a vendor quotes a figure at you:
CoinGate's API went down three days running
A high percentage and a bad week are compatible. Its status page reported “All services are online” when we read it at 18:49 UTC on 2 October 2026, with the API at 99.990% over the window. Scroll to the incident list and the last week of September looks like this:
Three API outages on three consecutive days, each short enough that 13 minutes of total budget absorbed all of them. That is the honest reading of 99.990%: not a promise of smoothness, a statement that the rough patches were brief. If your checkout retried, you never noticed. If it did not, you lost three days of invoices in bursts.
CoinGate is also the only gateway here that breaks out the components a merchant cares about — Invoice, Embed, Payout Link, Dashboard, Verify and Claim each get a row and a number — and its API carries the lowest figure of the eight. That is a vendor measuring itself where it hurts rather than monitoring its marketing site and calling that uptime.
BlockBee's monitors saw 16 September; its feed did not
BlockBee's status page is the most and least transparent here at once. Fetched without a browser it renders nothing — the HTML carries “Loading...” and “There was an error while fetching the data” and not one figure. Behind it, its UptimeRobot endpoints return 90 days of daily ratios for eight monitors, finer-grained data than any other gateway here publishes.
We pulled all 720 daily ratios for 5 July to 2 October 2026. One date stands out, and it is in no incident report.
Six chain monitors dipped on the same day, and for five it is the only blemish in three months. A correlated dip across six independent blockchains is not six blockchain problems; it is one problem in whatever those monitors share. BlockBee's event feed, queried for the 30 days to 2 October 2026, returns a count of zero, and the page says “There are no updates in the last 7 days.”
This is the distinction worth taking away from the whole audit. BlockBee's monitoring recorded the 16 September event and its communications did not, so a merchant who checked the status page that week saw green and a merchant who queried the data saw a correlated six-chain dip. Neither is lying. A status page reports what someone decided to announce; the monitor data reports what the probes saw. Where both exist, read the second.
Coinbase Commerce's page has been quiet for 196 days
If you integrate Coinbase Commerce and want its status, the page you probably open is status.coinbase.com. That is the wrong one. There is a separate Coinbase Commerce status page with its own 22 components, including Checkouts, API, Dashboard, Point of Sale, Withdrawals and Coinbase Payments — the things a merchant integration actually touches. The two pages tell very different stories.
Same company, same status-page vendor, and one feed is 38 times denser than the other. The main page's recent incidents are dominated by things no merchant cares about — “Prediction Markets Trading”, “Derivatives Positions” — which is exactly why the Commerce page exists. But that page has published nothing since 20 March 2026, 196 days before we read it.
That last incident is the longest in the audit. It is titled only “Partial Interruption”, carries an impact of “none”, and the gap between its creation and resolution timestamps is 187,013 minutes — 129.9 days. We do not read that as four months of broken checkouts; a resolution timestamp that far out usually means nobody closed the ticket. But it is the most recent thing a merchant evaluating Coinbase Commerce will find, and it is uninformative in both directions.
Read that column honestly: it is a sample capped at 50, so it cannot tell you 2021 was quieter than 2024. What it can tell you is that the rate of publication fell off a cliff this year, from 11 or 12 a year to 2. Either Coinbase Commerce got dramatically more reliable in 2026, or it stopped posting. The main Coinbase page's 50-incidents-in-50-days suggests which.
What the status page does not cover
A status page is a list of things the vendor chose to watch, and the gaps are where your outage will happen. BitPay has 54 components, mostly one coin on one network; BlockBee has eight, every one an API endpoint. Neither watches the thing you would most want watched.
Not one of the four monitors webhook delivery, and webhook delivery is the failure that costs you money quietly. A gateway whose invoice API is up, whose checkout renders, and whose callbacks have stopped arriving looks perfectly green on all four of these pages while your orders sit unpaid in your own database. We compared how the same gateways handle callback retries in our webhook retry comparison, and the short version is that the retry schedule is undocumented almost everywhere it matters.
BitPay's 54 components flatter it. The list is largely “API Invoice - BTC”, “API Invoice - BCH” and the same again for the sandbox, plus a row per settlement currency — granular where granularity is cheap. Its status page contains no percentage figure of any kind — we searched the rendered HTML and found zero — so you can see that something broke in February but not how much of the year was clean.
BitPay's incident history is the deepest here and the most useful for pattern-spotting. Its 50 most recent entries stretch back to 20 October 2020, 2,136 days, which by itself says the publication rate is low. The 2026 entries are almost all one shape:
Four of the five are a single chain being switched off, not the gateway failing — a category of outage the percentage-publishing gateways hide completely. If BitPay disables BASE for 18.7 days, a merchant selling USDC on BASE is fully down while “the gateway” is up. That is the outage that actually bites in this market, which is why we treat it separately when comparing which chains to accept.
Nobody owes you uptime: what the terms say
Search for these gateways' reliability and you will find SLA figures quoted with confidence. One widely-ranking 2026 comparison gives BitPay a “99.9% SLA”, CoinsPaid a “99.95% uptime SLA” and CoinGate a “documented 99.9% SLA”. Another gives CoinGate 99.5%. Neither cites a source, they contradict each other, and we found none of those figures in any first-party document.
What the first-party documents say is the opposite. These are the operative sentences, quoted from the merchant agreements:
So no crypto payment gateway in this audit sells you availability. There is no credit to claim, no threshold to hold anyone to, and no contractual difference between a gateway that was up all year and one down for a week. That is not unusual — read CoinGate's merchant terms and BitPay's terms of use side by side and they are the same disclaimer in different typography — but it changes what a published uptime figure is for. It is evidence about the past, voluntarily disclosed. It is not a commitment.
Which makes the four that publish anything more interesting, not less: a vendor that puts 99.990% on a public page and names its own API as its worst component has chosen to be measurable when nothing compels it. That is the same signal we found in the rate-limit audit and the sandbox comparison: the gateways that document one unglamorous thing tend to document the others too.
What to monitor yourself
Since nobody owes you uptime and five of nine report none, measure the two calls your revenue depends on. Not the homepage, not the docs site — create an invoice, then read its status.
Poll two endpoints per gateway on a fixed interval from outside your own network: an authenticated invoice-create and an authenticated invoice-read, using a real API key against a small fixed amount. Record latency alongside the status code, because degradation shows up as slowness long before it shows up as an error. Alert on two consecutive failures rather than one, and keep the interval inside the rate limit — at a ten-second poll you are spending six requests a minute per probe, which is fine against CoinGate's 200 but worth checking against a gateway that publishes no limit at all.
Then monitor your own webhook endpoint for silence. None of the four status pages watches callback delivery, so this is the gap you have to cover yourself. An alert that fires when no callback has arrived in longer than your normal quiet period catches the failure mode that every page in this article reports as green, and it is the one that leaves customers paid and orders unfulfilled. If you are already chasing that symptom, our guide to payments that never arrive walks through the other causes.
And keep the data, because you will be the only one who has it. Six months of your own latency figures beat any vendor percentage: measured at your egress, against your key, on the endpoints you call. It is also the only way to win an argument about whose outage it was.
- Crypto Payment Gateway Rate Limits 2026: We Checked 9
- Crypto Gateway Webhooks 2026: Retry Rules Compared
- Crypto Payment Gateway Sandbox 2026: We Tested 9
- Crypto Payout Schedules 2026: When Gateways Actually Pay
- Crypto Invoice Expiry 2026: The 15-Minute Window
- Crypto Pay API 2026: A Developer Comparison
Weigh reliability reporting before you integrate
We track fees, settlement timing, supported chains, invoice windows, webhook retries and rate limits for every processor in the directory, so whether a gateway reports its uptime at all is one more column to weigh before wiring anything. NOWPayments publishes neither, which is the norm here rather than the exception.
Compare Crypto Payment Gateways →FAQ
Which crypto payment gateways publish a status page?
Four of the nine we audited on 2 October 2026: CoinGate (status.coingate.com, Better Stack), BitPay (status.bitpay.com, Atlassian Statuspage), Coinbase Commerce (status.commerce.coinbase.com, separate from the main Coinbase page) and BlockBee (status.blockbee.io, UptimeRobot). NOWPayments, Plisio, Cryptomus and OxaPay publish nothing we could find, and BTCPay Server is self-hosted, so there is no vendor service to report on.
What uptime do crypto payment gateways actually report?
Only two of the nine publish a percentage. CoinGate reports per-component figures over a 90-day window: 99.990% for the API, 99.988% for the homepage, 99.996% for Embed and 100% for Invoice, Dashboard, Claim, Verify and Payout Link. BlockBee's daily ratios average 99.9908% across its eight monitors over the 90 days to 2 October 2026. BitPay and Coinbase Commerce publish incident histories but no percentage at all.
Does any crypto payment gateway offer an uptime SLA?
None of the nine publishes one, and two disclaim the opposite. CoinGate's Merchant Terms of Services section 6.5 says it does not warrant that operation of the CoinGate System will be uninterrupted or error free. BitPay's Terms of Use section 16 says it does not warrant the acceptance services will be available, uninterrupted or secure at any particular time or location. The 99.9% and 99.95% SLA figures circulating in comparison articles appear in neither document.
Is 99.99% uptime good for a payment gateway?
It is 52.6 minutes of downtime a year, or 13 minutes in a 90-day window: a reasonable number for a crypto gateway and a poor one for a card processor. The figure matters less than its scope, because 99.99% on a homepage monitor tells you nothing about the invoice API your checkout actually calls.
Why does BlockBee's status page look empty?
Because it renders entirely in JavaScript. Fetched without a browser, status.blockbee.io returns a shell containing the strings Loading and There was an error while fetching the data, and no figures. The real data sits behind its UptimeRobot endpoints, which return 90 days of daily ratios per monitor. Checking a status page with curl and seeing nothing establishes neither that the service is fine nor that the page is broken.
Has Coinbase Commerce had any outages in 2026?
Its status page publishes two incidents dated 2026, the most recent a Partial Interruption opened on 20 March 2026 and marked resolved 129.9 days later. Nothing has appeared on that page in the 196 days since, while the main Coinbase status page published 50 incidents in 50 days. The quiet reflects what the Commerce page reports, not what the wider Coinbase estate experienced.
What should I monitor yourself?
The two calls your checkout depends on: creating an invoice and reading its status. Probe them with your own API key from outside your network, record latency as well as the status code, and alert on consecutive failures rather than single ones. Watch your webhook endpoint for silence too, because a gateway that accepts invoices and then stops delivering callbacks shows green on every status page in this article.
Affiliate disclosure: payyd.co earns a commission on sign-ups made through our /go/ links, including the NOWPayments link above. No gateway supplied, reviewed or saw these findings before publication. Method: on 2 October 2026 we probed four status-page hostname patterns for each of nine gateways, then pulled the status APIs behind the four that have one — Statuspage endpoints for BitPay and Coinbase Commerce, the rendered Better Stack page for CoinGate, UptimeRobot monitor-list and event-feed endpoints for BlockBee. Every uptime percentage is the vendor's own figure; the conversions into minutes are ours, against a 129,600-minute window. The six-chain dip on 16 September 2026 is our reading of BlockBee's 720 daily ratios, not an incident BlockBee has reported. Incident counts come from a feed capped at 50 entries, so they are a sample, not totals. Terms quotations are verbatim. We did not attempt to cause an outage on any gateway. Last updated 2 October 2026.