Live / PawaPay / Incident
PawaPay: Performance degradation affecting Lesotho M-Pesa services
PawaPay · pawapay.cloudCritical outageResolved2026-11-13 16:02 UTC
Public — what happened
Summary
PawaPay reported a critical incident affecting deposit services for M-Pesa in Lesotho, which began at 05:52 UTC on 2026-11-13. The company said it had spotted instability and passed the matter to the mobile money operator, and at 08:26 UTC it described the problem as an outage of the Lesotho M-Pesa deposit gateway while it kept following up with that operator. PawaPay marked the incident resolved at 16:02 UTC the same day, though the text provided does not say what was done to fix it.
Affected
M-Pesa :: Web Deposit
Timeline
- Started — 2026-11-13 05:52 UTC
- Identified — 2026-11-13 05:52 UTC (2 updates)
- Resolved — 2026-11-13 16:02 UTC · 10h 10m 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.