WP Packages Now Has a Public Status Page

WP Packages processes over 76,000 WordPress plugins and themes every 5 minutes, syncing metadata from the WordPress.org API, building Composer repository artifacts, and deploying them to our CDN. We also run hourly status checks against every package to detect closures and re-openings.

All of this happened behind the scenes hidden behind a gated admin. Today we’re making it visible with a public status page.

What’s on the status page

The status page has three summary cards showing total packages, Composer install counts, and 24-hour activity (packages updated, deactivated, and reactivated). Below that, two tabs show detailed history:

Builds — Every 5-minute build with package counts, changed packages, duration breakdowns, and R2 CDN sync status. Builds with changes are expandable. Click a row to see exactly which packages were updated or deleted, with links to each package’s detail page or WordPress.org for deleted packages.

Status Checks — Hourly re-checks of all packages against the WordPress.org API to detect closures and re-openings. When plugins are closed or reopened on WordPress.org, the status check picks it up and the affected packages are listed in the expandable row.

Why transparency matters

If you’re relying on WP Packages for production deployments, you should be able to verify that the system is healthy without asking us. The status page answers the questions that matter: when was the last build, what changed, and are packages being kept up to date.

This is also useful for investigating specific packages. If a plugin was recently closed on WordPress.org, you can see exactly when our system detected it and deactivated the package.