Resolved -
YellowPepper is monitoring the service, and it is performing well. The event related to BIM's maintenance activity has been resolved.
Reported Start Time: 01:04 AM GMT-5 on 12 February 2026
Reported End Time: 02:02 AM GMT-5 on 12 February 2026
Impact: This may have impacted client’s ability to resolve aliases and/or send and receive funds from or to BIM.
Next Update: No further updates
Incident #: INC24107009
“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.”
Feb 12, 07:21 UTC
Monitoring -
BIM has informed the maintenance activity has been completed, YellowPepper has enabled the BIM Directory services at 01:59 GMT -5.
Reported Start Time: 01:04 AM GMT-5 on 12 February 2026
Impact: This may have impacted client’s ability to resolve aliases and/or send and receive funds from or to BIM.
Next Update: When more information is available
Incident: INC24107009
“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.”
Feb 12, 07:03 UTC
Update -
Due to the observed intermittence caused by the maintenance activity, YellowPepper has proceeded to disabled the BIM Directory services at 01:19 GMT -5.
Reported Start Time: 01:04 AM GMT-5 on 12 February 2026
Impact: This may impact client’s ability to resolve aliases and/or send and receive funds from or to BIM.
Next Update: When more information is available
Incident: INC24107009
“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.”
Feb 12, 06:36 UTC
Identified -
YellowPepper is aware of an Alias Directory service unavailability related to BIM affecting interoperability clients in Peru. This unavailability is due to a maintenance activity communicated by BIM.
Reported Start Time: 01:04 AM GMT-5 on 12 February 2026
Impact: This may impact client’s ability to resolve aliases and/or send and receive funds from or to BIM.
Next Update: As status changes
Incident: TBD
“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.”
Feb 12, 06:24 UTC