Is Sezzle Down?

No — Sezzle is up

Reachable from all 8 checked regions

Average response time: 543ms

Last checked 53 minutes ago · checks run every 6 hours

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

Sezzle uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

700ms

Avg response, 30 days

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

30-day history

27-day clean streak

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.

ams

233ms

DNS 44ms TCP 2ms TLS 6ms TTFB 224ms

arn

571ms

DNS 77ms TCP 1ms TLS 5ms TTFB 561ms

cdg

66ms

DNS 43ms TCP 2ms TLS 6ms TTFB 57ms

ord

91ms

DNS 75ms TCP 1ms TLS 3ms TTFB 84ms

sin

1532ms

DNS 293ms TCP 137ms TLS 140ms TTFB 891ms

sjc

102ms

DNS 80ms TCP 1ms TLS 4ms TTFB 94ms

syd

1380ms

DNS 292ms TCP 136ms TLS 140ms TTFB 793ms

yyz

375ms

DNS 76ms TCP 14ms TLS 16ms TTFB 316ms

What Sezzle does

Sezzle is a buy now, pay later service that splits a purchase into four interest-free instalments over six weeks. Shoppers choose it at checkout on participating online stores, and merchants connect to it through Sezzle's gateway and APIs. Because it sits inside other companies' checkouts, a Sezzle outage often looks like a problem with the store rather than with Sezzle.

What an outage looks like

The Sezzle option at checkout fails to load or returns an error after the shopper signs in, so the order cannot complete. The Sezzle website or app will not open, so shoppers cannot see or pay instalments. Merchants find the Sezzle dashboard unavailable and API calls from their store failing, which can surface as abandoned carts rather than a clear error.

What to do about it

Check status.sezzle.com, which lists the Sezzle Gateway API, Core API, Website and Dashboards separately. Shoppers facing a failed checkout should not retry repeatedly: confirm in Sezzle whether an order was created before trying again or paying another way. Merchants should check the Gateway API row before debugging their own checkout integration, and look for orders left pending once it recovers.

Is it down for everyone, or just you?

If this page says Sezzle 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

Sezzle outage FAQ

Sezzle failed at checkout. Was I charged?

Check before trying again. Sign in to Sezzle once the website is working and see whether an order was created for that store. If one exists, the purchase went through even though the store page showed an error. If none exists, nothing was charged, and you can retry or pay another way without ending up with two orders.

Is Sezzle down or is it the store?

Look at status.sezzle.com. Sezzle reports its Gateway API and Core API separately from the Website, so checkout can fail at every store while sezzle.com works, or the reverse. If the APIs are operational and only one store fails, the problem is probably that store's integration, and its support team is the right contact.

What if an instalment is due while Sezzle is down?

Try again once the website or app is back, and keep a note of when the attempt failed. Sezzle does not state on its status page how it treats payments missed during an outage, so contact Sezzle support if a late fee appears for a day when the service was unavailable.

I am a merchant. How do I tell a Sezzle outage from my own bug?

Check the Sezzle Gateway API and Core API rows, and the Dashboards row for merchant tools. If they show an incident, errors from your checkout are almost certainly theirs. After recovery, review orders left pending during the incident, since some customers will have completed the Sezzle step without the store confirming the order.

Is Sezzle down for everyone or just me?

Compare the status page with this page's regional measurements. If both show Sezzle healthy, the likely causes are local: an ad blocker or privacy extension blocking the checkout window, or a stale browser session. Failures from several regions at once point to Sezzle itself.

How we measure this

We request Sezzle'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 Sezzle 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 Sezzle 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