User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Shopping
Is IDfy down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: FSSAI Verification performance is degraded | PHL SEC Verification performance is degraded
Source: the vendor's status page · We are not affiliated with IDfy.
What to try while IDfy is having problems
Estimated fix: Not enough IDfy history yet; similar Shopping outages lasted 9 min (median, typically 8 min–17 min; 47 outages).
- Try the app instead of the website (or the reverse); orders already placed are not affected.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → idfy.com—
Your browser → us—
Our checksReaching it
Official · ReportsCritical incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 374 ms.
Official status
Critical incident
FSSAI Verification performance is degraded | PHL SEC Verification performance is degraded Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 22 | 0 | 0.0 | 326 ms | 0 |
| Tue 00 | 0 | 0.0 | 1035 ms | 0 |
| Tue 02 | 0 | 0.0 | 352 ms | 0 |
| Tue 04 | 0 | 0.0 | 1035 ms | 0 |
| Tue 06 | 0 | 0.0 | 1037 ms | 0 |
| Tue 09 | 0 | 0.0 | 1014 ms | 0 |
| Tue 11 | 0 | 0.0 | 959 ms | 0 |
| Tue 13 | 0 | 0.0 | 1130 ms | 0 |
| Tue 15 | 0 | 0.0 | 1048 ms | 0 |
| Tue 17 | 0 | 0.0 | 905 ms | 0 |
| Tue 20 | 0 | 0.0 | 472 ms | 0 |
| Tue 22 | 0 | 0.0 | 380 ms | 0 |
| Wed 00 | 0 | 0.0 | 858 ms | 0 |
| Wed 02 | 0 | 0.0 | 948 ms | 0 |
| Wed 05 | 0 | 0.0 | 1002 ms | 0 |
| Wed 07 | 0 | 0.0 | 1175 ms | 0 |
| Wed 09 | 0 | 0.0 | 1145 ms | 0 |
| Wed 11 | 0 | 0.0 | 1220 ms | 0 |
| Wed 13 | 0 | 0.0 | 1073 ms | 0 |
| Wed 15 | 0 | 0.0 | 1138 ms | 0 |
| Wed 18 | 0 | 0.0 | 665 ms | 0 |
| Wed 20 | 0 | 0.0 | 996 ms | 0 |
| Wed 22 | 0 | 0.0 | 1041 ms | 0 |
| Thu 00 | 0 | 0.0 | 358 ms | 0 |
| Thu 02 | 0 | 0.0 | 1042 ms | 0 |
| Thu 04 | 0 | 0.0 | 1195 ms | 0 |
| Thu 06 | 0 | 0.0 | 984 ms | 0 |
| Thu 08 | 0 | 0.0 | 1010 ms | 0 |
| Thu 11 | 0 | 0.0 | 1215 ms | 0 |
| Thu 13 | 0 | 0.0 | 992 ms | 0 |
| Thu 15 | 0 | 0.0 | 1085 ms | 0 |
| Thu 17 | 0 | 0.0 | 360 ms | 0 |
| Thu 19 | 0 | 0.0 | 360 ms | 0 |
| Thu 21 | 0 | 0.0 | 1056 ms | 0 |
| Thu 23 | 0 | 0.0 | 378 ms | 0 |
| Fri 01 | 0 | 0.0 | 936 ms | 0 |
| Fri 03 | 0 | 0.0 | 990 ms | 0 |
| Fri 05 | 0 | 0.0 | 1065 ms | 0 |
| Fri 07 | 0 | 0.0 | 1015 ms | 0 |
| Fri 09 | 0 | 0.0 | 1035 ms | 0 |
| Fri 10 | 0 | 0.0 | 336 ms | 0 |
| Fri 12 | 0 | 0.0 | 1109 ms | 0 |
| Fri 14 | 0 | 0.0 | 954 ms | 0 |
| Fri 16 | 0 | 0.0 | 628 ms | 0 |
| Fri 18 | 0 | 0.0 | 1035 ms | 0 |
| Fri 19 | 0 | 0.0 | 352 ms | 0 |
| Fri 21 | 0 | 0.0 | 310 ms | 0 |
| Fri 22 | 0 | 0.0 | 374 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live IDfy badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
Having trouble with IDfy?
One report per service every 10 minutes from this network. No account.
Follow IDfy
Get an email when IDfy goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send IDfy alerts to Slack, Discord or a webhook — free.
About IDfy
We track IDfy (idfy.com) as part of the Shopping group. Secure Customer Onboarding | Smarter Fraud Detection | DPDP Compliance & Privacy Governance made Easy for Banks, E-Commerce, and Logistics.
IDfy publishes an official status page at status.idfy.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with shopping services: checkout and payment errors, carts not loading, and order tracking problems.
Measured uptime from our checks: 100% over 8 days of checks. We logged 1 public incident since monitoring began 8 days ago.
Response time over the last 24 hours: 801 ms average, 273–1258 ms range across 16 successful checks.
Questions
Is IDfy down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: FSSAI Verification performance is degraded | PHL SEC Verification performance is degraded
When was IDfy last down?
The most recent public incident we recorded started 2026-11-06 and lasted 3 days 17 h. 1 incident since monitoring began 8 days ago.
What is IDfy's uptime?
From our own checks: 100% over 8 days of checks.
How fast does IDfy respond?
801 ms on average over the last 24 hours (273–1258 ms).
Does IDfy have an official status page?
Yes, at https://status.idfy.com.
IDfy not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For shopping services, watch for checkout and payment errors, carts not loading, and order tracking problems. If many people report IDfy here at once, the problem is on IDfy's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with IDfy. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.