Live / YellowPepper / Incident
YellowPepper: Peru | Directory Ecosystem Maintenance | Directories | BIM Directory Related | 02/09/2026
YellowPepper · yellowpepper.comMinor incidentResolved2026-09-02 07:48 UTC
Public — what happened
Summary
YellowPepper said its Alias Directory service connected to BIM was unavailable for interoperability clients in Peru, which could affect their ability to look up aliases and move money to or from BIM. The company reported the problem began at 07:41 GMT on 02 September 2026 and attributed it to a maintenance activity that BIM had announced. YellowPepper said it switched off its BIM directory services at 07:44 GMT in response, and the incident was marked resolved at 10:51 the same day.
Timeline
- Started — 2026-09-02 07:48 UTC
- Resolved — 2026-09-02 10:51 UTC · 3h 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 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 37, 2026, our weekly internet health report.