Live  /  YellowPepper  /  Incident

YellowPepper: Peru | Transactional Ecosystem incident | YellowPepper - Yepex | Niubiz Related | Priority 2 | 15/11/2026

YellowPepper · yellowpepper.comMinor incidentResolved2026-11-15 19:12 UTC
Public — what happened

Summary

YellowPepper said its Yepex service was running slowly for clients in Peru, which could delay sending or receiving funds. Its first notice was posted at 15:05 UTC on 15 November 2026, and it later said some transaction requests might not go through. The company said the problem was tied to Niubiz, but that it could not see what happened inside Niubiz's processing and that Niubiz would need to confirm the origin. YellowPepper later said the impact had been reduced, gave an end time of 11:14 GMT-5, kept monitoring, and the incident was marked resolved at 19:12 UTC.

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 47, 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.