rewindex

ChangesStripeElevated MobilePay errors

Stripe: Major incident: Elevated MobilePay errors

Major incidentdegradation (model (Jev), 50%)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what Stripe removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: Elevated MobilePay errors
AddedImpact#2
Before: not present
After: major
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2026-05-16 16:01 UTC
AddedResolved time#5
Before: not present
After: 2026-05-16 18:53 UTC
AddedAffected components#6
Before: not present
After: Acquirers and payment methods
AddedUpdateinvestigating#7
Before: not present
After: We're currently investigating elevated MobilePay errors. We'll post an update soon.
AddedUpdateresolved#8
Before: not present
After: Between 14:18–17:20 UTC May 16th, we saw elevated error rates and response times with MobilePay requests. This is now resolved.
AddedUpdateinvestigating#9
Before: not present
After: Between 14:18–17:20 UTC May 16th, we saw elevated error rates and response times with MobilePay requests. This is now resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.

How the archive is checked, and what it cannot prove.

History of this incident

Saturday, May 16

1 incident change

All Stripe changesStripe profileMarkdownJSON