Is Worldpay Down?

No — Worldpay is up

Reachable from all 8 checked regions

Average response time: 1994ms

Last checked just now · checks run every 6 hours

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

Worldpay uptime

100%

Last 7 days

100%

Last 30 days

100%

Last 90 days

1236ms

Avg response, 30 days

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

30-day history

66-day clean streak

Sep 12 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

416ms

DNS 0ms TCP 2ms TLS 7ms TTFB 387ms

arn

690ms

DNS 0ms TCP 1ms TLS 5ms TTFB 660ms

nrt

2097ms

DNS 0ms TCP 49ms TLS 1095ms TTFB 1832ms

ord

490ms

DNS 0ms TCP 1ms TLS 6ms TTFB 440ms

sin

3558ms

DNS 0ms TCP 217ms TLS 438ms TTFB 2430ms

sjc

3892ms

DNS 0ms TCP 1ms TLS 160ms TTFB 3769ms

syd

3836ms

DNS 0ms TCP 47ms TLS 99ms TTFB 3237ms

yyz

980ms

DNS 0ms TCP 13ms TLS 153ms TTFB 893ms

What Worldpay does

Worldpay is a payment processor and merchant acquirer handling card authorisation, settlement and payouts for retailers, restaurants and online businesses. Merchants reach it through the Worldwide Payment Gateway, hosted payment pages and direct integrations, and it routes transactions across card and debit networks. For many businesses it is the link between a card being tapped and money arriving in the bank.

What an outage looks like

Card payments decline at checkout or on the terminal with network or gateway errors rather than a genuine refusal, and a retry sometimes succeeds where the first attempt failed. Hosted payment pages fail to load or hang after the customer submits card details. Settlement files and payouts arrive late, and merchant portals and reporting may be unreachable while authorisation itself works normally.

What to do about it

Check status.worldpay.com, which separates Authorization & Payments, Acquiring Services, Funding & Payouts and Portals & Reporting, and publishes numbered incidents with running updates. Worldpay's notes distinguish its own faults from card-network ones: an incident on 6 August 2026 on the Accel network resolved without any technical intervention by Worldpay. Read the current incident before deciding whether to re-run declined transactions.

Is it down for everyone, or just you?

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

Worldpay outage FAQ

Is Worldpay down, or is it my card network?

The status page distinguishes the two. Worldpay posts incidents naming the specific network or third party involved, with recent entries covering the Accel debit network and an Electronic Benefit Transfer problem traced to FIS Global, and in several of those it states that all Worldpay systems were operating normally throughout. If failures are confined to one card type or scheme, a network incident is the likelier explanation.

Will a Worldpay outage delay my payouts?

Possibly, because Funding & Payouts is a separate component from authorisation. Transactions that authorised successfully are recorded even when the settlement and payout stage is degraded, so the money is not lost, but the date it reaches your bank can move. Watch that component specifically rather than the overall banner, since authorisation can be perfectly healthy while funding is not.

Should I retry a declined transaction during an incident?

Read the incident note first. Worldpay's updates say explicitly when retries may succeed: its 6 August 2026 gateway incident stated that some transactions were declined with a network-related failure and that retries may be successful. Where a note does not say so, repeated attempts risk multiple authorisations against one customer's card, which is harder to unwind than a single failed sale.

Does an outage affect card machines as well as online payments?

It can, because both routes depend on the same authorisation and acquiring components. The status page does not split in-person from online, so check Authorization & Payments and Acquiring Services, which cover both. If only your hosted payment pages are failing while terminals keep working, that points at the gateway rather than acquiring, and recent incidents have been scoped exactly that narrowly.

How we measure this

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