Peru | Transactional Ecosystem incident | YellowPepper Caused | P2 | 02/07/2026
Incident
Report for YellowPepper
Resolved
We have now resolved the issue affecting Yepex service. YellowPepper will conduct an internal review of the event to mitigate future occurrences and enhance financial ecosystem controls.
Reported Start Time: 02 July 2026, 12:55 GMT
Reported End Time: 02 July 2026, 14:18 GMT
Impact: This may have prevented certain transaction requests to be successful.
Next Update: No further updates
Incident #: INC26305363
Reported Start Time: 02 July 2026, 12:55 GMT
Reported End Time: 02 July 2026, 14:18 GMT
Impact: This may have prevented certain transaction requests to be successful.
Next Update: No further updates
Incident #: INC26305363
Identified
We have identified an issue with Yepex affecting clients in Peru.
This issue is causing service intermittence or degradation.
We are working urgently to resolve the ongoing situation.
Reported Start Time: 02 July 2026, 12:55 GMT
Impact: This may prevent certain transaction requests to be successful.
Next Update: Within 60 minutes
Incident #: INC26305363
This issue is causing service intermittence or degradation.
We are working urgently to resolve the ongoing situation.
Reported Start Time: 02 July 2026, 12:55 GMT
Impact: This may prevent certain transaction requests to be successful.
Next Update: Within 60 minutes
Incident #: INC26305363
Update
We are continuing to investigate this issue.
Investigating
YellowPepper is experiencing a Yepex degradation affecting clients in Perú.
We are investigating the cause and working urgently to resolve the situation.
Reported Start Time: 02 July 2026, 12:55 GMT
Impact: This may prevent certain transaction requests to be successful.
Next Update: Within 60 minutes
Incident #: INC26305363
We are investigating the cause and working urgently to resolve the situation.
Reported Start Time: 02 July 2026, 12:55 GMT
Impact: This may prevent certain transaction requests to be successful.
Next Update: Within 60 minutes
Incident #: INC26305363
This incident affected: Yepex (Peru).