52 recorded Stark Bank incidents since May 2024, with official updates, affected components, duration and resolution information.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
There was an instability in the creation of transfers resulting in 400 errors in the API
The issue was identified and a correction is being deployed
The incident has been resolved
We are currently experiencing an issue with our acquiring service that is preventing some Visa transactions from being approved. All other card networks are operating normally. Our team is actively working with Visa to resolve this as quickly as possible.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The status of some Transfers and BrcodePayments experienced a delay in updates between 12:35 and 12:55 BRT. The incident has been resolved and all statuses are now reflecting correctly. No transactions were lost or affected, only the status updates were delayed during this window.
There is an instability in the communication with our settlement bank. The resolution status for yesterday’s boleto settlements, boleto payments, tax payments and utility payments is delayed.
The issue has been identified as an instability with our settlement bank.
This incident has been resolved.
We observed widespread system instability across our infrastructure, resulting in elevated error rates. The incident occurred from 11:02 on April 10th until 00:22 on April 11th. The issue has been mitigated and services have returned to normal operation.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We are currently experiencing a Pix instability due to an issue in the Central Bank’s systems. Our team is monitoring the situation and will provide updates as more information becomes available.
The current issue is affecting the Central Bank’s DICT system, preventing the use of Pix keys in any capacity.
We are continuing to monitor for any further issues.
This incident has been resolved.
Between 10/dez 18:50 and 11/12 09:30 (GMT-3), some card purchase transactions were not approved due to an internal issue in the acquiring authorization flow. The issue was resolved, and all systems have been operating normally since then.
There is an instability in the communication with our settlement bank. The resolution status for yesterday’s boleto settlements, boleto payments, tax payments and utility payments is delayed.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
There is an instability in the communication with our settlement bank. The resolution status for yesterday’s boleto settlements, boleto payments, tax payments and utility payments is delayed.
We are continuing to investigate this issue.
This incident has been resolved.
We’re currently investigating an instability in the provider postal code lookup service, which affects only the address search step in physical card requests.
After further investigation, we identified that the issue was caused by an instability in our provider’s services. The service now appears to have stabilized, and our team is currently monitoring to ensure everything remains fully operational.
We have been monitoring the provider’s service since yesterday, and it has remained stable during this period. As the functionality has been consistently operating as expected, we are now marking this incident as resolved.
We are currently investigating this issue.
We are monitoring
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
There is an instability in processing Pix operations.
This incident has been resolved.
