←  Back to Blog
March 4, 2020

February 2020 crawl archive now available

The crawl archive for February 2020 is now available! It contains 2.6 billion web pages or 240 TiB of uncompressed content, crawled between February 16th and 29th. It includes page captures of 1 billion URLs unknown in any of our prior crawl archives.

The crawl archive for February 2020 is now available! It contains 2.6 billion web pages or 240 TiB of uncompressed content, crawled between February 16th and 29th. It includes page captures of 1 billion URLs unknown in any of our prior crawl archives.

Data Type File List #Files Total Size
Compressed (TiB)
Segments segment.paths.gz 100
WARC warc.paths.gz 56000 49.28
WAT wat.paths.gz 56000 17.98
WET wet.paths.gz 56000 7.97
Robots.txt files robotstxt.paths.gz 56000 0.22
Non-200 responses non200responses.paths.gz 56000 2.21
URL index files cc-index.paths.gz 302 0.20
Columnar URL index files cc-index-table.paths.gz 897 0.24

Improvements and Fixes

The HTTP headers in WARC response records have been fixed: the HTTP response status line now has a white space following the status code if the reason-phrase is empty. E.g., if a server sends an empty message (instead of “OK”), the status line will include a trailing space character: “HTTP/1.1 200 ”. Following RFC 7230 the white space between status code and message is mandatory. Please refer to the bug report NUTCH-2763 for further details.

Archive Location and Download

The February crawl archive is located in the commoncrawl bucket at crawl-data/CC-MAIN-2020-10/.

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.

The Common Crawl URL Index for this crawl is available at: https://index.commoncrawl.org/CC-MAIN-2020-10/. 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: 

Columnar Index Subsets with Fewer than 900 Partitions per Crawl

Originally reported by: 
Sebastian Nagel
More details
Older crawls from CC-MAIN-2013-20 including CC-MAIN-2016-30 do not have the robotstxt and crawldiagnostics subset partitions in the Columnar Index.

Erratum: 

WARC-Target-URI May Include Non-ASCII Characters

Originally reported by: 
More details
The WARC-Target-URI header in WARC record, but also corresponding WAT, WET and URL index records may include non-ASCII characters, not encoded using percent-encoding or Punycode.

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