Status
loremfile.dev has no server, so there is nothing to host a live status page on. Instead, the project checks production from the outside, the same way you reach it, and writes down what it finds where anyone can read it.
Every day
A scheduled job checks the headers every published file must carry. It downloads a rotating tenth of the files, and everything from the newest release, and compares their bytes with the SHA-256 hashes in the manifest; on Mondays it downloads and hashes every file. It fetches every page and discovery file of this website and compares them with a fresh build of the same commit, so a page that changed without a deploy is noticed. It also checks that the domain registration, the TLS certificate and security.txt are not close to expiring.
Who is asking
The checks say who they are. Every day, after each deploy and when a release archive is made, they send loremfile-verify/0.1.0 (+https://loremfile.dev/status). The probe that tests the rules at the edge after a change sends loremfile-probe/0.1.0 (+https://loremfile.dev/status). The checks also send the names of some AI crawlers to the two legal pages, on purpose, to confirm they are refused.
When a check fails
A failing check opens a GitHub issue labelled health, adds a comment on every further failing day, and closes the issue on the first clean run. If there is no open issue, the last check passed.