How to Monitor Website Uptime from Your iPhone

By Paul Snyman · Published · 9 min read

You launched a side project. Or you run a small business website that brings in real revenue. Or you maintain an internal tool that the team relies on every day. In all of these cases, you want to know the moment something goes down - not when a customer emails you, not when you happen to refresh the page, but the instant your monitoring catches the problem.

Traditionally, uptime monitoring meant signing up for a SaaS dashboard, configuring webhooks, and learning yet another tool. This guide shows you how to do it with push notifications going directly to your iPhone home screen, using PingKit Uptime Watch. The checks themselves run server-side from PingKit's backend, every five minutes with Guardian or once an hour for the free target. Your iPhone only adds and views the targets it watches, and the push alert reaches your iPhone when one of them changes state; the free Mac Agent keeps a separate list of its own.

What Uptime Monitoring Actually Does

An uptime monitor performs three things on a schedule:

  1. Sends an HTTP request to a URL you specify. Usually a GET request to your homepage, status endpoint, or health check.
  2. Checks the response. Did it return in time? Is the status code in the expected range (typically 200–299)? Does the body contain the expected content?
  3. Records the result and notifies you on failure. Successes go into a history log. Failures trigger a push notification.

That is the entire job. The value is not in the technology - HTTP requests are trivial - it is in the discipline of doing it consistently and surfacing the results where you will actually see them.

Why iPhone Monitoring Beats a Dashboard You Never Open

Most outage detection failures are not technical. They are attentional. The Grafana dashboard is open in a tab nobody is looking at. The SaaS monitoring service emails you, but the email lands in a folder you scan once a day. By the time you notice, the outage has been visible to users for an hour.

A push notification on your iPhone arrives in the only place you actually pay attention to. The lock screen. The notification banner. The badge on the app icon. You will see it within seconds, regardless of what device you are at, regardless of whether your laptop is open. For a solo founder, indie developer, or small team, this is the right level of monitoring.

What to Monitor

Start with the smallest set of endpoints that actually matter:

Resist the urge to monitor everything. Five well-chosen endpoints with frequent checks beat fifty endpoints checked rarely. Each false alarm reduces your willingness to react to the next one.

How Often Uptime Watch Checks Run

Uptime Watch does not ask you to pick an interval; the interval comes with your tier. With Guardian, each of up to ten targets is checked every five minutes. The free target is checked once an hour. Either way the check runs server-side from PingKit's backend, a scheduled job that sends a request to every target, whether it was added on an iPhone or in the Mac Agent. Neither app performs the check itself; each keeps its own list of targets and shows their results. When a target you added on your iPhone changes state, from up to down or back again, your iPhone gets a push notification; targets added in PingKit Agent alert on the Mac with Guardian, while the Mac is awake.

A five-minute cadence will not reliably catch a 90-second blip, an hourly one even less so, and neither is a substitute for the one-minute, multi-region checks a dedicated SRE platform offers. What it is good at is the thing most solo developers and small teams actually need: knowing within minutes on Guardian, or within the hour on the free tier, that a site is down, without babysitting a dashboard or configuring anything.

What Counts as "Down"?

Not every non-200 response is an outage. A useful monitor distinguishes:

Step-by-Step: Set Up Uptime Watch on iPhone

  1. Install PingKit from the App Store.
  2. Optionally subscribe to Guardian ($2.99/month or $24.99/year on iPhone) for ten targets, five-minute checks, TCP port checks, keyword checks and 30 days of history. Your first URL is watched free without it.
  3. Optionally install the free PingKit Mac Agent on a Mac. It keeps its own Uptime Watch list, separate from your iPhone's, and its checks also run on PingKit's servers; alerts for the Mac's targets appear on the Mac with Guardian, while it is awake.
  4. Open the Monitor tab and tap into Uptime Watch.
  5. Add your first endpoint. Enter the full URL (including https://) and pick a friendly name. With Guardian you can instead choose Port (TCP) and enter a public host and port, or add a keyword or expected status code to a website target.
  6. Enable push notifications when prompted. Without this, alerts do not reach you.
  7. Repeat for each endpoint. Add the homepage, health check, and any other critical URLs.
  8. Test the alert. Watch a page you control, wait until Uptime Watch shows it up, then take it offline: Uptime Watch checks again 30 seconds after a failure and, if it is still down, notifies you, within about five minutes on Guardian or within the hour on the free tier. A target that is already down when you add it shows as down but sends no alert.

Reading the Uptime History

After a few days, the history view starts to be useful. Each target has an hourly response-time chart covering its full history (7 days on the free tier, 30 days with Guardian), with red marking any hour that had a failed check. Look for:

One Uptime Watch target in PingKit for iPhone, with thirty days of hourly response times charted and the hours with a failed check marked.
One target in Uptime Watch on iPhone: thirty days of hourly response times, with the hours a check failed marked.

What Uptime Watch Does Not Replace

For a solo developer or small team, Uptime Watch is enough. For larger operations you will eventually want:

Uptime Watch fills the gap between "I have nothing" and "I have a full SRE platform". For a very large set of users, that gap is the right place to be.

The Real Win: Knowing Your Actual Uptime Number

Most small site owners overestimate their uptime. The site feels fine when they check it, so they assume it is always fine. After a month of automated monitoring, the real number is often 98% - meaning roughly 14 hours of cumulative downtime that nobody noticed.

This number is the data you need to make decisions: switch hosting providers, move to a CDN, harden a deployment process, or accept that 98% is fine for your use case. Without measurement, you are guessing.

Conclusion

Uptime monitoring used to be a hosted service you paid for and never opened. With PingKit Uptime Watch, it is a feature that pushes an alert to your iPhone once a second check confirms something went wrong. Add the URLs that matter and let the alerts come to your iPhone, no dashboard, no interval to configure.

Related Articles

Get Notified the Moment Your Site Goes Down

Uptime Watch checks one endpoint free every hour, or ten every five minutes with Guardian, from PingKit's backend and pushes alerts straight to your iPhone when something changes.

Download Free on the App Store