Monitoring Whether Your Published Site Is Actually Reachable
Every published Piskes site is now checked for reachability from outside the platform every 15 minutes, no separate uptime service required.
Every site published on Piskes Website Builder is now checked for reachability automatically, every 15 minutes, from outside the platform — the same category of monitoring you'd otherwise pay a separate uptime service to run.
Why "from outside" matters
A check that never actually leaves Piskes' own infrastructure only tells you the platform's opinion of itself. This check runs from the website-builder app specifically because it's the one part of the platform configured to reach the public internet for real, rather than having internal requests short-circuited — so when it checks whether your site is reachable, it's asking the same question a visitor's browser would ask, not a question answered from inside the building.
Kept separate from domain configuration checks
This uptime check runs alongside — but independently from — a second scheduled check that reconciles every customer domain's configuration. They're deliberately two separate jobs: one measures whether the app and render path are working, the other measures every domain's setup, and a failure in one was never meant to stop the other from running.
What this means for you
If your published site goes unreachable — a DNS problem, an outage, anything that would stop a visitor from loading it — it's now something the platform is actively watching for in the background, not something you only find out about when a customer mentions it.
No setup is required; this runs automatically on every published site starting now.