Live / Incidents / YellowPepper
YellowPepper: Peru | Directory Ecosystem Maintenance | Directories | CCE Directory Related | 01/10/2026
YellowPepper · yellowpepper.comImpact: minorResolved2026-10-01 08:08 UTC
Public — what happened
Summary
YellowPepper is monitoring the service, and it is performing well.
The event related to CCE affecting interoperability clients in Peru has been resolved.
<b>Reported Start Time:</b> 01 October 2026, 06:38 GMT
<b>Reported End Time:</b> 01 October 2026, 07:49 GMT
<b>Impact:</b> This may have prevented clients from successfully resolving aliases and/or sending and receiving funds through CCE.
<b>Next Update:</b> No further updates
<b>Incident #:</b> INC27130265
“This notification does not have the intention to designate or allocate any liability to any specific party of ecosystem for the alerts, interruptions, or impacts mentioned in this communication.”
Timeline
- Started — 2026-10-01 06:48 UTC
- Last update — 2026-10-01 08:08 UTC
- Resolved — 2026-10-01 08:08 UTC
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 →