Live / YellowPepper / Incident
YellowPepper: Peru | Directory Ecosystem Maintenance | Directories | CCE Directory Related | 22/10/2026
YellowPepper · yellowpepper.comMinor incidentResolved2026-10-22 08:56 UTC
Public — what happened
Summary
YellowPepper said an alias directory service tied to CCE became unavailable, affecting interoperability clients in Peru. The company said the outage came from a maintenance activity that CCE had announced, and that it switched off its CCE directory services at 01:09 local time (GMT-5) after seeing the problem. It warned that customers might be unable to look up aliases or to send and receive funds to or from CCE. The incident began at 06:13 UTC on October 22, 2026, and was marked resolved at 08:56.
Affected
Peru
Timeline
- Started — 2026-10-22 06:13 UTC
- Identified — 2026-10-22 06:13 UTC (2 updates)
- Resolved — 2026-10-22 08:56 UTC · 2h 43m 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 44, 2026, our weekly internet health report.