Portuguese 
English 
Spanish 
3 min of reading 
0 comments 
Instability Affected The App On Monday (6). Reports On Downdetector Exceeded 4.5 Thousand; Itaú Stated That The Service Was 100% Normalized By Around 7:40 PM.
Itaú Unibanco clients reported issues accessing the app, paying bills, and making Pix on Monday, October 6, 2025. Complaints began in the afternoon and concentrated between 3 PM and 6 PM. According to the bank, it was a “point-in-time instability” impacting part of the user base.
According to monitoring from Downdetector, complaints surpassed 4.5 thousand around 5:24 PM, indicating a peak of unavailability perceived by users. The surge started after 2 PM.
In a statement sent to the press, Itaú said it had been working on a fix and apologized to clients. Later, it announced that services were normalized by around 7:40 PM.
-
The INSS and the Ministry of Management set December 31, 2026, as the deadline for mandatory biometric registration, see who needs to do it.
-
Tax reform raises an alert in industrial engineering and puts EPC contracts, heavy infrastructure, and large projects at the center of the debate.
-
New ‘Rota dos Sertões’ could elevate the Brazilian Northeast with R$ 4.1 billion in investments, nearly 500 km modernized on the BR-116, 95 km of duplications, and strategic works that promise to transform logistics, agribusiness, and the regional economy.
-
Brazil could become a global powerhouse in green aviation fuel: JetBio plans to build the world’s largest commercial SAF factory, producing 1 billion liters per year from domestic ethanol, with 90% of production for export and operations expected to start in 2030.
The instability occurred on the 5th business day, when there is an increase in access for bill payments and transfers. During the same period, other banks also recorded peaks in reports of issues, according to specialized websites.
When Did The Instability On The Itaú App Start?
Error reports started to intensify in the early afternoon. Monitoring tools indicated a rise in notifications starting at 2 PM, accompanied by thousands of mentions on social media.
Newspapers and websites reported the sequence of complaints and access difficulties. The reports mentioned issues authenticating in the app and completing transactions.
The peak of reports occurred in the late afternoon, shortly before 6 PM, when users reported inability to log in, pay bills, and use Pix.
What Did Itaú Say And When Did The App Come Back?
The bank acknowledged the instability and stated it was working to normalize “as quickly as possible,” apologizing for the inconvenience.
According to an update sent to the press and tech sites, the system was 100% restored by around 7:40 PM on Monday (6).
After the fix, traffic on the app gradually resumed, with reports of normalized access by early evening.
Pix, Bill Payments, And Login Among The Affected Services
Users reported login failures and slowness when opening the app. Some complaints involved bills due on the day and failed attempts at completing Pix transactions.
Independent monitoring listed “login,” “bill payments,” and “Pix transfers” among the most frequently mentioned issues during the afternoon.
The total number of complaints during the period exceeded 4.5 thousand, reinforcing the concentrated nature of the disruption.
5th Business Day Concentrates Traffic And Pressures Digital Services
The incident coincided with the 5th business day, the date with the highest volume of access in digital channels due to salary and bill payments. Specialized portals noted that during similar windows, various institutions typically record peaks in reports.
Also on Monday (6), there were reports of instability attributed by users to other banks. The official assessment regarding the origin of each case varied by institution.
For consumers, the practical recommendation is to keep proof of attempts, protocols, and screenshots to dispute interest and fines in case of undue charges after the service normalization.
Do you think that the bank should automatically waive interest and fines when the failure is in the app, or should it depend on case-by-case analysis? Leave your comment.
Be the first to react!