Space for ads
Checked every 5 minutes · How we measure this
As of 15:10 EDT on 8 Sep 2026, digilocker.gov.in responded to our check in 28 ms, with 100.00% availability over the last 24 hours.
Checked every 5 minutes · last checked 5 minutes ago
The line is response time measured from our probe to digilocker.gov.in, which rises when the service slows down. Shaded red marks intervals where checks actually failed. It excludes your own connection and browser rendering.
0 problem reports
No incidents recorded since monitoring began. Monitoring for DigiLocker records every incident lasting ten minutes or more.
DigiLocker is responding normally. Our last automated check of digilocker.gov.in completed 5 minutes ago and succeeded in 28 ms. Over the past 24 hours the service answered 100.00% of our checks.
Measured from our automated checks, DigiLocker has been available 100.00% over 24 hours, 100.00% over 7 days, 100.00% over 30 days. We have recorded no incidents in the last 30 days.
DigiLocker has averaged 159 ms across our successful checks in the past 24 hours, which is fast — comfortably within what a healthy service should return. Response time is measured from our probe to digilocker.gov.in and does not include rendering time in your browser.
Our probe is reaching digilocker.gov.in normally right now, so the problem is more likely to be local to you than a full outage. Use the report button on this page to add your own signal — when several people report the same problem within a short window, it appears on the chart above.
Board result days drive sharp spikes in marksheet retrieval. Retrying outside those windows is usually faster than repeatedly refreshing during them.
Application portals are provisioned for average load, not deadline load. If a form will not submit in the final hours of a window, the server is queueing rather than rejecting you — retrying every few seconds makes the queue worse for everyone, including you.
Screenshot any error page with a visible timestamp, and save the transaction or reference ID if payment was attempted. Boards frequently extend deadlines after a documented outage, and the screenshot is what supports a grievance.
Aggregator and coaching sites often mirror stale links. Type digilocker.gov.in directly rather than following a search result, which avoids landing on a decommissioned subdomain.
Open any other site. If nothing loads, the issue is your network rather than DigiLocker. On Windows run ping digilocker.gov.in and nslookup digilocker.gov.in in Command Prompt; on macOS or Linux use Terminal. A DNS failure and a server failure look identical in a browser but are very different problems.
Load digilocker.gov.in in a private or incognito window. If it works there, clear cookies and site data for digilocker.gov.in in your normal browser rather than clearing everything.
Switch from Wi-Fi to mobile data, or vice versa. Regional ISP routing problems are common and often affect one carrier while others are unaffected.
We link the vendor status page so you can check our reading against theirs.
No comments received
