Performance observations · BIGDBM
September 2026 API performance observations
BIGDBM reports an approximately 80% match rate and 100–300ms API response latency from analysis of internal API activity during September 2026. The reporting workload exceeded 20 billion API requests. Figures are stated as of October 1, 2026.
| Measure | Reported result |
|---|---|
| Reporting period | September 1–30, 2026 |
| Internal API workload | More than 20 billion requests |
| Match rate | Approximately 80% |
| API response latency | 100–300ms |
Source and measurement scope
Source: BIGDBM’s analysis of internal API requests for September 2026. These are company-reported observations from production activity, not a controlled comparison against other providers. Raw request logs are not published with this report.
How to interpret the results
Request volume counts API activity, not unique people, records or customers. The number of eligible matching requests, endpoint mix, duplicate or retry treatment and distribution of input identifiers are not specified here. The overall workload count should not be used as the denominator to reconstruct the match rate.
The reported latency range is not identified as a percentile or minimum/maximum. It should not be interpreted as a p95 or p99 guarantee, an external end-to-end response time, or a contractual SLA.
Evaluating your own workload
Use a representative, deduplicated sample of your identifiers and agree on the matching denominator and confidence threshold. Measure false matches as well as coverage. For API performance, record the endpoint, payload, client region, concurrency, error rate and latency percentiles.
Request a workload-specific evaluation or review coverage definitions, API documentation and RFIS scoring.