Klarna experienced a minor incident on May 8, 2026 affecting North America and North America and 1 more component, lasting 10h 37m. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- investigating May 08, 2026, 01:28 AM UTC
We are currently experiencing a service disruption affecting Klarna services in the United States. Some customers and merchants may be unable to access certain features, including shopping, payments, customer service, communications, and the Merchant Portal. We have identified the root cause as an infrastructure issue with our cloud provider and are actively working to resolve it. All other regions are unaffected. Thank you for your patience.
- identified May 08, 2026, 01:44 AM UTC
We are seeing some recovery of service for multiple services - we are monitoring this closely while also actively working on resolving this issue.
- identified May 08, 2026, 02:48 AM UTC
We are still working on a resolution, while monitoring updates from our cloud infrastructure provider.
- monitoring May 08, 2026, 04:06 AM UTC
We have implemented a fix that should help with the resolution of this issue, we are currently monitoring the outcome of this fix.
- monitoring May 08, 2026, 05:02 AM UTC
We are seeing recovery on additional services, we are still monitoring the issue closely.
- monitoring May 08, 2026, 06:52 AM UTC
We are seeing continued recovery across all services. At this time, the only remaining impact is related to recent card transactions not being visible in the app for US users. Send outs and notifications for those purchases may also be delayed.
- monitoring May 08, 2026, 10:23 AM UTC
Recovery is continuing across impacted US services. The main remaining user impact is that some recent Klarna Card transactions may not yet appear in-app, and related purchase notifications/sendouts can be delayed. We have implemented mitigation and are actively monitoring stability and full catch-up. Root cause remains tied to a cloud infrastructure provider issue.
- resolved May 08, 2026, 12:05 PM UTC
This incident has been resolved.