Live / PawaPay / Incident
PawaPay: Performance degradation affecting Kenya Mpesa services
PawaPay · pawapay.cloudMinor incidentResolved2026-11-13 02:25 UTC
Public — what happened
Summary
PawaPay said its Kenya M-Pesa services were running with reduced performance, a problem it rated as minor and first reported at 10:22 UTC on 12 November 2026. Later that day it noted that success rates were getting better, then said the deposit gateway was still affected and that it was working with the mobile money operator on it. By 21:08 UTC it again reported improving success rates while it kept monitoring, and the incident was marked resolved at 02:25 UTC on 13 November. PawaPay did not name a cause in the updates provided.
Affected
M-Pesa :: Web Deposit
Timeline
- Started — 2026-11-12 10:22 UTC
- Investigating — 2026-11-12 10:22 UTC
- Monitoring — 2026-11-12 14:21 UTC (3 updates)
- Resolved — 2026-11-13 02:25 UTC · 16h 03m 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 PawaPay 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 PawaPay: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the PawaPay report →
More from PawaPay
Covered in The Squid’s Ink, Week 47, 2026, our weekly internet health report.