Instability in the Nubank application affects customers and service is normalized in a few hours
On August 14, 2026, the Nubank application faced moments of instability, preventing millions of users from accessing its digital services. Account holders reported problems querying data and using the platform’s features, generating concern among the fintech’s vast customer base. The situation, however, was quickly resolved by the financial institution.
Crash reports and user notifications

Problems in the system began to be noticed around 6:20 pm, as pointed out by the Downdetector portal, which monitors interruptions in online services. At this peak, more than 2,800 failure notifications related to Nubank were recorded, indicating a broad awareness of the incident. During the interruption, many account holders were surprised by a notification directly in the application, informing them of the impossibility of uploading their information.
Learn more: US Bank faces digital instability affecting 1,350 banking customers this Monday
Impact on Nubank’s customer base
The relevance of an interruption, even if brief, is magnified by the size of Nubank’s operation. The institution serves approximately 118 million customers in Brazil, covering both individuals and legal entities. For these users, the failure meant a temporary impediment to access to essential transactions, balance checks, payments and other daily financial operations, highlighting the dependence on the digital service in modern life.
Nubank’s response and the normalization of services
Nubank officially confirmed the technical incident on its platform. According to the company, the situation was completely normalized around 7pm, reestablishing access and functionality for all affected users. Speedy resolution was crucial to minimize inconvenience and consumer confidence.
Details of the incident still unexplained
Despite the rapid normalization, Nubank did not provide specific details about the origin of the failure that caused instability in its application. The lack of information about the exact cause raises questions about the infrastructure and security protocols to prevent similar incidents from happening again. Maintaining transparency in these moments is essential for the trust of millions of customers.
Brief chronology of the application problem
- Start of reports: Around 6:20 pm, with an increase in notifications on Downdetector.
- Notification to users: Customers saw a message saying it was impossible to load information.
- Normalization: Service fully restored around 7pm.

















