- Detected by Pingoru
- May 14, 2026, 01:00 PM UTC
- Resolved
- May 14, 2026, 07:07 PM UTC
- Duration
- 6h 7m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 3 updates
-
investigating May 14, 2026, 01:00 PM UTC
Users may be unable to enroll in in-person identity proofing at this time due to issues with one of our proofing vendors. Users may encounter timeouts or errors as they try to complete the proofing process. All other services are functioning normally at this time. We will provide an update as soon as more information is available.
-
investigating May 14, 2026, 01:47 PM UTC
In-person identity proofing is disabled while we investigate issues with one of our proofing vendors. All other services are functioning normally at this time. We will provide an update as soon as more information is available.
-
resolved May 14, 2026, 07:07 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Apr 25, 2026, 04:56 PM UTC
- Resolved
- Apr 27, 2026, 03:39 PM UTC
- Duration
- 1d 22h
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
identified Apr 25, 2026, 04:56 PM UTC
Users may be unable to enroll in in-person identity proofing at this time due to issues with one of our proofing vendors. Users may encounter timeouts or errors as they try to complete the proofing process. Users are advised to wait until the incident is resolved if they require in-person identity proofing. All other services are functioning normally at this time. We will provide an update as soon as more information is available.
-
resolved Apr 27, 2026, 03:39 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 19, 2026, 10:53 PM UTC
- Resolved
- Mar 20, 2026, 12:57 PM UTC
- Duration
- 14h 4m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 3 updates
-
investigating Mar 19, 2026, 10:53 PM UTC
Users will be unable to proof identity at this time using passports due to issues with one of our proofing vendors. All other services are functioning normally at this time. We will provide an update as soon as more information is available.
-
monitoring Mar 20, 2026, 12:42 PM UTC
The proofing vendor service is now available. We have re-enabled identity proofing with passports and we are monitoring the situation.
-
resolved Mar 20, 2026, 12:57 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Feb 08, 2026, 08:25 PM UTC
- Resolved
- Feb 08, 2026, 09:47 PM UTC
- Duration
- 1h 21m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
investigating Feb 08, 2026, 08:25 PM UTC
We are seeing authentication errors for a subset of our PIV/CAC users. We are currently investigating the issue.
-
resolved Feb 08, 2026, 09:47 PM UTC
We have identified the problem. It resulted from expired certs used by our PIV/CAC hosts. We have updated the certs and bundles on the hosts; users that previously had issues can now sign in successfully. We will continue to monitor and update accordingly if any new findings are reported.
Read the full incident report →
- Detected by Pingoru
- Jan 14, 2026, 07:44 PM UTC
- Resolved
- Jan 15, 2026, 01:29 PM UTC
- Duration
- 17h 45m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 3 updates
-
investigating Jan 14, 2026, 07:44 PM UTC
We are currently investigating an elevated error rate for text messages through Verizon. Two factor codes or phone verification codes delivered by SMS may return errors or fail to be delivered. Other two factor authentication mechanisms, such as Authenticator App (TOTP) or backup codes, should be unaffected. We are monitoring this and will post updates as available.
-
investigating Jan 14, 2026, 07:44 PM UTC
We are continuing to investigate this issue.
-
resolved Jan 15, 2026, 01:29 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Dec 02, 2025, 05:30 AM UTC
- Resolved
- Dec 02, 2025, 05:30 AM UTC
- Duration
- —
Timeline · 1 update
-
resolved Dec 02, 2025, 02:19 PM UTC
Impact: Moderate - Customer support functionality was unavailable via phone line The Login.gov Contact Center phone line was unavailable from 12:30 a.m. - 2:00 a.m. Eastern. Login.gov users were able to submit help desk tickets using the online form. Login.gov continued to function normally during this window. Partners may submit any questions or concerns through our Partner Support system: https://logingov.zendesk.com/
Read the full incident report →
- Detected by Pingoru
- Nov 17, 2025, 07:30 PM UTC
- Resolved
- Nov 17, 2025, 07:52 PM UTC
- Duration
- 22m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
investigating Nov 17, 2025, 07:30 PM UTC
Some users may experience errors and/or slow performance when using Login.gov. We are investigating the cause at this time and will provide more information when it is available. Agency partners should email [email protected] if immediate support is needed.
-
resolved Nov 17, 2025, 07:52 PM UTC
Between 2:04 PM and 2:25 PM Eastern Time, we experienced increased error rates from our cloud service provider. The issue has been resolved and the service is operating normally.
Read the full incident report →
- Detected by Pingoru
- Oct 30, 2025, 03:07 AM UTC
- Resolved
- Oct 30, 2025, 05:46 AM UTC
- Duration
- 2h 39m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
identified Oct 30, 2025, 03:07 AM UTC
Users may be unable to enroll in in-person identity proofing at this time due to issues with one of our proofing vendors. Users may encounter timeouts or errors as they try to complete the proofing process. All other services are functioning normally at this time. We will provide an update as soon as more information is available.
-
resolved Oct 30, 2025, 05:46 AM UTC
This incident has been resolved.
Read the full incident report →
Critical October 13, 2025 - Detected by Pingoru
- Oct 13, 2025, 05:30 PM UTC
- Resolved
- Oct 13, 2025, 06:04 PM UTC
- Duration
- 34m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 3 updates
-
investigating Oct 13, 2025, 05:10 PM UTC
We are currently investigating an elevated error rate with our text messaging provider. Two factor codes or phone verification codes delivered by SMS may return errors or fail to be delivered. Other two factor authentication mechanisms, such as voice codes, authenticator application (TOTP) or backup codes should be unaffected. The team is working to identify the cause and resolve it. We will provide an update here when more information is available.
-
monitoring Oct 13, 2025, 05:49 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 13, 2025, 10:33 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Sep 15, 2025, 08:11 PM UTC
- Resolved
- Sep 16, 2025, 01:13 PM UTC
- Duration
- 17h 2m
Affected: Customer Support Phone Line
Timeline · 4 updates
-
investigating Sep 15, 2025, 08:11 PM UTC
Impact: Moderate - Customer support functionality unavailable via the contact center phone number. The Login.gov Contact Center phone number is currently unavailable and we are currently investigating. Login.gov users are able to submit help desk tickets using the online form. Login.gov will continue to function normally during this window. Partners may submit any questions or concerns through our Partner Support system: https://logingov.zendesk.com/
-
identified Sep 16, 2025, 12:25 PM UTC
The issue has been identified and a fix is being implemented.
-
monitoring Sep 16, 2025, 12:52 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 16, 2025, 01:13 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 25, 2025, 09:47 PM UTC
- Resolved
- Aug 28, 2025, 12:48 PM UTC
- Duration
- 2d 15h
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
monitoring Aug 25, 2025, 09:47 PM UTC
Identity verification services are currently unavailable for residents of Nevada due to issues with a downstream service provider. All other services are functioning normally at this time. We are monitoring and will provide an update as soon as more information is available.
-
resolved Aug 28, 2025, 12:48 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 22, 2025, 04:00 AM UTC
- Resolved
- Aug 22, 2025, 10:12 AM UTC
- Duration
- 6h 12m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
investigating Aug 22, 2025, 04:00 AM UTC
Users will be unable to go through the identity proofing process at this time due to issues with one of our proofing vendors. Users may encounter timeouts or errors as they try to complete the proofing process. All other services, including single sign-on and authentication, are functioning normally at this time. We will provide an update as soon as more information is available.
-
resolved Aug 22, 2025, 10:12 AM UTC
The situation has been resolved. Identity proofing services are now available.
Read the full incident report →
- Detected by Pingoru
- Aug 19, 2025, 10:16 PM UTC
- Resolved
- Aug 21, 2025, 02:22 AM UTC
- Duration
- 1d 4h
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 3 updates
-
monitoring Aug 19, 2025, 10:16 PM UTC
Identity verification services are currently unavailable for residents of South Dakota due to issues with a downstream service provider. All other services are functioning normally at this time. We are monitoring and will provide an update as soon as more information is available.
-
monitoring Aug 19, 2025, 10:16 PM UTC
We are continuing to monitor for any further issues.
-
resolved Aug 21, 2025, 02:22 AM UTC
South Dakota has resumed normal application processing.
Read the full incident report →
- Detected by Pingoru
- Feb 13, 2025, 08:29 PM UTC
- Resolved
- Feb 13, 2025, 10:01 PM UTC
- Duration
- 1h 31m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 4 updates
-
identified Feb 13, 2025, 08:29 PM UTC
We are currently investigating an elevated error rate for text messages to AT&T customers in the United States. Two factor codes or phone verification codes delivered by SMS may return errors or fail to be delivered. Other two factor authentication mechanisms, such as Authenticator App (TOTP) or backup codes, should be unaffected. The team is working to identify the cause and resolve it. We appreciate your patience in the meantime.
-
identified Feb 13, 2025, 09:38 PM UTC
We have identified a potential mitigation. The downstream outage appears to affect only a subset of SMS short codes, so we are switching to different SMS short codes and will monitor the situation.
-
monitoring Feb 13, 2025, 09:44 PM UTC
Switching to alternate SMS short codes appears to be effective, and we are no longer seeing elevated error rates. We will continue to monitor the situation.
-
resolved Feb 13, 2025, 10:01 PM UTC
This incident has been resolved.
Read the full incident report →
Critical January 27, 2025 - Detected by Pingoru
- Jan 27, 2025, 02:42 PM UTC
- Resolved
- Jan 27, 2025, 04:41 PM UTC
- Duration
- 1h 58m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 4 updates
-
investigating Jan 27, 2025, 02:42 PM UTC
Login.gov is experiencing a critical outage impacting all services including sign in, MFA, new account creation, and identity verification. We are investigating the problem and will provide an update as soon as we have more information to share.
-
monitoring Jan 27, 2025, 04:10 PM UTC
We've identified and implemented a mitigation plan and are monitoring the results.
-
monitoring Jan 27, 2025, 04:28 PM UTC
We are continuing to monitor for any further issues.
-
resolved Jan 27, 2025, 04:41 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 24, 2025, 10:17 PM UTC
- Resolved
- Jan 24, 2025, 11:10 PM UTC
- Duration
- 53m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
monitoring Jan 24, 2025, 10:17 PM UTC
Between 4:27PM EST and 4:51PM EST, we experienced a degradation in our database that caused an increased error rate for end users. The issue has been resolved.
-
resolved Jan 24, 2025, 11:10 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 13, 2024, 09:11 PM UTC
- Resolved
- Nov 13, 2024, 10:36 PM UTC
- Duration
- 1h 24m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 3 updates
-
investigating Nov 13, 2024, 09:11 PM UTC
Users may be unable to enroll in in-person identity proofing at this time due to issues with one of our proofing vendors. Users may encounter timeouts or errors as they try to complete the proofing process. All other services are functioning normally at this time. We will provide an update as soon as more information is available.
-
monitoring Nov 13, 2024, 09:23 PM UTC
We are seeing some recovery for in-person identity verification services and will continue monitoring until we have confirmed full recovery.
-
resolved Nov 13, 2024, 10:36 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Aug 12, 2024, 02:54 PM UTC
- Resolved
- Aug 12, 2024, 04:16 PM UTC
- Duration
- 1h 21m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
monitoring Aug 12, 2024, 02:54 PM UTC
Identity verification services are currently unavailable for residents of Georgia due to issues in a downstream service provider. We are monitoring and will provide an update when the situation is resolved.
-
resolved Aug 12, 2024, 04:16 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jul 19, 2024, 02:19 PM UTC
- Resolved
- Jul 20, 2024, 04:34 AM UTC
- Duration
- 14h 14m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 5 updates
-
investigating Jul 19, 2024, 02:19 PM UTC
Identity verification services are currently unavailable for residents of several states due to issues in a downstream service provider. We are monitoring and will provide an update when the situation is resolved.
-
investigating Jul 19, 2024, 02:39 PM UTC
We have observed issues with identity verification for users from the following states: Indiana, Virginia, Texas, Georgia, Tennessee, Kansas, Pennsylvania, Iowa, Montana, Ohio, and Connecticut
-
investigating Jul 19, 2024, 05:38 PM UTC
We have seen errors subside for some states. At this time we are still seeing issues with identity verification for users in the following states: Indiana, Virginia, Texas, Georgia, Tennessee, and Kansas
-
investigating Jul 19, 2024, 09:56 PM UTC
At this point we are only observing issues with the state of Georgia.
-
resolved Jul 20, 2024, 04:34 AM UTC
The issues with Georgia have been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 13, 2024, 09:21 PM UTC
- Resolved
- Jun 14, 2024, 12:32 PM UTC
- Duration
- 15h 10m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
monitoring Jun 13, 2024, 09:21 PM UTC
Identity verification services are currently unavailable for residents of Vermont due to issues in a downstream service provider. We are monitoring and will provide an update when the situation is resolved.
-
resolved Jun 14, 2024, 12:32 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 07, 2024, 04:56 PM UTC
- Resolved
- Jun 07, 2024, 11:01 PM UTC
- Duration
- 6h 4m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 2 updates
-
monitoring Jun 07, 2024, 04:56 PM UTC
Identity verification services are currently unavailable for residents of Virginia due to issues in a downstream service provider. We are monitoring and will provide an update when the situation is resolved.
-
resolved Jun 07, 2024, 11:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 05, 2024, 04:45 PM UTC
- Resolved
- Jun 05, 2024, 07:00 PM UTC
- Duration
- 2h 14m
Affected: Single Sign-On & Identity Proofing (secure.login.gov)
Timeline · 3 updates
-
identified Jun 05, 2024, 04:45 PM UTC
The vendor Login.gov uses for SMS is currently having issues delivering SMS to T-Mobile numbers. The vendor is actively investigating. Non-SMS authentication methods (like auth app codes, passkeys, PIV/CAC) are operating normally
-
monitoring Jun 05, 2024, 05:06 PM UTC
We are seeing improved SMS delivery rates for our customers, and are continuing to monitor.
-
resolved Jun 05, 2024, 07:00 PM UTC
This incident has been resolved.
Read the full incident report →
