Updated: November 13, 2026 | Service: Aadhaar Authentication | Authority: UIDAI, Government of India
Quick Answer: How to Fix Aadhaar Error E-67
Error E-67 – Connection Timeout From ASA API indicates that an Aadhaar-related application has reported a timeout while communicating with its Authentication Service Agency (ASA) interface.
The problem may involve the application, internet connectivity, the ASA gateway or another component of the authentication service.
Try these steps: Check your internet connection, wait briefly, restart the affected application and retry the authentication once. If the problem continues, contact the bank, attendance administrator, service centre or application provider handling the transaction.
Important: E-67 has not been verified as an official UIDAI authentication response code. Its precise definition may depend on the application or ASA provider.
What Is Aadhaar Error Code E-67?
Some Aadhaar-integrated applications display a message similar to:
ERROR E-67
Connection Timeout From ASA API
Authentication request could not be completed
This message suggests that a component of the application did not receive the expected response within its configured timeout period.
It does not necessarily mean that the Aadhaar number is invalid, the biometric information is incorrect or the Aadhaar account is blocked.
It also does not establish that UIDAI’s central authentication system is unavailable.
UIDAI’s official documentation distinguishes authentication response errors from connectivity and service-provider issues. Authentication Service Agencies may use their own error codes for timeout situations.
What Is an ASA API in Aadhaar Authentication?
ASA stands for Authentication Service Agency.
An ASA provides secure connectivity between an authorized Authentication User Agency (AUA) and UIDAI’s Central Identities Data Repository (CIDR).
An AUA is an authorized organization that uses Aadhaar authentication to verify identity for an eligible service.
The typical authentication path is:
| Step | System | Function |
|---|---|---|
| 1 | User or operator | Initiates authentication with consent |
| 2 | Application / AUA | Prepares and submits an authentication request |
| 3 | ASA | Transmits the request through authorized secure connectivity |
| 4 | UIDAI CIDR | Processes the authentication request |
| 5 | ASA / AUA | Returns the response to the application |
If a communication timeout occurs at any stage, the application may display a technical error rather than a successful authentication response.
See the official Aadhaar Authentication API specification for the technical architecture.
Also Read : Jeevan Pramaan Life Certificate Download by PPO Number 2026
Why Does E-67 Connection Timeout Happen?
| Possible Cause | Explanation | Suggested Action |
|---|---|---|
| Unstable internet | The application cannot reliably communicate with its provider. | Check internet connectivity. |
| ASA gateway timeout | The ASA interface does not respond within the application’s timeout period. | Contact the service provider. |
| Temporary service interruption | A provider system may be unavailable or overloaded. | Wait and retry later. |
| Network routing problem | Traffic between authorized systems may be interrupted. | Escalate to the technical team. |
| Firewall or proxy restrictions | Required application traffic may be blocked. | Request an administrator review. |
| Outdated application | An older client may have compatibility or connection issues. | Install approved updates. |
| Incorrect integration configuration | Gateway, endpoint or authentication settings may be incorrect. | Ask the AUA/ASA integration team. |
These are potential causes of a connection timeout, not confirmed explanations for every E-67 occurrence.
Fix 1: Check Your Internet Connection
Begin with the simplest test.
- Check whether the device is connected to the internet.
- Open a trusted website to confirm basic connectivity.
- If using Wi-Fi, verify the network is stable.
- If authorized, switch to another trusted connection.
- Return to the application and retry once.
Basic internet access does not prove that the application’s secure ASA connection is working. However, it can help identify a local connectivity problem.
Fix 2: Wait and Retry the Aadhaar Transaction
Temporary network interruptions may resolve without changing any settings.
- Stop submitting additional authentication requests.
- Wait a few minutes.
- Check whether the original transaction was completed.
- If it did not complete, submit a fresh request through the normal application workflow.
Fix 3: Restart the Aadhaar Application
A temporary application-session problem may sometimes be cleared by restarting the software.
- Close the affected application normally.
- Wait briefly.
- Reopen the application.
- Sign in using the approved method.
- Check whether a software update is available.
- Retry the transaction if its previous status is confirmed.
Use only official or organization-approved applications. Avoid installing APK files or patches from unknown websites.
Fix 4: Check the Biometric Device and RD Service
If the error appears during biometric attendance, banking or identity verification, check the biometric device’s normal operating status.
For an authorized operator:
- Confirm the biometric device is connected.
- Check whether its Registered Device (RD) service is running.
- Use the approved device diagnostic utility if available.
- Check for device or RD service error messages.
- Restart the application if required.
- Contact the device vendor if its service is malfunctioning.
Note: A biometric device problem is not the same as an ASA API timeout. These checks are useful for identifying separate issues that may occur during the same authentication workflow.
Fix 5: Check the Device Date and Time
Incorrect system time can cause some Aadhaar authentication requests to fail.
UIDAI documents specific timestamp-related errors, including codes 561 and 562.
For Windows or Android devices:
- Open the device’s date and time settings.
- Enable automatic date and time synchronization where supported.
- Verify the correct time zone.
- Restart the affected application.
However, incorrect device time is not an officially established cause of E-67 specifically.
Fix 6: Check ASA and AUA Connectivity
This step is intended for authorized technical administrators, not ordinary Aadhaar users.
When multiple terminals report the same timeout, the problem may involve a shared application server, AUA integration or ASA connection.
The technical team should review:
- Application-to-AUA response times.
- AUA-to-ASA connectivity and authorized routing.
- ASA gateway availability.
- Connection and read-timeout settings.
- Firewall and proxy rules.
- Relevant service health monitoring.
- Request correlation IDs and response logs.
- Whether other applications using the same gateway are affected.
Production Aadhaar authentication connectivity is restricted to authorized secure infrastructure. Do not attempt to bypass ASA controls or connect directly to production UIDAI endpoints.
Fix 7: Contact the Bank, Service Centre or Attendance Administrator
If E-67 continues after basic checks, contact the organization providing the Aadhaar-enabled service.
Examples include:
- Aadhaar-enabled banking or payment service provider.
- Biometric attendance system administrator.
- Authorized Aadhaar authentication operator.
- Government service portal support team.
- AUA or ASA technical helpdesk.
Provide the error message, application name, approximate time and a transaction reference if one is available.
Do not share your Aadhaar OTP, biometric data, password or full Aadhaar number in public support forums.
Is E-67 an Official UIDAI Error Code?
The official UIDAI Authentication API contains numbered errors covering demographic mismatches, biometric failures, invalid requests, authorization problems and server-side technical failures.
E-67 is not listed as a standard UIDAI authentication response code in the official documentation reviewed.
Its exact definition should therefore be obtained from the application developer or ASA provider.
E-67 vs Other Aadhaar Authentication Error Codes
| Error Code | Documented Meaning | Recommended Response |
|---|---|---|
| E-67 | Reported ASA API connection timeout; provider-specific definition unverified | Check connectivity and contact the provider |
| 300 | Biometric data did not match | Follow approved biometric retry guidance |
| 400 | OTP validation failed | Verify or regenerate OTP |
| 542 | AUA not authorized for ASA | Administrator checks AUA-ASA linkage |
| 561 | Authentication request expired | Check time synchronization and submit a fresh request |
| 562 | Request timestamp is in the future | Correct device time |
| 563 | Duplicate authentication request | Use a fresh request as instructed |
| 930–939 | Technical server-side errors | Escalate through authorized technical support |
| 999 | Unknown authentication error | Contact the responsible support team |
For official definitions, refer to UIDAI API Error Handling documentation.
How to Diagnose E-67 in Aadhaar Biometric Attendance
When an attendance terminal shows E-67, the operator should first determine whether the issue affects one device or several devices.
If Only One Device Is Affected
- Check that terminal’s network connection.
- Verify the approved attendance application is running.
- Check for device-specific warnings.
- Ask the local administrator to review the terminal configuration.
If Multiple Devices Are Affected
- Check the attendance platform’s service notices.
- Determine whether the devices share a network or application gateway.
- Report the issue to the nodal officer or technical administrator.
- Ask the provider to investigate ASA connectivity.
The official Aadhaar-enabled Biometric Attendance System (AEBAS) documentation lists other connectivity-related errors, including 1201 for lost ASA connectivity and 1204 for no response from UIDAI.
These are separate codes and should not be treated as equivalent to E-67.
What Should Developers Check for ASA API Timeouts?
For authorized AUA and ASA integration teams, a timeout should be investigated using the application’s approved monitoring and incident-response process.
| Diagnostic Area | What to Review |
|---|---|
| Request lifecycle | Request start, gateway handoff and response timestamps |
| Timeout configuration | Approved connection and response timeout values |
| Network health | Packet loss, latency and route availability |
| Gateway capacity | Connection pools, saturation and service health |
| Certificates | Valid certificates and approved TLS configuration |
| Transaction tracing | Non-sensitive correlation IDs and response codes |
| Retries | Safe retry rules that prevent duplicate processing |
| Escalation | ASA provider support and incident records |
UIDAI requires careful protection of Aadhaar authentication information. Do not store raw biometric information, authentication secrets or sensitive request payloads in ordinary application logs.
Does Error E-67 Mean Aadhaar Is Blocked?
No. The E-67 timeout message alone does not establish that an Aadhaar number is blocked, cancelled or suspended.
UIDAI documents separate authentication codes for invalid or inactive Aadhaar records.
If you are concerned about Aadhaar status, use the official myAadhaar portal or contact UIDAI through an official support channel.
Frequently Asked Questions
What is error E-67 connection timeout from ASA API?
It is an error message reported by some Aadhaar-integrated applications when their ASA API communication does not complete within the expected time.
How do I fix Aadhaar E-67 error?
Check internet connectivity, wait briefly, restart the application and retry after verifying the original transaction status. Contact the service provider if it continues.
Is E-67 an official UIDAI error?
E-67 has not been verified in the official UIDAI Authentication API error list. It may be an application-specific or ASA-specific error.
What is ASA in Aadhaar?
ASA means Authentication Service Agency. It provides authorized secure connectivity between Aadhaar authentication user agencies and UIDAI’s central authentication infrastructure.
Can slow internet cause E-67?
An unstable network can contribute to application timeouts. However, the error may also originate from an upstream service or gateway.
Does E-67 mean my fingerprint is wrong?
No. A connection timeout does not by itself establish a biometric mismatch.
Can I solve E-67 by updating the RD service?
Updating an outdated or malfunctioning RD service may resolve a separate device problem, but it is not a confirmed universal fix for E-67.
Is UIDAI server down when E-67 appears?
Not necessarily. A timeout can occur in the application, network, AUA or ASA systems without a UIDAI-wide outage.
Should I submit the Aadhaar request repeatedly?
No. Check the previous transaction status first, particularly when banking or payment services are involved.
Who should I contact if E-67 continues?
Contact the organization operating the application, such as your bank, attendance administrator or authorized service provider. The provider can escalate the issue to its technical team.
Can I contact UIDAI directly?
For general Aadhaar assistance, visit UIDAI’s official website or call the published helpline. For application-specific ASA API errors, the service provider is usually the appropriate first contact.
Will reinstalling the app fix E-67?
Reinstallation is not recommended as the first step. If the problem is upstream, reinstalling will not resolve it. Follow your provider’s approved troubleshooting instructions.
Official Sources and Support
- UIDAI — Official Website
- UIDAI — API Error Handling and Documentation
- UIDAI — Aadhaar Authentication API Specification
- AEBAS — Biometric Attendance Error Codes
- myAadhaar — Official Portal
- C-DAC — Aadhaar ASA/AUA Services
Related Error Fix Guides
For additional login, authentication and government service troubleshooting, browse  News and Error Fix Guides.
Final Summary: Aadhaar Error E-67
- Error: E-67 – Connection Timeout From ASA API.
- Meaning: The application reports a timeout in ASA API communication.
- Possible causes: Network instability, gateway timeout or provider service interruption.
- First fix: Check connectivity and verify transaction status before retrying.
- For operators: Check the approved application, device and attendance platform.
- For administrators: Review AUA/ASA connectivity and non-sensitive logs.
- Escalation: Contact the responsible application or service provider.
Bottom line: E-67 is primarily a reported communication timeout, not proof of an Aadhaar biometric mismatch or blocked Aadhaar number. The application provider must confirm its exact internal meaning.
Editorial note: Reviewed November 13, 2026 using official UIDAI Authentication API documentation and government biometric attendance references. E-67 is treated as a provider-specific reported error because an official UIDAI definition for that exact code could not be established.


Pingback: Best Enterprise Cloud Infrastructure Migration Tools in 2026-27