Live  /  YellowPepper  /  Incident

YellowPepper: Peru | Directory Ecosystem Maintenance | Directories | CCE Directory Related | 06/10/2026

YellowPepper · yellowpepper.comMinor incidentResolved2026-10-06 09:21 UTC
Public — what happened

Summary

YellowPepper said its Alias Directory service tied to CCE was unavailable for interoperability clients in Peru on October 6, 2026, with the problem reported as beginning at 01:14 GMT-5. The company said this stemmed from a maintenance activity that CCE had announced, and that it switched off the CCE directory services at 01:19 GMT-5. According to YellowPepper, affected clients may have been unable to look up aliases or to send and receive money to or from CCE. The incident, which YellowPepper rated minor, was marked resolved at 09:21 the same day.

Affected

Peru

As listed on YellowPepper’s status page.

Timeline

Source of record: provider status page. Summary written by SquidGrid from the provider’s published updates; times in UTC.

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 see
Customers 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 42, 2026, our weekly internet health report.

The full archive is on the YellowPepper status & history page.

Related: YellowPepper status & history. SquidGrid is not affiliated with YellowPepper.