How long does the report take after payment?
No delivery time is promised. The report is released as soon as the provider document is validated; one documented request returned a PDF in 10.6 seconds.
Check the review date and linked sources for context. Live availability, prices and record coverage can vary by VIN, source, jurisdiction and time.
The current policy does not promise a delivery time, and the site deliberately shows no estimate until the real report is ready. The report is released as soon as the provider document comes back and is validated, which can be seconds: the internal reliability review records an authorised provider request returning a PDF in 10.6 seconds. The same review records one incident needing a manual check that took about 33 minutes and 30 seconds from payment to ready report.
- No artificial delay is added; delivery happens as soon as the provider PDF is validated.
- The order page shows progress, never a countdown — no estimate is shown until the report is ready.
- A provider request is allowed up to 180 seconds before it is treated as interrupted.
- Internal speed targets exist, but they are proposed, unvalidated and explicitly not a commercial promise.
What the wait consists of
Payment is confirmed server-side, then the report job asks the data provider for the document for your VIN. That single provider request is the long pole: it is allowed up to 180 seconds before the system treats it as interrupted. Nothing else in the path is padded, and the internal review is explicit that no artificial 180-second delay is added to the journey.
That is why the preparing screen states that no estimated time is shown until the real report is ready. A countdown would be a guess about a third party’s response time, and a wrong guess is worse than none.
| Step | Observed | How to read it |
|---|---|---|
| Authorised provider request | 10.6 seconds | One request that returned the PDF, not a typical case |
| Report ready to email sent | 0.25 seconds | Sending was not the bottleneck in that incident |
| Report ready to email delivery event | 1.83 seconds | An email-provider event, not proof anyone read it |
| Payment to report ready, during one incident | About 33 min 30 s | Includes a manual check and operator handling |
When it takes longer than that
If a provider request ends without a status, a provider report identifier or a complete PDF, the order is moved to a manual check instead of being retried automatically. The reason is financial rather than technical: the provider may already have processed the first request, so an automatic retry could become a second billable purchase.
In that case the status changes, you receive a message confirming that the payment was received and asking you not to pay again, and support receives a private copy so a person already has the case. No resolution time is published for a manual check; the one documented incident resolved in roughly half an hour end to end.
Steps
- Leave the order page open or close it — both work.
- Check My Reports before assuming a failure.
- Read the status wording before retrying anything.
- Never start a second payment for the same vehicle.
What this does not cover
- A single observed request is not a latency distribution and does not predict your vehicle.
- The internal targets, such as 95% of orders ready within 120 seconds, are proposed SLOs awaiting production measurement, not guarantees.
- Email timing is measured from the email provider’s events and never proves a message was read.
Sources reviewed
Open the underlying public source and verify that its scope matches the question you are asking.
Frequently asked questions
Why is there no progress percentage or countdown?
Because the wait depends on a third party’s response. The preparing screen states that no estimated time is shown until the real report is ready, which is why you see labelled steps — collecting records, preparing report — rather than a number that would be invented.
It is slow. Should I pay again?
No. The states where a second payment is the tempting mistake say so in writing: the payment-confirmation step, the stopped-report state, the pack’s pending-payment state and the manual-check message all record the payment and tell you not to submit another one. If something looks stuck, send the order reference to support instead.
Is half an hour normal?
No. That figure comes from a single documented incident that required a manual check and human handling. The same review records an authorised provider request returning a PDF in 10.6 seconds. Neither number is a promise about your order.