Skip to main content
Cleverbridge logo

Is Cleverbridge Down?

No — Cleverbridge is up

Reachable from all 8 checked regions

Average response time: 668ms

Last checked · checks run every 6 hours

Official status page: https://status.cleverbridge.com

Cleverbridge uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
613ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 34 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

34-day clean streak
Sep 14: 100.00% uptime, 32 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 31 checks
Sep 18: 100.00% uptime, 31 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 42 checks
Oct 1: 100.00% uptime, 29 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 24 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

gru
1022ms
DNS 296ms TCP 2ms TLS 26ms TTFB 1008ms
iad
404ms
DNS 100ms TCP 7ms TLS 10ms TTFB 388ms
jnb
1195ms
DNS 516ms TCP 0ms TLS 7ms TTFB 1192ms
lax
441ms
DNS 62ms TCP 2ms TLS 9ms TTFB 435ms
lhr
411ms
DNS 118ms TCP 2ms TLS 16ms TTFB 376ms
nrt
866ms
DNS 263ms TCP 1ms TLS 8ms TTFB 862ms
ord
433ms
DNS 124ms TCP 1ms TLS 11ms TTFB 425ms
sin
572ms
DNS 158ms TCP 1ms TLS 7ms TTFB 562ms

What Cleverbridge does

Cleverbridge runs online checkout and subscription billing for software and SaaS companies, handling the order, the payment, tax and the recurring renewal on the vendor's behalf. Customers usually meet it as the checkout that opens from a software vendor's own website, so the Cleverbridge name may be unfamiliar even to people whose purchase depends on it.

What an outage looks like

Checkout fails or never loads after a customer clicks buy, so the vendor's marketing site looks entirely healthy while no order can be completed. Payment confirmations and licence keys stop arriving. Subscription renewals, upgrades and cancellations can fail on their own, separately from new orders. Applications calling the REST or GraphQL APIs receive errors or timeouts.

What to do about it

Read status.cleverbridge.com, which reports Order Process, REST API, GraphQL API and Subscription Management as separate components, each with uptime and response time. Match the symptom to the row. If only Subscription Management is affected, new purchases still complete while renewals and plan changes do not. Avoid resubmitting a payment that returned no confirmation until you have checked whether the order was recorded.

Is it down for everyone, or just you?

If this page says Cleverbridge is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Stripe
Stripe
Paddle
Paddle
Adyen
Adyen
Recurly
Recurly

Cleverbridge outage FAQ

I paid but never got a confirmation or licence key. Did the payment go through?
Treat it as unresolved rather than failed, and do not pay again immediately. Cleverbridge reports Order Process separately from its APIs, so an order can be recorded while the message confirming it is delayed. Check your card or bank statement for a pending charge and contact the software vendor's support with the time of the attempt. Paying a second time is the action most likely to create a duplicate order.
The vendor's website works fine, so why can I not buy anything?
That combination is normal during a Cleverbridge incident. The vendor's marketing pages are served from their own infrastructure, while the checkout, payment and licence delivery run on Cleverbridge. The site being reachable says nothing about whether an order can complete. Check status.cleverbridge.com rather than the vendor's own status page, which may correctly report all of its own systems as healthy.
Will my subscription be cancelled if a renewal fails during an outage?
A failed renewal attempt during an incident is a billing retry situation rather than an immediate cancellation, and Cleverbridge reports Subscription Management as its own component precisely because it moves independently of new orders. Cleverbridge does not publish retry timings for every plan, so if a renewal date falls inside an incident window, confirm the outcome with the vendor rather than assuming either result.
Is this Cleverbridge or my card being declined?
Compare scope. A declined card produces a specific decline message and affects one payment method, and switching cards usually works. A Cleverbridge incident affects the checkout itself, so the page fails to load, times out or errors before any card detail is judged. If the checkout never reaches the point of asking for payment, the problem is upstream of your card.
Does a Cleverbridge outage stop the software I already bought from working?
Generally no. Cleverbridge handles the purchase and the billing relationship, not the running product, so software already installed and licensed keeps working through an incident. What stops is buying, renewing, upgrading and receiving new licence keys. Where a product checks its licence against the vendor rather than against Cleverbridge, that check is the vendor's system and unaffected.

How we measure this

  • We request Cleverbridge's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Cleverbridge publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Cleverbridge goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required