Live / YellowPepper / Incident
YellowPepper: Peru | Directory Ecosystem Incident | Directories | BIM Directory Related | {28/09/2026}
YellowPepper · yellowpepper.comResolved2026-09-29 03:15 UTC
Public — what happened
Summary
YellowPepper said a slowdown in the BIM directory affected clients in Peru who rely on interoperability between payment services, potentially preventing them from looking up aliases or moving money to and from BIM. According to the company, the problem began at 20:30 on 28 September 2026 (GMT-5) and ended at 21:56 the same evening. YellowPepper did not name a cause, reported the issue as resolved, and said it would continue watching the service, which it described as working normally.
Timeline
- Started — 2026-09-29 01:46 UTC
- Resolved — 2026-09-29 03:15 UTC · 1h 28m 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 YellowPepper 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 YellowPepper: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the YellowPepper report →
More from YellowPepper
Covered in The Squid’s Ink, Week 41, 2026, our weekly internet health report.