Major incident
ID.me: Elevated Application Errors for Identity Verifications
Sep 21, 2026, 15:26 UTC
started
16:29 UTC
resolved
1 h 03 min
duration
Affected: NIST 800-63-3 Policies, NIST 800-63-2 Policies, KBA-replacement Policies, Telecom Possession API, Telecom Identity API, Document Identity API
Current status of ID.me: Operational — live ID.me status
Timeline
- Sep 21, 2026, 15:26 UTCinvestigatingWe're experiencing an elevated level of application errors and are currently looking into the issue. Status updates will be provided as soon as available.
- Sep 21, 2026, 16:16 UTCidentifiedThe issue has been identified and a fix is being implemented.
- Sep 21, 2026, 16:23 UTCmonitoringA fix has been implemented and we are monitoring the results.
- Sep 21, 2026, 16:29 UTCresolvedThis incident has been resolved. The fix has eliminated the elevated level of errors for verifications.
Updates as published by ID.me (original).
Other services with incidents at the same time
This was part of a wider event: 13 services reported incidents within the hour.
- Confluent Cloud 16:15 UTC · Confluent Cloud Console Degraded (All Regions) and Multiple Services Impacted in AWS us-west-2
- GoCardless 15:28 UTC · Delayed BACS reports
- Netlify 15:12 UTC · Errors accessing Netlify-hosted sites
- Circle 15:08 UTC · Circle CCTP Testnet - Delays/Degraded Performance
- Pitt Digital Systems 15:07 UTC · RESOLVED: Vendor Issue Affecting Phone Calls to Technology Help Desk
- SU ITS 14:49 UTC · Webex Contact Center Issues
- Ivanti Cloud 14:46 UTC · IAZ PRD - Tenants are not accessible
More ID.me incidents
- September 9, 2026 IAL-2 pass rates degradation
- August 7, 2026 Elevated Application Errors for Sign-Ins and Verifications
- July 31, 2026 shop.id.me Service Unavailable
- July 24, 2026 Verification Services Outage
- July 17, 2026 Site Wide Intermittent Service Interruption
- July 14, 2026 Verification Services Outage