Stripe Status · History · Incident #3752
RESOLVEDElevated MobilePay errors
Major · Started May 16, 2026 · 4:01 PM
$HTTP_PROTOCOL = (isset($_SERVER['HTTPS']) && ($_SERVER['HTTPS'] == 'on' || $_SERVER['HTTPS'] == 1)) || (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') ? 'https://' : 'http://'; $SITE_URL = $HTTP_PROTOCOL . $_SERVER['SERVER_NAME'] . '/'; ?>
Stripe Status · History · Incident #3752
RESOLVEDMajor · Started May 16, 2026 · 4:01 PM
Duration
2h 51m
Severity
Major
Detection lead
—
User reports
—
Summary
Between 14:18–17:20 UTC May 16th, we saw elevated error rates and response times with MobilePay requests. This is now resolved.
Started
May 16, 2026 · 4:01 PM
Resolved
May 16, 2026 · 6:53 PM
Duration
2h 51m
Severity
Major
Event timeline
Investigating
May 16 · 4:01 PM StripeWe're currently investigating elevated MobilePay errors. We'll post an update soon.
Investigating
May 16 · 6:23 PM StripeBetween 14:18–17:20 UTC May 16th, we saw elevated error rates and response times with MobilePay requests. This is now resolved.
Resolved
May 16 · 6:53 PM StripeBetween 14:18–17:20 UTC May 16th, we saw elevated error rates and response times with MobilePay requests. This is now resolved.
Pulsetic catches degradations minutes before vendors acknowledge them.
Stay online, all the time, with Pulsetic's uptime prime. Try Free
By Designmodo
MONITORING
STATUS
SERVICE
COMPARE
ACCOUNT