social-general
archive.today. X / Facebook
archive.today used specifically for X and Facebook pages that the Wayback crawler often cannot reach, holding tens of millions of on-demand snapshots. Existence is checked through its Memento timemap, and you open the saved snapshot via a direct link. It is valuable for social pages other archives miss, though the snapshot pages can rate-limit and it has faced regional blocks in 2026.
Why it’s useful & how it works
archive.today captures social pages on demand, which means it often holds copies of tweets and Facebook posts that automated crawlers like the Wayback Machine never reached. Anyone can submit a URL for saving, and millions of social pages have been captured this way over the years. You search by pasting a URL and browsing the snapshot history, or by opening a direct link to a saved copy. In 2026 the service has faced regional access restrictions and occasional slowdowns, so availability can vary by location.
What’s inside
The total archive held roughly 500 million saved pages and 700 terabytes of data as of 2021; the collection has continued to grow since then. There are no current published figures, but social media pages make up a substantial portion of the corpus.
API access
TimeMap http://archive.ph/timemap/ <url> ; save POST https://archive.ph/submit/
What we measured
Our own probes, not the archive’s own claims. Re-run periodically; every reading below is dated.
Reachability
- Direct request
- Rate-limited HTTP 429 446 ms
- Through a datacenter proxy
- Rate-limited HTTP 429 2.1 s
- API, direct
- Rate-limited HTTP 429 606 ms
- API, through a proxy
- Rate-limited HTTP 429 898 ms
- API timemap, direct
- Rate-limited HTTP 429 238 ms
- API timemap, through a proxy
- Rate-limited HTTP 429 637 ms
Did a real search return anything?
The request failed · median 10.5 s · down during the run
Slow: budget for long waits, or call it asynchronously.
HTTP 429 on every attempt (direct and proxy).
Benchmark coverage
Found 0 of 3 test items (0%) in the Social cluster. Median response 190 ms.
By how well known the item is: 0/2 well-known, 0/1 mid .
Reachability measured 2026-08-22. Search checked 2026-08-22. Benchmark run 2026-08-22.
Access
May require solving a captcha before it responds.