Skip to content

System health

Platform Status

Freshness of the live index, the public stats snapshot and the industry feed, and how much of the catalog the rolling alive re-check has covered — each measured against what it is expected to hold.

Current verdictAll systems operational
Page refreshEvery 5 minutes
Times shown inUTC

Live index freshness

Catalog writes

1msince refresh

214,707 tracked

13 Aug · 21:25 UTC

Healthy

Alive re-check

Rolling re-verification of listings already in the index

5dsince refresh

95% of the catalog re-checked · 203,844 of 214,707

9 Aug · 02:21 UTC

Healthy

Public stats snapshot

The numbers every public surface reads

1msince refresh

1,626/day · 24h intake 4,443

13 Aug · 21:27 UTC

Healthy

Industry Updates

RSS, GitHub, status pages, doc diffs

6msince refresh

Feed daemon last completed a full pass

13 Aug · 21:21 UTC

Healthy

Active issues

Every monitored surface refreshed inside its window. This view has no history — it reports the state of the last successful snapshot at page build time.

Changelog

Changes to what a listing says or whether it qualifies, and incidents once they are closed. Starts 15 Jul 2026 — the record is not reconstructed further back than it is reliable.

  1. Method
    Listings nobody has checked now say so

    A listing's lifecycle read “Alive” whenever it was not known to be dead, which covered every record no liveness check had reached — the great majority of the catalog. Those now read “Unverified”. Only a positive finding says “Alive”.

  2. Method
    “None confirmed dead” instead of “0 dead”

    The pool line reported a dead count of zero, which reads as a completed census that found no casualties. Nothing has been confirmed dead yet, and the line now says that instead.

  3. Method
    Peer lists name what produced them

    The section under a listing was headed “Similar apps” whether it came from a nearest-neighbour match on what the projects do or from a fallback that lists the same category. The two are different claims, and the heading now distinguishes them.

  4. Incident
    Listing imagery served through an open proxy — closed

    Icons and preview images were resized by an image optimizer configured to accept any URL from anyone, so third parties could drive it at our expense. It now serves only imagery belonging to records in this catalog, fetched by us rather than by your browser. Visible effect: a listing whose icon is over 250 kB falls back to its lettermark tile.

  5. Method
    Listing bar widened to data completeness

    Whether a listing qualifies for public surfaces now takes the completeness of its record into account, not only its identity. Google Play surfaces are excluded from that pool.

  6. Method
    Thin records excluded from the sitemap

    Records without enough description to be worth a page are kept out of the sitemap, in step with the same quality tier that governs indexing.

What the labels mean

Healthy
The latest successful public snapshot is inside the expected freshness window for that surface.
Delayed
The surface is behind its expected cadence but still recent enough to read with caution.
Stale
The latest timestamp is missing or materially older than the threshold for that surface.
Partial
A rolling job has covered some of the catalog but not most of it — read its figure, not its badge.
Not running
The job has not covered any of the catalog. Nothing it would report can be inferred from its silence.

An age label says how long it has been since PulseGate last refreshed that surface successfully. It does not imply source-side uptime, and it does not guarantee the underlying third-party source changed at the same moment.