On 10 October 2026 confirmtx.net did not load. Four attempts spread across the day returned HTTP 522, the Cloudflare code for an origin server that is not answering. Its Trustpilot page carries a notice that reviews are closed because the company's website has closed, above three one star reviews from people who paid and got nothing. The terms the listicles still quote, free under 250 bytes, $5 above, confirmation within twelve hours, describe a service we could not reach. If you have a payment pending with it, treat the money as gone and fix the transaction yourself; the fix is usually about a hundred sats.
Search for a Bitcoin accelerator and ConfirmTX appears in most of the top ten lists, usually with the same three facts: free for transactions under 250 bytes, five dollars flat above that, and confirmation within twelve hours. Three impressions for confirmtx accelerator reached this site last month with no page to land on, so we went and looked. This is what we found, in the order we found it.
The site on 10 October 2026
We requested confirmtx.net four times across the day, with the same browser identification an ordinary visitor would send, waiting twenty seconds between attempts and more between batches.
| Attempt | Response | Meaning |
|---|---|---|
| Morning, first | HTTP 522 | Cloudflare could not get a reply from the origin server |
| Morning, second | HTTP 522 | Same |
| Midday, two attempts | HTTP 522, HTTP 522 | Same, with Cloudflare's Retry-After header asking for two minutes |
| Response headers | Server: cloudflare | The domain is still proxied; the machine behind it is not responding |
A 522 is specific. It is not a 404, which would mean the page moved, and not a 403, which would mean we were blocked. It means Cloudflare still answers for the domain and the server it forwards to has stopped. A site can show this for an hour during maintenance. It can also show it for years after an operator walks away, because the Cloudflare proxy keeps answering long after the server behind it is switched off.
We cannot tell you which this is from one day. We can tell you what the other evidence says.
What the people who paid said
Trustpilot's page for confirmtx.net has three reviews, every one of them one star, and no reviews in the last twelve months. Above them is a notice: it is no longer possible to leave a review because the company's website has closed. The reviews themselves are from 2023.
- June 2023. A $17 payment to accelerate a transaction. Twenty days later the transaction was still unconfirmed.
- September 2023. $17 sent for a promised confirmation within 24 hours, then a request for more money because the transaction was larger, then no response to a refund request.
- September 2023. Paid three days earlier, transaction still stuck.
Two details in those reviews do not match the listicle description. The price people report paying is $17, not $5, and the promise they report is 24 hours, not 12. Either the terms changed over time or the quoted terms were never the real ones. Either way, the pages ranking for this name in 2026 are describing a price list that the service's own customers did not see in 2023.
Older reports say the same thing
A NewsBTC article from the service's early years reported that ConfirmTX was not processing requests despite receiving payments. The original 2017 BitcoinTalk announcement was for confirmtx.com, free up to 400 bytes. The .net domain, the 250 byte threshold and the $5 fee came later. The one constant across every source is people paying and waiting.
Fix it yourself for about a hundred sats
Paste the transaction ID. We show the shortfall to the next block in sats and which bump fixes it. No account, no payment.
The advertised terms, priced against reality
Suppose the service were up and the listicle terms were accurate. Free under 250 bytes, $5 flat above. What would that buy?
A normal single input, two output transaction is about 140 virtual bytes. So the typical stuck transaction would fall in the free tier, and the free tier of a service like this is a rebroadcast, which does nothing for a transaction the network already holds. Every node that has your transaction ignores a second copy. That is not an opinion about ConfirmTX; it is how Bitcoin nodes work, and it is why rebroadcast accelerators do nothing for a propagated transaction.
Above 250 bytes, $5 is about 6,000 sats at the price on the day this was written. The transaction it would be bought for, if it is like most stuck transactions, pays about 0.15 sat/vB and needs lifting to around 1 sat/vB. For a 300 byte transaction that is roughly 255 sats. The flat fee is about twenty four times the real shortfall, and unlike a fee bump it goes to the service, not to a miner, so the transaction's fee rate does not rise by a single satoshi.
Against our six red flags
We keep a list of six signs that separate a working accelerator from an advance fee pattern. Run ConfirmTX against it using only the public record.
| Flag | Finding |
|---|---|
| Asks for a seed phrase or key | No report of this. It asked for a txid and a payment |
| Hides who gets paid and what for | No company name, address or named pool in any source we found; our earlier survey noted it described its infrastructure as powered by a third party tool brand |
| Guarantees a fixed time | Twelve hours in the listicles, 24 hours in the reviews. Nobody can promise a block |
| Wall of green badges, no detail | Cannot check today; the site does not load |
| Claims rebroadcasting fixes everything | The free tier is a rebroadcast sold as acceleration |
| Nothing verifiable | No public record of accelerations, no named pools, no reachable server |
Four flags out of six from the public record alone, before the server went quiet. For contrast, the mempool.space Accelerator names fifteen pools, publishes every job it takes and shows its price before payment, and ViaBTC at least runs the pool it promises to use.
If you already paid ConfirmTX
- Assume the payment is gone. Accelerator payments are made in crypto to an address the service controls. There is no chargeback. A refund request to a server that returns 522 will not be read.
- Check whether the transaction confirmed anyway. Many do, by chance, within a day or two of a panic payment, which is how services like this collect good reviews. Look it up on any explorer.
- If it is still pending, bump it. You sent it: RBF from your wallet. You received it: CPFP from yours. The cost is the shortfall, which the checker shows in sats.
- If it is not found anywhere, it was dropped or never broadcast. Push the raw hex back to the network, free, or send a new payment at a clearing rate.
- If you cannot bump and it cannot wait, use a service you can verify, and read its refund rule before paying a second time.
Why it is still in the listicles
Because the listicles are not maintained. AMBCrypto's list was refreshed in May 2025 and still carries the 250 byte and $5 terms. A 2026 press release on a wire service promotes the name in the present tense. Mudrex's list dates from 2021. None of them say when the author last opened the site. We rank the same category by whether each service answers today, and on 10 October 2026 this one did not. The full status table is in our ranked answer to which accelerator is best, alongside the 360 Bitcoin Accelerator, whose free tool is switched off, and BTC.com, Poolin and F2Pool, which are gone outright.
We will keep checking
A single day of 522s is strong evidence, not proof of permanent closure. We re-check every accelerator in our comparison periodically and update the status tables when something changes. If confirmtx.net comes back, this page will say so, with the date, and we will price its real terms the same way we price everyone else's. Until then, a service that cannot be reached cannot be recommended, whatever position it holds in a list written years ago.
The bottom line
ConfirmTX, on the day we looked, was a Cloudflare error page with a Trustpilot obituary behind it. Its advertised fee was a multiple of the real cost of fixing a stuck transaction even when it worked, and its customers reported paying more than the advertised fee for nothing. The listicles will keep ranking it until someone opens the site. Open the site. Then bump the fee yourself.
The accelerator that tells you when not to pay
Twenty named nodes, every answer shown, and a verdict that says whether anyone at all should be paid. Free, no account.
Frequently asked questions
Is ConfirmTX still working?
Not on 10 October 2026. Four requests to confirmtx.net spread across the day each returned HTTP 522, Cloudflare's code for an origin server that is not responding. Its Trustpilot page carries a notice that the company's website has closed. We will update this page if the site returns.
Is ConfirmTX a scam?
We cannot say what the operator intended. We can say that its three Trustpilot reviews are all one star and describe payments of $17 with no confirmation and no reply to refund requests, that an earlier news report described it taking payments without processing requests, that it names no company, address or mining pool, and that its site did not answer on any check we made. Treat money sent to it as gone.
How much does ConfirmTX cost?
The listicles say free for transactions under 250 bytes and a flat $5 above that, with confirmation promised within twelve hours. Its reviewers report paying $17 and being promised 24 hours. We could not confirm either, because the site did not load.
I paid ConfirmTX and my transaction is still stuck. What now?
Check an explorer first; many transactions confirm by chance within a day or two. If it is still unconfirmed, bump the fee yourself: RBF from the sending wallet, or CPFP from the receiving wallet, for roughly the shortfall in sats. If no explorer can find it, push the raw hex back to the network for free. Do not send a second payment to a site that does not answer.
What is a 522 error on an accelerator site?
Cloudflare returns 522 when it can reach the domain but the server behind it does not reply. It is not a block and not a moved page. A site can show it briefly during maintenance, or indefinitely after the operator shuts the server down while the Cloudflare proxy keeps answering for the domain.
What should I use instead of ConfirmTX?
First find out whether the transaction is actually stuck; most are already in line for the next block. If the fee is genuinely too low, bump it from your own wallet for about a hundred sats. If nobody can bump it and it cannot wait, use a service with named pools, a public record and a price shown before payment, such as the mempool.space Accelerator, and read its refund rule first.