Live / YellowPepper / Incident
YellowPepper: Peru | Directory Ecosystem Incident | Directories | BIM Directory Related | P1 | {14/09/2026}
YellowPepper · yellowpepper.comResolved2026-09-14 11:01 UTC
Public — what happened
Summary
YellowPepper reported that its Alias Directory Service became unavailable for interoperability clients in Peru, with a lower success rate in API Resolve hurting the BIM Directory. The company said the problem began at 10:45 GMT on 14 September 2026 and that it switched off the BIM directory services at 10:55 GMT. According to YellowPepper, clients may have been unable to resolve aliases or to send and receive funds to or from BIM. The company did not name a cause; its status page lists the issue as identified, and the incident record shows it ending at 14:33 the same day.
Timeline
- Started — 2026-09-14 11:01 UTC
- Resolved — 2026-09-14 14:33 UTC · 3h 32m 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 39, 2026, our weekly internet health report.