←  Back to Blog
September 16, 2016

August 2016 Crawl Archive Now Available

The crawl archive for August 2016 is now available! The archive contains more than 1.61 billion web pages.

The crawl archive for August 2016 is now available! The archive located in the commoncrawl bucket at crawl-data/CC-MAIN-2016-36/ contains more than 1.61 billion web pages.

To extend the seed list, we've added 50 million hosts from the Common Search host-level pagerank data set. While many of these hosts may already be known, and some may not provide crawlable content, the number of crawled hosts has grown by 18 million (or 50%) and there are 8 million more unique domains (plus 35%).

Together with the August 2016 crawl archive we also release two data sets containing robots.txt files and responses without content (404s, redirects, etc.). More information can be found in a separate blog post.

Data Type File List #Files Total Size
Compressed (TiB)
Segments segment.paths.gz 100
WARC warc.paths.gz 29800 26.78
WAT wat.paths.gz 29800 9.57
WET wet.paths.gz 29800 4.23
Robots.txt files robotstxt.paths.gz 29800 0.28
Non-200 responses non200responses.paths.gz 29800 0.81
URL index files cc-index.paths.gz 302 0.1
Columnar URL index files cc-index-table.paths.gz 900 0.14

To assist with exploring and using the dataset, we provide gzipped files that list:

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-2016-36/.

For more information on working with the URL index, please refer to the previous blog post or the Index Server API. There is also a command-line tool client for common use cases of the url index.

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 and packages.

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: 

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: 

No Truncation Indicator in WARC Records

Originally reported by: 
Henry Thompson
More details
Due to an issue with our crawler, not all truncations were indicated correctly. A workaround to detect length truncation is to be suspicious if the length of the content is exactly 1048576 bytes. Truncations for time or network do not have such a workaround. In the WARC files this indicator is called "WARC-Truncated".

Erratum: 

Missing content_truncated flag in URL indexes

Originally reported by: 
More details
The flag in our URL indexes (CDX and columnar) that indicates whether or not a WARC record payload was truncated was added in CC-MAIN-2019-47. This indicator is missing in our indexes for all previous crawl releases. In the CDX index this is referred to as "truncated", and the columnar index refers to this as "content_truncated".

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: 

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: 

Incorrect fetch_time metadata

Originally reported by: 
More details
The fetch_time metadata for robots.txt might be incorrect in some crawl releases.

Erratum: 

Charset Detection Bug in WET Records

Originally reported by: 
Javier de la Rosa
More details
The charset detection required to properly transform non-UTF-8 HTML pages in WARC files into WET records didn't work before November 2016 (CC-MAIN-2016-50) due to a bug in IIPC Web Archive Commons.

Erratum: 

Missing Language Classification

Originally reported by: 
More details
Starting with crawl CC-MAIN-2018-39 we added a language classification field (‘content-languages’) to the columnar indexes, WAT files, and WARC metadata for all subsequent crawls.