←  Back to Blog
December 14, 2022

November/December 2022 crawl archive now available

The crawl archive for November/December 2022 is now available! The data was crawled November 26 – December 10 and contains 3.35 billion web pages or 420 TiB of uncompressed content. Page captures are from 44 million hosts or 34 million registered domains and include 1.2 billion new URLs, not visited in any of our prior crawls.

The crawl archive for November/December 2022 is now available! The data was crawled November 26 – December 10 and contains 3.35 billion web pages or 420 TiB of uncompressed content. Page captures are from 44 million hosts or 34 million registered domains and include 1.2 billion new URLs, not visited in any of our prior crawls.

Data Type File List #Files Total Size
Compressed (TiB)
Segments segment.paths.gz 100
WARC warc.paths.gz 88000 92.59
WAT wat.paths.gz 88000 22.89
WET wet.paths.gz 88000 9.58
Robots.txt files robotstxt.paths.gz 88000 0.15
Non-200 responses non200responses.paths.gz 88000 2.43
URL index files cc-index.paths.gz 302 0.25
Columnar URL index files cc-index-table.paths.gz 900 0.28

Archive Location and Download

The November/December crawl archive is located in the commoncrawl bucket at crawl-data/CC-MAIN-2022-49/.

To assist with exploring and using the dataset, we provide gzipped files which list all segments, WARC, WAT and WET files.

By simply adding either s3://commoncrawl/ or https://data.commoncrawl.org/ to each line, you end up with the S3 and HTTP paths respectively, please see accessing the data for detailed instructions.

The Common Crawl URL Index for this crawl is available at: https://index.commoncrawl.org/CC-MAIN-2022-49/. Also the columnar index has been updated to contain this crawl.

Please donate to Common Crawl if you appreciate our free datasets! We’re also seeking corporate sponsors to partner with Common Crawl for our non-profit work in open data. Please contact info@commoncrawl.org for sponsorship information.

This release was authored by:
No items found.

Erratum: 

WARC Content-Type header in revisit records

Originally reported by: 
Sebastian Nagel
More details
Common Crawl's WARC revisit records use Content-Type: message/http (following the WARC 1.1 spec's example), but per iipc/warc-specifications#55 it should be application/http;msgtype=response for consistency with other HTTP response records.

Erratum: 

Redirect target URL in URL indexes may be a relative URL

Originally reported by: 
Sebastian Nagel
More details
When the HTTP “Location” header includes a relative URL, the corresponding “redirect” field in the CDX index and “fetch_redirect” field in the columnar index will also store a relative URL. In all other cases, redirect targets in the URL indexes should be recorded as absolute URLs.

Erratum: 

Content is truncated

Originally reported by: 
More details
Some archived content is truncated due to fetch size limits imposed during crawling. This is necessary to handle infinite or exceptionally large data streams (e.g., radio streams). Prior to March 2025 (CC-MAIN-2025-13), the truncation threshold was 1 MiB. From the March 2025 crawl onwards, this limit has been increased to 5 MiB.

Erratum: 

SURT URLs do not properly encode non-UTF-8 percent-encoded characters

Originally reported by: 
Tom Morris
More details
When constructing SURT (Sort-friendly URI Reordering Transform) URLs, percent-encoded characters that are not valid UTF-8 sequences were not being correctly handled. This could lead to inconsistencies in URL normalization and sorting, potentially causing incorrect deduplication or retrieval issues in datasets that rely on SURT-based indexing.

Erratum: 

WAT data: repeated WARC and HTTP headers are not preserved

Originally reported by: 
More details
Repeated HTTP and WARC headers were not represented in the JSON data in WAT files.

Erratum: 

WARC revisit metadata records

Originally reported by: 
More details
The revisit records in the Common Crawl WARC archives (since Aug 2018) lack the metadata record which is attached to all response records.

Erratum: 

Erroneous title field in WAT records

Originally reported by: 
Robert Waksmunski
More details
The title field in WAT record is extracted from last but not first <title> element in an HTML page

Erratum: 

Some 2–Level CCTLDs Excluded

Originally reported by: 
More details
A bad configuration was checked into our exclusion list on Sep 22, 2022 and was fixed on Oct 27, 2023. The configuration blocked a number of 2–level domains, meaning they were not included in certain crawls.