A database described as “updated today” can contain old detection results. Before comparing its size or price, find out what changed today: the file, the catalog record or the underlying fact about the number.
Freshness is useful when it describes the evidence you need. It becomes misleading when several different timestamps are compressed into one marketing label.
Three dates describe three events
| Timestamp | What happened | What it does not prove |
|---|---|---|
| Ingestion date | The record entered the catalog | A new platform or network check happened then |
| Detection or observation date | A particular check produced a result | Every other fact on the record was refreshed |
| Export generation date | Your order file was created | The records were rechecked during file generation |
Keep these dates separate in your comparison. A newly generated CSV can faithfully deliver an older observation without making that observation recent.
Recent ingestion is a selection rule
Pinglake’s self-service date choices are 3, 7, 30 or 90 days of ingestion. They narrow the records entering the catalog within that window. They do not promise that every phone number was rechecked during the same period.
When you select a platform, inspect its observation time as well as the record’s ingestion time. If a timestamp is missing, keep that uncertainty visible rather than substituting another date.
A record can contain facts of different ages
A number might have a recent registration result for one platform and an older result for another. Carrier metadata may come from numbering rules rather than a live lookup. A single “last updated” date cannot describe all of that evidence.
List the facts your workflow relies on, then check the age and method of each. The valid, active and registered guide explains why the checks are distinct.
Compare a useful slice rather than two global totals
Start with one country and the required number type. Add only the platforms and attributes you need. Check whether enough records remain for your intended quantity.
If you are comparing two suppliers, use the same count definition and timestamp rule. A smaller file with documented observations can be more useful than a larger file of unknown age, but recency alone does not guarantee reachability, response or permission to contact.
Keep the estimate separate from the delivery count
A browsing screen may show a sample-based estimate or a bounded count such as 50,000+. Neither should be read as an exact total inventory figure.
Confirm the quantity you intend to purchase and the quote before payment. When the generated file arrives, compare the manifest’s unique-row quantity with the order. Export time belongs in that audit trail, alongside the source observation times.
A short freshness review before purchase
Ask which date drives the filter, where each platform’s check time appears, how unknown timestamps are represented and when the export was generated. Also ask whether the carrier is inferred or observed, if your workflow depends on it.
Review the phone data vendor checklist and CSV field guide, then choose a country. Define the freshness you need before comparing the number of rows.