Live / Vipps MobilePay / Incident
Vipps MobilePay: Degraded service for some users
Vipps MobilePay · vippsmobilepay.comMinor incidentResolved2026-10-23 20:30 UTC
Public — what happened
Summary
Vipps MobilePay said some of its users had trouble paying by card starting at 10:52 UTC on 23 October 2026. The company said the problem was with its payment infrastructure provider and affected all card payments for those users. It reported that the issue was identified at 10:55 UTC and a fix was in place by 10:56 UTC, after which it monitored the results. The incident was marked resolved at 20:30 UTC and was rated minor by the company.
Affected
MP Online API, MP Online API, ePayments API, ePayments API, ePayments API, Webhooks, Webhooks, Webhooks
Timeline
- Started — 2026-10-23 10:52 UTC
- Investigating — 2026-10-23 10:52 UTC
- Identified — 2026-10-23 10:55 UTC
- Monitoring — 2026-10-23 10:56 UTC
- Resolved — 2026-10-23 20:30 UTC · 9h 38m after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach Vipps MobilePay against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for Vipps MobilePay: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the Vipps MobilePay report →
More from Vipps MobilePay
Covered in The Squid’s Ink, Week 44, 2026, our weekly internet health report.