The essentials
Developer error sent test notification to 11 million Crédit Agricole users, crashing the app.
Crédit Agricole sent a test notification to 11 million users due to a developer error, triggering an unexpected surge in login attempts that caused application outages across the platform. The incident originated from an internal testing procedure that inadvertently reached the bank's entire user base rather than a limited test group.
The mass notification prompted a spike in simultaneous login attempts, overwhelming the bank's systems and rendering the application unavailable to customers. The outage underscores how test procedures, when misconfigured, can cascade into production-level incidents affecting millions of users.
Other ways to read this story.
Alternative framings generated by SigNews. These are not independent sources or attributed quotations.
Testing protocol failure cascades into major service disruption
The incident reveals a gap in testing controls. A developer error allowed a test notification to reach production users, generating 11 million unexpected login attempts simultaneously. The surge overwhelmed login infrastructure, disabling the application for all users. This demonstrates insufficient segregation between test and production environments.
Millions lose access to banking services due to internal mistake
11 million Crédit Agricole customers received an unexpected test notification, prompting a wave of login attempts that crashed the application. Customers attempting to access banking services encountered outages stemming entirely from an internal developer error, leaving them unable to perform transactions or check accounts.