The links we point at
The post URLs this run was handed — the dataset we ran the test on, before any request goes out.
| Platform | Target | Source URL |
|---|---|---|
| The linkset loads here the moment a run is armed. | ||
Every week, any visitor can trigger a run that scrapes 1,000,000 real public posts in about 20 minutes — roughly 72 million a day at that pace. Watch the success rate, throughput and latency move live. No other scraping API lets you do this.
Crawling the verified profile corpus for recent public posts and assembling 250,000 active URLs plus 25,000 reserves before the measured waves begin.
Finalizing results.
The run did not complete. Its partial results remain on the public record.
This console is connected to the public benchmark controller.
We run millions of scrapes a day for production teams — a public run clears its 1,000,000 in about 20 minutes, roughly 72 million a day at that pace. Before you trust a vendor with that volume, you should watch it clear a real load and check the numbers yourself — so any visitor can put the network through a 1,000,000-scrape run, once every 7 days.
Make a free account ($10 credit, no card) and fire the run yourself — no sales call, no demo. One run at a time, one every 7 days, so it stays fair.
You decide which million links we scrape:
A validated library — 250,000 active URLs plus 25,000 reserves. Four waves, 1,000,000 scrapes, starts instantly. Download and inspect it first.
Our profile scrapers crawl verified profiles for fresh posts, build a brand-new 275,000-link set, and run four waves — 1,000,000 scrapes.
Every request takes the same production path as a paying customer's — residential network, real-visitor traffic, per-platform parsers. No special harness. You watch the console tick up live: throughput, success rate, latency.
Every row is published with a link to its live post — open any of them and check our number against the source. Download the full set as JSON or CSV.
Both halves of the run, yours to inspect: the links we point at and the results we got back. Pull a random 10,000-row sample to spot-check, or download the whole set — either half, as JSONL or CSV.
The post URLs this run was handed — the dataset we ran the test on, before any request goes out.
| Platform | Target | Source URL |
|---|---|---|
| The linkset loads here the moment a run is armed. | ||
What each link returned — the metric, latency and status. Open any row to check it against the live post.
| Platform | Target | Captured | Scraped at (UTC) | Latency | Status |
|---|---|---|---|---|---|
| Rows stream in here live as the run scrapes — each one links to its real post. | |||||
Anyone can copy a landing page overnight. Nobody can fake a year of weekly runs. Every run gets a permanent page — including the weeks it dipped, incident note attached.
A number is only as honest as the shortcuts it couldn't take. Here's what a public run is built so it can't do.
A visitor fires it at a random hour, into whatever live load the network is already carrying. There's no quiet moment picked to make the numbers look better.
Every request takes the same production path a paying customer's does — the same residential network, the same parsers. There's no benchmark-only shortcut.
The corpus is assembled from a rotating profile list, not a curated set of posts we already know will score well. We don't get to choose the easy ones.
Each row carries the raw captured value and its week-over-week delta — no rounding up, no "up to" figures, no averages hiding a bad platform inside a good total.
Every week we scrape 1,000,000 public posts in the open. Anyone can watch the run live and audit the results after — the only scraping API with a benchmark you can watch happen.
Each public run scrapes 1,000,000 posts in about 20 minutes — roughly 72 million a day at that pace. It runs on the same production path that serves paying customers, who run millions of scrapes a day.
No. Benchmark traffic is deprioritized below paying customers, so a run can't degrade a real customer's success rate or latency — even though it runs at a random, real-world hour.
Anyone with a free account — $10 credit, no card. One run at a time, one per week; everyone else watches the same live console.
Make a free account, trigger a run, and watch a million scrapes clear in real time. The proof is the product.
Create a free account →