1‑minute website monitoring and custom check intervals

Uptimia sets the check interval per monitor, with uptime checks from every 30 seconds to once a day. On 30‑second checks an outage goes unseen for 30 seconds at most, against up to 5 minutes on a 5‑minute interval.

Start free trial → See what slow checks miss
30-day free trial No credit card GDPR-ready

Short outages slip between slow checks

If an outage starts and ends between two checks, you get no alert and the monitor's history shows nothing.

On the 30‑second monitor, the outage is on record 20 seconds after it began, whatever alert delay you set. Both checks on the 15‑minute monitor answered up, so its history has no trace of the outage. Choose each interval by what an unseen minute costs on that page. For a checkout that takes orders, that usually means every 30 seconds.

Price a blind minute with the downtime cost calculator →

What sets the time to alert

Only the wait for the next check depends on the interval. Confirmation and the alert delay filter out blips, so a faster interval does not add alerts for failures that clear by themselves.

  • Wait for the next check

    Set by the interval. The wait averages half an interval and can last a whole one. Moving a monitor from 5 minutes to 30 seconds cuts the longest wait by 4 minutes 30 seconds.

    Set per monitor

  • Confirmation round from other locations

    Checked again from elsewhere. The moment a check fails, backup checks from other locations are queued, so a bad route at one checkpoint does not reach you as an alert. You choose 1, 2 or 3 backup checks, and each one must also fail.

    Your choice, 1 to 3

  • Alert delay you set

    A hold from instant to 30 minutes. An outage that ends inside the delay pages nobody, though the incident still goes on record with its duration. Pair a fast interval with a short delay to find outages early without an alert for every blip.

    Yours, 0 to 30 min
A shorter interval shortens only the wait for the next check. Confirmation and the alert delay apply as before, so a single failed check does not send an alert. How false alarms are filtered out → 30 s

Where the interval shows up

You see the pace you pick in the editor, in the summary beside it and in the spacing between rows in the check log.

Check frequency slider

One slider runs from every 30 seconds up to every 24 hours, and the sentence under it reads the setting back before you save. The alert-delay slider sits right below it.

Plain-language summary before you save

Beside the form, a summary describes the monitor in full sentences: its pace, confirmation, locations and who gets alerted. Click a line to jump to the setting behind it.

Check log rows spaced by the interval

Every check lands as a row with its time, result, location and response time. The Gap column here shows the spacing between rows, which is your interval. Open a row for the location, the URL and any error.

Set the check interval on each monitor,from every 30 seconds to once a day.

Checks run from 171+ locations, and website failures are confirmed before you're alerted.

Start your free 30-day trial →
30 days free no credit card cancel anytime
Choosing an interval

Pick the interval by downtime cost

Each monitor has its own interval, so you decide page by page. Put the fastest checks on the pages that take money or sign people in, and let the rest run slower.

  • Revenue paths every 30 seconds. Checkout, sign-in and the API, where an unseen minute is lost orders and support tickets.
  • Brochure pages every 5 minutes. A marketing site or a blog loses little in a few blind minutes.
  • Change it at any time. Tighten the checkout for a launch week and relax it afterwards. The next check uses the new pace.
Price a blind minute with the downtime cost calculator →

Alerts confirmed before anyone is paged

Check frequency, outage confirmation and alert delay are set on each monitor. A 30‑second interval finds an outage early. If the failure clears before backup checks confirm it or before the delay runs out, no alert is sent.

Check frequency per monitor

Set each monitor anywhere from every 30 seconds to once a day. A line under the slider repeats the setting in plain words before you save, and the next check runs at the new pace.

Outage confirmation from backup checks

One checkpoint seeing an error proves little, since the fault may sit on that checkpoint's route. A website failure is confirmed by backup checks from other checkpoints before you're paged, at every interval.

Alert delay for flapping endpoints

Hold the alert back for up to 30 minutes, or send it instantly. With a 30‑second interval and a 2‑minute delay, the outage is still found and recorded early. A cache rebuild that clears in 90 seconds pages nobody.

  • You choose how many must agree. 1, 2 or 3 backup checks, at every interval.
  • What each alert includes. Failing location, error, response, headers and a traceroute.
  • One passing check closes the incident. Everyone alerted gets the all-clear with the outage duration.
How false alarms are filtered out → Explore downtime alerts →
Recovered: one passing check closes it, all-clear to everyone alerted 10 min

Check intervals for each monitor type

Uptime, speed and server monitors go down to 30 seconds. SSL and domain monitors have slower floors, since a certificate or a domain registration changes only when you renew it.

A heartbeat monitor sends no checks of its own. Your job pings Uptimia on its own schedule, and if a ping misses the grace period, an incident opens. Explore cron & heartbeat monitoring → Explore server monitoring → or cron
Locations

Checks spread across your locations

Each check runs from one of the locations you select, out of 171+ in 70+ countries, so consecutive checks usually come from different cities. Every row in the check log shows its checkpoint location.

  • One request per check. At 30 seconds that is 2,880 requests a day, each from one location.
  • Same pace at all hours. The interval does not slow down at night or over a weekend, so an outage at 3 a.m. on a Sunday waits no longer for its first check.
  • Checks pause only for maintenance. They stop for the window you schedule and pick up again when it ends.
Explore multi-location monitoring →
171+ checkpoints in 70+ countries 4 cities

Also included

Heartbeats & cron

For backups and queue workers the job pings Uptimia on its own schedule, an interval from 30 seconds to 90 days or a cron expression, and a missed ping opens an incident once the grace period runs out.

0 2 * * * curl -fsS https://uptimia.com/p/hb_…
expected 02:00grace 30 min
0 2 * * * · grace 30 min

Maintenance windows

Schedule planned work and the monitor's checks pause for the window, so a deploy under 30‑second checks pages nobody.

00:00Window · 02:00 to 03:0024:00
Deploy window → checks paused

Recovery notices

One passing check closes the incident, and the all-clear tells everyone who was alerted how long it lasted.

Checkout is DOWN14:03
Checkout is UPBack up after 10 min

Scheduled reports

Uptime and average response time for every monitor, sent daily, weekly, monthly, quarterly or yearly as PDF, HTML or CSV.

DailyWeeklyMonthlyQuarterlyYearly
Next · Mon 08:00Weekly · PDF

Bulk create at one interval

Paste one URL per line, or url,name pairs, and every new monitor gets the same check frequency, alert delay and confirmation.

https://caldmont.comhttps://shop.caldmont.com,Shophttps://api.caldmont.com… 15 more 18 URLs → every 1 minute

One dashboard for everything

Uptime checks every 30 seconds, daily SSL checks, weekly domain refreshes and a nightly heartbeat can all run in the same account and use the same alerting setup.

checkout.caldmont.comevery 30 sUPTIME caldmont.comevery 24 hSSL caldmont.comevery 7 daysDOMAIN nightly-backup0 2 * * *HEARTBEAT

Example monitors and their settings

Each example lists the monitor settings that fit the case and what Uptimia shows while it happens, from a checkout checked every 30 seconds to a nightly backup that never reports.

Example 1Uptime monitor

Checkout checked every 30 seconds

The payment page stops answering between two checks. The next check runs from Dallas 20 seconds later and is the first to fail. Backup checks from 3 other locations are queued the moment it does.

Monitor settings Check frequencyEvery 30 seconds Outage confirmation3 backup checks Alert delayInstant
What the monitor shows and what happens →
On the monitor
A row lands in the check log every 30 seconds. The Down row is the first check after the outage began, and the incident lists the backup checks that confirmed it.
What happens
With no alert delay, the alert goes out as soon as the backup checks agree, naming the failing location and the error. The recovery notice carries the outage duration.
Example 2Uptime monitor

A 20‑second blip that paged nobody

A search endpoint drops requests for 20 seconds while its cache rebuilds. The 30‑second check lands inside that window and fails. Backup checks from other locations follow, and by the time they run, the endpoint is answering again.

Monitor settings Check frequencyEvery 30 seconds Outage confirmation3 backup checks Alert delayInstant
What the monitor shows and what happens →
On the monitor
The monitor stays Up and no incident is recorded. One backup check that gets a reply is enough to clear a failure that was never confirmed.
What happens
Nobody is paged. Had the backup checks found the endpoint still down, the incident would open and, with no alert delay set, the alert would go out right away.
Example 3SSL monitor

A failed automatic certificate renewal

The automated renewal fails and nobody notices, because the old certificate keeps working. A certificate changes only when you deploy one, so one check a day is enough to watch the date.

Monitor settings Check frequencyEvery 24 hours Expiry alert7 days before
What the monitor shows and what happens →
On the monitor
The first daily check that sees 7 days left raises the expiry alert. A 10‑minute pace would raise it at most a day sooner.
What happens
The alert reaches the monitor's recipients with a week to fix the renewal. Once you renew, the next daily check reads the new expiry date.
Example 4Heartbeat monitor

The nightly backup that never reported

The backup job runs every night and pings Uptimia when it finishes. One night the disk fills and the job dies before the ping. An uptime check would see a healthy site, because nothing it can reach has changed.

Monitor settings Schedulecron 0 2 * * * Grace period30 minutes Failure signalOn
What the monitor shows and what happens →
On the monitor
The schedule runs in your account's timezone. Monday's and Tuesday's pings came in late but inside the grace window. On Wednesday the window runs out with no ping, and the run is marked missed.
What happens
An incident opens when the grace period runs out, and you're alerted as for any outage. If the job catches its own error, it can send a failure signal, which opens the incident without waiting out the grace period.
Explore cron & heartbeat monitoring →

Put 30‑second checks on your checkoutand slower ones on the rest.

Choose the backup checks and the alert delay for each monitor as you add it.

Start your free 30-day trial →
30 days free no credit card cancel anytime

How monitoring intervals work

Uptimia checks each monitor on the interval you set, each check from one of 171+ locations, with uptime checks anywhere from every 30 seconds to once a day. When an uptime check fails, backup checks from other locations confirm it before the alert goes out, and one passing check closes the incident with the outage duration.

01What check interval should I use?+
Base it on what a minute of downtime costs on that page. Revenue paths (checkout, sign-in, your API) deserve 30-second or 1-minute checks. A marketing site is fine at 5 minutes, and internal tools can run hourly. A status page or a docs site gains nothing from 30-second checks.
02How fast will I know my site is down?+
It is the wait for the next check plus the confirmation round plus the alert delay. The wait runs from 0 to 1 interval, half an interval on average. The confirmation round is backup checks from up to 3 other locations, queued the moment the first failure lands and picked up by other probes as they free up. The alert delay is 5 minutes by default when you create a monitor in the editor, or instant if you set it to 0. The interval changes only the first part. On 5-minute checks, an outage can be 5 minutes old before the first check fails.
03Which plans include 30-second checks?+
30-second intervals are available from the Professional plan, and on the 30-day trial. Basic checks as often as every minute; the free plan monitors 1 website at 5-minute intervals. Speed monitors follow the same ladder, with a 5-minute floor on Basic.
04Will frequent checks put load on my site?+
Each check is one request to the URL you set, from one location. At 30-second intervals that is 2,880 requests a day. If a page must stay untouched, give that monitor a slower pace. The interval is per monitor.
05How do I change the interval on an existing monitor?+
Move the Check frequency slider on the monitor's settings. The line under it reads the new pace back ("Check for problems every 30 seconds"), and the next check after you save uses it. Monitors created in bulk start with one shared frequency and can each be changed afterwards.
06Can I be alerted only if the failure lasts?+
Yes. The alert delay holds the notification until a failure has lasted as long as you choose, from instant up to 30 minutes, and it defaults to 5 minutes when you create a monitor in the editor. An outage that ends inside the delay pages nobody and sends no recovery notice either, though the incident stays on record.
07Does a faster interval cause more false alarms?+
Not on its own. An uptime failure is confirmed by backup checks from other locations before the incident opens and the alert goes out, whatever the interval. The default is 3 backup checks; you can lower that to 2 or 1 under Outage confirmation on the monitor's Advanced tab, which confirms sooner but lets more single-route blips through. API monitors count the first failed run in that number, so 1 means no re-check. A single passing check closes an outage.
08How many checks a month does each interval make?+
Over a 30-day month, 30-second checks make 86,400; 1-minute checks 43,200; 5-minute checks 8,640; 15-minute checks 2,880; hourly checks 720; and a daily check 30. Plans count monitors, so none of these numbers changes your bill.
09Why can SSL, domain and virus monitors not run every 30 seconds?+
What they watch changes only when you deploy. An SSL monitor checks every 10 minutes at the fastest and every 24 hours at the slowest, and warns a set number of days before expiry (7 by default). A domain monitor refreshes the WHOIS record every 1 to 9 days, which is plenty for an expiry date known a year ahead. A virus monitor scans every hour to once a week, daily by default.
10What is the fastest interval for API and transaction monitors?+
An API monitor runs a multi-step request sequence, so its fastest pace is every minute, up to every 24 hours. A transaction monitor drives a real browser through a whole journey (sign in, add to cart, pay), so it runs every 10 minutes at the fastest, 30 minutes by default. Put an uptime monitor at 30 seconds on the same URL when you also need to know the page answers.
11Does the server agent have an interval?+
Yes. The agent on your Linux, macOS or Windows host reports every 30 seconds by default, and you can set 60, 120 or 300 seconds instead. Silence for 3 reports in a row opens an offline incident, so at the default a dead host is flagged after 90 seconds of silence.
12What about monitoring cron jobs on a schedule?+
Use a heartbeat monitor. Your job pings Uptimia when it runs, on an interval from 30 seconds to 90 days or on its own cron expression, and you are alerted when the ping fails to arrive within the grace period (2 minutes by default). Use it for jobs such as a nightly backup, where the site looks fine even when the job did not run.
13Do DNS and blacklist monitors have an interval?+
A DNS monitor queries your nameservers on a fixed 5-minute sweep, so a record change is seen within 5 minutes. A blacklist monitor checks the lists every 15, 30 or 60 minutes, which you pick per monitor, since a listing lasts hours.

Give every monitor its own interval.

Website failures are confirmed from other locations before anyone is paged.

Start free trial →
30-day free trial Uptime checks from 30 s to 24 h Confirmed before alerting No credit card
Change a monitor's pace whenever you like. The next check uses it.