Website and API gateway
OperationalHTTPS request through the public web endpoint.
Live checks across the services that keep Pingy running.
Database, jobs, delivery and the services behind every check.
HTTPS request through the public web endpoint.
A database query and access to the monitoring registry.
Write/read checks against the Redis stores.
A test job completed by the background worker.
The scheduled health collection completed.
Eligible monitors are being dispatched and returning results on time.
An independent host timer checks progress and performs bounded recovery.
A DNS query through our recursive resolver.
The Apprise gateway responds to its health endpoint.
A test object can be written, read and removed.
A public asset responds through the delivery endpoint.
Browser rendering is tested at each screenshot station every five minutes.
A small browser screenshot test, with an active worker heartbeat.
A small browser screenshot test, with an active worker heartbeat.
12 locations. Each station checks in through an authenticated heartbeat.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.
Recent authenticated contact from this monitoring station.