Is Klarna down right now?

No. As of 2026-10-10 07:18 UTC, Klarna is up. This page reads the status again every 3 minutes.

Where does this status come from?

From Klarna's own status page API at https://status.klarna.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Klarna's words.

Can I get an alert when Klarna goes down?

Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Klarna reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/klarna/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.

How can my agent or app check Klarna status?

Fetch https://upbutler.com/status/klarna/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"klarna"}, on https://upbutler.com/mcp/public.

How do I know whether an outage is mine or Klarna's?

Add "klarna" to the dependencies of your UpButler workspace. When one of your monitors fails while Klarna has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Is Klarna down?

Klarna is up

Right now

No. No incidents reported.

Last checked 45 s ago (2026-10-10 07:18 UTC) from status.klarna.com · every 180s

For agents

proceed

Proceed.

GET upbutler.com/status/klarna/status.agent.json

MCP: upstream_status {"service":"klarna"}

Buy now, pay later checkout and payments APIs.

What Klarna says

Operational

Taken as is from Klarna's own status page API. Incident titles and component names below are theirs.

Open status.klarna.com

What UpButler measured

There is no keyless endpoint of Klarna that says anything useful, so UpButler does not probe it. To check your own Klarna account, add a monitor with your key: it is yours alone and catches what a shared probe cannot.

Open at Klarna

Planned maintenance: Database upgrade in Europe and the UKscheduled maintenance
Starts 2026-10-12 21:00 UTC · Europe
During scheduled maintenance, incoming and outgoing Single Euro Payments Area (SEPA) payments may briefly fail or time out. The interruption is expected to last up to approximately 30 seconds. Failed payments are not retried automatically and may need to be resubmitted once services recover. Pay by Bank will temporarily disable SEPA Instant before the migration and re-enable it afterwards. No data loss is expected. We apologize for any inconvenience this may cause.
Planned maintenance: PostgreSQL services upgrade in North Americascheduled maintenance
Starts 2026-10-12 07:00 UTC · North America
On 12 October between 09:00 and 11:00 CEST, we will perform scheduled maintenance on Klarna banking services in North America. During this window, customers may briefly experience errors or slower responses when viewing accounts, balances or transaction history, making transfers or top-ups, or using Klarna Card. The interruption is expected to last up to approximately 2 minutes. Services should recover automatically. We apologize for any inconvenience.

Text written by Klarna, shown unchanged.

Klarna components

39 operational

Klarna Payments

EuropeOperational
North AmericaOperational
Asia PacificOperational

Merchant Onboarding

EuropeOperational
North AmericaOperational
Asia PacificOperational

Merchant Portal

EuropeOperational
North AmericaOperational
Asia PacificOperational

Customer Service

EuropeOperational
North AmericaOperational
Asia PacificOperational

Payments in the App

EuropeOperational
North AmericaOperational
Asia PacificOperational

Banking in the App

EuropeOperational

Klarna Card

EuropeOperational
North AmericaOperational
Asia PacificOperational

Merchant Settlements/Payouts

EuropeOperational
North AmericaOperational
Asia PacificOperational

Sign-in

EuropeOperational
North AmericaOperational
Asia PacificOperational

Klarna Credit Card

EuropeOperational
North AmericaOperational

One-Time Card

EuropeOperational
North AmericaOperational
Asia PacificOperational

Shopping in the App

EuropeOperational
North AmericaOperational
Asia PacificOperational

Transaction history in the app

EuropeOperational
Asia PacificOperational
North AmericaOperational

Chat and Disputes in the App

EuropeOperational
North AmericaOperational
Asia PacificOperational

Klarna incidents, last 90 days

2026-07-13: no record
2026-07-14: no record
2026-07-15: no record
2026-07-16: no record
2026-07-17: no record
2026-07-18: no record
2026-07-19: no record
2026-07-20: no record
2026-07-21: no record
2026-07-22: no record
2026-07-23: no record
2026-07-24: no record
2026-07-25: no record
2026-07-26: no record
2026-07-27: no record
2026-07-28: no record
2026-07-29: no record
2026-07-30: no record
2026-07-31: no record
2026-08-01: no record
2026-08-02: no record
2026-08-03: no record
2026-08-04: no record
2026-08-05: no record
2026-08-06: no record
2026-08-07: no record
2026-08-08: no record
2026-08-09: no record
2026-08-10: no record
2026-08-11: no record
2026-08-12: no record
2026-08-13: no record
2026-08-14: no record
2026-08-15: no record
2026-08-16: no record
2026-08-17: no record
2026-08-18: no record
2026-08-19: no record
2026-08-20: no record
2026-08-21: no record
2026-08-22: no record
2026-08-23: no record
2026-08-24: no record
2026-08-25: no record
2026-08-26: no record
2026-08-27: no record
2026-08-28: no record
2026-08-29: no record
2026-08-30: no record
2026-08-31: no record
2026-09-01: no record
2026-09-02: no record
2026-09-03: no record
2026-09-04: no record
2026-09-05: no record
2026-09-06: no record
2026-09-07: no record
2026-09-08: no record
2026-09-09: no record
2026-09-10: no record
2026-09-11: no record
2026-09-12: no record
2026-09-13: no record
2026-09-14: no record
2026-09-15: no record
2026-09-16: no record
2026-09-17: no record
2026-09-18: no record
2026-09-19: no record
2026-09-20: no record
2026-09-21: no record
2026-09-22: no record
2026-09-23: no record
2026-09-24: no record
2026-09-25: no record
2026-09-26: no record
2026-09-27: no record
2026-09-28: no record
2026-09-29: no record
2026-09-30: no record
2026-10-01: no record
2026-10-02: no record
2026-10-03: no record
2026-10-04: no record
2026-10-05: no record
2026-10-06: no record
2026-10-07: no record
2026-10-08: no record
2026-10-09: no incident reported
2026-10-10: no incident reported

2026-07-130 of 2 days with an incidenttoday

Each bar is a day, coloured by the worst incident Klarna reported. It is their incident record, not a measurement of uptime.

Incidents: 1; 0 major or critical
Typical time to resolve: —; median, needs 3 incidents
Nine in ten within: —; 90th percentile
Longest: under a minute; record since 2026-10-09

Started (UTC)	Incident	Impact	Lasted
2026-10-09 18:17	Sign-in and purchase disruption for BankID in Sweden	none	under a minute

Get alerted when Klarna goes down

No account. One email when Klarna reports an incident, one when it is over. You confirm the address first, and every email has a one-click unsubscribe.

Or follow the RSS feed. On UpButler? Add Klarna as a dependency to route it to Slack, Teams or a webhook.

Status badge

Show Klarna's current status in a README or an internal wiki. It updates by itself.

[![Klarna status](https://upbutler.com/status/klarna/badge.svg)](https://upbutler.com/status/klarna)

Tell your outage from Klarna's

Declare that your project depends on Klarna. When one of your monitors fails while Klarna has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.

npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.

Start free How it works

upbutler.yaml

# upbutler.yaml
dependencies:
  - klarna

Ask before you retry

curl -s https://upbutler.com/status/klarna/status.agent.json

status.agent.json (live)

{
  "schema": "upbutler.upstream-status/v1",
  "service": "klarna",
  "verdict": "proceed",
  "status": "operational",
  "reason": "No incidents reported",
  "retryAfterSec": null,
  "incident": null,
  "probe": null
}

Questions

Is Klarna down right now?: No. As of 2026-10-10 07:18 UTC, Klarna is up. This page reads the status again every 3 minutes.
Where does this status come from?: From Klarna's own status page API at https://status.klarna.com. UpButler reads it once for everyone (not once per visitor) every 3 minutes with conditional requests, and shows it unchanged: incident titles and component names are Klarna's words.
Can I get an alert when Klarna goes down?: Yes, without an account: enter your email on this page, confirm the link we send, and you get one email when Klarna reports an incident and one when it is over. There is also an RSS feed at https://upbutler.com/status/klarna/feed.rss. Teams on UpButler can route the same alert to Slack, Teams or a webhook.
How can my agent or app check Klarna status?: Fetch https://upbutler.com/status/klarna/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"klarna"}, on https://upbutler.com/mcp/public.
How do I know whether an outage is mine or Klarna's?: Add "klarna" to the dependencies of your UpButler workspace. When one of your monitors fails while Klarna has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.

Also check

UpButler is not affiliated with Klarna. Status and incident text belong to Klarna and are read from their public status source; the probe result is UpButler's own measurement.