CheckUpstream does not yet run an independent probe against Klarna, so no availability figure is published for it — only Klarna's own disclosure record below. 17 incidents were recorded in the past 12 months; the most recent resolved earlier today after 1 hour. Status signals are polled from Klarna's official Atlassian Statuspage status page, alongside independent probes and community reports.
Independent measurement how this is computed
Not measured
We run no independent probe against Klarna yet, so we publish no availability figure for it. What follows is Klarna's own disclosure record, which is a different thing.
Vendor disclosed: 5 incidents · 29 of 30 days with none posted · 1h of declared impact
Fewer incidents in the last 30 days than 18% of 232 tracked services.
Share of each window with no impact declared by Klarna
7d
99.399%
30d
99.860%
90d
99.953%
180d
99.714%
1y
99.859%
Downtime like this can be refundable
If you're a paying Klarna customer, outages in these windows may count against Klarna's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Klarna entitlement →Does Klarna actually matter to you?
A Klarna outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →From 5 incidents Klarna published and resolved in the last 30 days, measured between their own start and resolution times. It describes how long Klarna takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 31, 19:19 UTC · resolved in 1h 20m · Resolved
Aug 28, 06:12 UTC · resolved in 1h 18m · Resolved
Aug 28, 06:12 UTC · resolved in 8m · Resolved
Live Klarna status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/klarna)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Klarna is currently Operational. CheckUpstream tracks Klarna in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Looking for the live "is Klarna down" view? See the Klarna Live status page.
Aug 25, 12:30 UTC · resolved in 31m · Resolved
Aug 25, 12:30 UTC · resolved in 4m · Resolved
Apr 30, 12:07 UTC · resolved in 42m · Resolved
Apr 26, 12:12 UTC · resolved in 49m · Resolved
Apr 18, 03:32 UTC · resolved in 2h 17m · Resolved
Apr 17, 11:50 UTC · resolved in 49m · Resolved
Apr 9, 08:37 UTC · resolved in 1d 1h · Resolved
Mar 30, 08:59 UTC · resolved in 53m · Resolved
Mar 25, 11:10 UTC · resolved in 59m · Resolved
Klarna's last resolved incident started earlier today and lasted 1h 20m (degraded performance).
We don't publish one. CheckUpstream runs no independent probe against Klarna yet, and the only other figure available would be derived from Klarna's own incident posts — which measures how much a vendor discloses rather than how available it was. Vendors that post often score worse than vendors that stay quiet, so the number would be backwards.
Sign up to CheckUpstream and add Klarna to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Klarna's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.