Live / Incidents / YellowPepper
YellowPepper: Peru | Transactional Ecosystem Incident | Payment Processor | Niubiz Related | Priority 2 | Date (08/09/2026)
YellowPepper · yellowpepper.comImpact: maintenanceResolved2026-09-08 09:01 UTC
Public — what happened
Summary
YellowPepper is aware of a Yepex latency related to Niubiz affecting clients in Peru.
YellowPepper does not have the visibility to identify the origin of the event within Niubiz processing. Therefore, events must be confirmed with Niubiz to know the exact detail of the origin of the incident.
<b>Reported Start Time:</b> 08 September 2026, 08:46 GMT
<b>Impact:</b> Clients in Peru may experience latency when receiving or sending funds.
<b>Next Update:</b> When more information is available
<b>Incident #:</b> INC26943825
“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 mentio
Timeline
- Started — 2026-09-08 09:01 UTC
- Last update — 2026-09-08 09:01 UTC
- Resolved — 2026-09-08 11:45 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 →