The crawl archive for September/October 2023 is now available! The data was crawled Sept 21 – October 5 and contains 3.4 billion web pages or 456 TiB of uncompressed content. Page captures are from 43 million hosts or 34 million registered domains and include 1.2 billion new URLs, not visited in any of our prior crawls.
Archive Location and Download
The September/October crawl archive is located in the commoncrawl bucket at crawl-data/CC-MAIN-2023-40/.
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.
Erratum:
Redirect target URL in URL indexes may be a relative URL
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.
Additional information about this issue and the fix is available in this GitHub issue.
Erratum:
Content is truncated
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.
For more details, see our truncation analysis notebook.
Erratum:
SURT URLs do not properly encode non-UTF-8 percent-encoded characters
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. This was addressed in commoncrawl/nutch@6b2d9ea.
Erratum:
WAT data: repeated WARC and HTTP headers are not preserved
Repeated HTTP and WARC headers were not represented in the JSON data in WAT files. When a header was repeated adding a further value of that header, only the last value was stored and other values were lost. This issues was fixed with CC-MAIN-2024-51, see ia-web-commons#18. All WAT files from CC-MAIN-2013-20 until CC-MAIN-2024-46 are affected.
Erratum:
WARC revisit metadata records
The revisit records in the Common Crawl WARC archives in all crawls from CC-MAIN-2018-34 to CC-MAIN-2024-46 (since Aug 2018) lack the metadata record which is attached to all response records. Fixed with CC-MAIN-2024-51, see commoncrawl/nutch#33. Note: before CC-MAIN-2018-34, WARC revisit records were not stored at all.
Erratum:
Erroneous title field in WAT records
The "Title" extracted in WAT records to the JSON path `Envelope > Payload-Metadata > HTTP-Response-Metadata > HTML-Metadata > Head > Title` is not the content included in the <title> element in the HTML header (<head> element) if the page contains further <title> elements in the page body. The content of the last <title> element is written to the WAT "Title". This bug was observed if the HTML page includes embedded SVG graphics.
The issue was reported by the user Robert Waksmunski:
- https://groups.google.com/g/common-crawl/c/ZrPFdY3pPA4/m/s5D_8wCJAAAJ
- WAT extractor: Document title bug ia-web-commons#36
...and was fixed for CC-MAIN-2024-42 by commoncrawl/ia-web-commons#37.
This erratum affects all crawls from CC-MAIN-2013-20 until CC-MAIN-2024-38.
Erratum:
Some 2–Level CCTLDs Excluded
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.
The excluded CCTLDs were:
We apologize for this mistake, and that it took us a while to find it.
.svg)
