Docket CacheDocket Cache By The Numbers
We often wonder what kind of sites use Docket Cache. We cannot see most of them, and we do not want to. But WordPress.org shares a few totals, and sites that connect to Cronbot send us a few details with each ping. Together they give us a small picture.
All numbers in this post are from 16 October 2026. We show totals and percentages only, never a site address.
On WordPress.org#
Docket Cache was first published on WordPress.org on 8 July 2020.
- 20,000+ active installs. WordPress.org rounds this number down, so the real number is somewhere above it.
- 431,592 downloads in total, counting every update.
- 49 of 50 ratings are five stars.
Thank you to everyone who took the time to leave a rating.
Sites connected to Cronbot#
The rest of this post only covers sites connected to Cronbot, not every site that runs Docket Cache.
The Cronbot server knows about 23,506 sites. These are sites that have connected at some time since Cronbot started.
3,453 of them are connected now, which is about 15%. The rest have disconnected, removed Docket Cache, or no longer exist. Compared with the 20,000+ active installs, fewer than one site in five uses Cronbot. It is optional, and most sites run without it.
99.2% of the connected sites are single sites. Only 25 are multisite networks.
Docket Cache versions#
| Version | Sites | Share |
|---|---|---|
| 26.04.x | 2,919 | 84.5% |
| 24.07.x | 419 | 12.1% |
| 23.08.02 | 62 | 1.8% |
| Other | 53 | 1.5% |
Most sites keep Docket Cache up to date, which is good to see. The most common version was 26.04.08, on 1,037 sites.
Only 12.5% were on 26.04.10 or 26.04.11, the versions with the latest security fixes. That is not a surprise, because those versions were only one and two days old at the time. But about one site in seven still runs a version from 2024 or older. If yours is one of them, please update. Our post Why Docket Cache No Longer Unserializes Strings explains the most important fix.
WordPress versions#
| WordPress | Sites | Share |
|---|---|---|
| 7.1 | 2,665 | 77.2% |
| 7.0 | 208 | 6.0% |
| 6.9 | 180 | 5.2% |
| 6.8 | 126 | 3.6% |
| 6.7 | 28 | 0.8% |
| Other | 246 | 7.1% |
Two out of three connected sites (66.2%) run WordPress 7.1.3, the most common version by far. About half of the rest are on another 7.0 or 7.1 release. A small number still run WordPress 6.7 or older.
Where the sites are#
Cronbot only knows the timezone set in Settings > General, so this is a rough picture.
- 28.4% use
+00:00. This is the WordPress default, so many of these sites have simply never changed it. - 19.6% use a European city, led by Berlin, London, Paris, Amsterdam, Rome and Warsaw.
- 13.9% use a city in the United States or Canada, led by New York, Chicago, Toronto and Los Angeles.
- 10.6% use a fixed offset other than
+00:00, such as+03:00or+02:00.
The rest are spread across many more timezones.
How many sites answer#
Each time Cronbot pings a site, it notes the HTTP status code of the answer.
| Answer | Sites | Share |
|---|---|---|
| 200, OK | 3,009 | 87.1% |
| No answer | 176 | 5.1% |
| 404, not found | 137 | 4.0% |
| 403, forbidden | 69 | 2.0% |
| 500, server error | 24 | 0.7% |
| Other | 38 | 1.1% |
Most sites answer every ping. About one site in eight did not answer the last ping with OK. When a site does not answer, Cronbot waits longer before the next ping, so it does not keep knocking on a door that is closed.
If your site is connected and the Cronbot screen shows an error, these are the usual places to look.
- 403. A firewall, a security plugin or your host may be blocking the ping.
- 404. The site may have moved to a new address, or the ping no longer reaches WordPress.
- No answer. The site may be down, or too slow to answer in time.
Thank you#
Every one of these sites chose to connect, and that helps us keep Cronbot running and improve Docket Cache. Thank you.
If you do not use Cronbot and you are not sure whether you need it, our post Docket Cache On Shared Hosting explains when it helps.