Is ID.me down?
Last checked just nowNo incidents right now.
ID.me is operational right now. Last checked just now; the most recent incident resolved 40d ago.
Real-time ID.me status, recent outages, and incident history: pulled directly from ID.me's official status page at status.id.me every 5 minutes. Pingoru tracks 24 ID.me services and has captured 7 incidents in the last 90 days (99.38% uptime). Get email, Slack, Discord, or webhook alerts the moment ID.me reports a new incident, free for 3 monitors, no credit card.
Recent outages & incidents
Past 90 days- NIST 800-63-3 PoliciesNIST 800-63-2 PoliciesKBA-replacement PoliciesTelecom Possession APITelecom Identity APIDocument Identity API
Timeline · 4 updates
- investigating · Sep 21, 2026, 04:11 PM UTC
We're experiencing an elevated level of application errors and are currently looking into the issue. Status updates will be provided as soon as available.
- identified · Sep 21, 2026, 04:16 PM UTC
The issue has been identified and a fix is being implemented.
- monitoring · Sep 21, 2026, 04:23 PM UTC
A fix has been implemented and we are monitoring the results.
- resolved · Sep 21, 2026, 04:29 PM UTC
This incident has been resolved. The fix has eliminated the elevated level of errors for verifications.
Latest: This incident has been resolved. The fix has eliminated the elevated level of errors for verifications.
-
- NIST 800-63-3 PoliciesNIST 800-63-2 Policies
Timeline · 4 updates
- investigating · Sep 09, 2026, 05:37 PM UTC
ID.Me is experiencing IAL-2 pass rate degradation due to failures in the legal ID and face verifications. Team is actively working on to recover the services.
- investigating · Sep 09, 2026, 05:39 PM UTC
We are continuing to investigate this issue.
- investigating · Sep 09, 2026, 05:53 PM UTC
The IAL-2 pass rates are back to normal. All the affected services have been recovered. The incident is resolved.
- resolved · Sep 09, 2026, 05:53 PM UTC
This incident has been resolved.
Latest: This incident has been resolved.
-
-
Timeline · 1 update
- resolved · Aug 07, 2026, 01:48 AM UTC
We experienced an high level of application errors for Sign-Ins and Verifications from 9:12PM - 9:22PM ET due to planned maintenance. Maintenance activity ended and Sign-Ins and Verifications services returned to normal operations.
Latest: We experienced an high level of application errors for Sign-Ins and Verifications from 9:12PM - 9:22PM ET due to planned maintenance. Maintenance activity ended and Sign-Ins and Ve…
-
Incident record
Since April 2026 · Statuspage by Atlassian · 24 components checked every 5 minutesThe longest incident in the last year, Service Degradation - Authenticator App Push Notifications on April 3, 2026, ran for 4 days. 4 maintenance windows announced in the same period.
Most affected components, last 12 months
- Document Identity API6
- NIST 800-63-2 Policies6
- NIST 800-63-3 Policies6
- KBA-replacement Policies5
- Telecom Identity API5
Latest incidents
- Elevated Application Errors for Identity Verifications
We're experiencing an elevated level of application errors and are currently looking into the issue. Status updates will be provided as soon as available.
- IAL-2 pass rates degradation
ID.Me is experiencing IAL-2 pass rate degradation due to failures in the legal ID and face verifications. Team is actively working on to recover the services.
- Elevated Application Errors for Sign-Ins and Verifications
We experienced an high level of application errors for Sign-Ins and Verifications from 9:12PM - 9:22PM ET due to planned maintenance. Maintenance activity…
- Started Sep 21, 2026, 03:26 PM UTC · Resolved Sep 21, 2026, 04:29 PM UTC · 1h 3m
- IAL-2 pass rates degradation ResolvedStarted Sep 09, 2026, 05:37 PM UTC · Resolved Sep 09, 2026, 05:53 PM UTC · 16m
- Started Aug 07, 2026, 01:05 AM UTC · Resolved Aug 07, 2026, 01:12 AM UTC · 7m