Monitoring services

Everything is built around one job: helping you understand when a site is failing.

Uptime Basics keeps the service lineup focused. You get recurring website checks, slow response alerts, incident visibility, alert history, SSL and domain monitoring, public status pages, and a customer dashboard that stays readable when something goes wrong.

Service coverage

Monitoring stack

Live
1
Add monitor
HTTP or HTTPS target with plan-based interval.
2
Collect checks
Store timing, status, slow response events, incidents, and alert activity.
3
Respond faster
Review incidents, notify stakeholders, and publish a status page if needed.

HTTP and HTTPS checks

Monitor websites with recurring checks, track response codes, and keep detailed logs for troubleshooting.

Alerting and incident visibility

Get downtime and recovery alerts, then review the incident timeline instead of relying on guesswork.

Slow response alerts

Catch performance problems when a website is still online but responding slower than your chosen threshold.

SSL, domain, and public status

Watch certificate and renewal risk, and optionally share a monitor-backed public status page.

Website Monitoring

HTTP and HTTPS uptime monitoring for the sites you actually care about.

Every monitor starts with a URL. Uptime Basics then checks it on the interval your plan allows, records healthy and failed responses, and keeps the history available from the dashboard and monitor detail view.

This is useful when you need a straightforward answer to the question, “Was the site really down, or was it just slow for one user?”

  • Plan-based check intervals from 5 minutes down to 1 minute
  • Detailed logs available per monitor
  • Response time tracking for historical context
  • Optional slow response thresholds
Monitor detail

shop.example.com

Up
1 minPro check interval
164 msLatest response time
99.97%7-day uptime
3 incidentsRecent reliability summary
Slow Response Alerts

Know when a site is technically up but too slow for customers.

Not every website problem is a full outage. A page can still return a healthy status code while taking long enough to hurt conversions, support volume, trust, and user experience.

Slow response alerts are tracked separately from downtime, so a performance issue does not falsely reduce uptime percentage or get treated like a full outage.

  • Set a per-monitor response time threshold
  • Require consecutive slow checks before alerting
  • Keep performance warnings separate from downtime incidents
  • Review slow events from the monitor and incident pages
Performance alert

checkout.example.com

Slow
3 secAlert threshold
3Consecutive slow checks
4.8 secLatest response
UpDowntime status unchanged
Slow check observed
Response exceeded threshold
10:32 AM
Performance alert queued
Separate from downtime alerting
10:34 AM
Alerts And Recovery

Alerts are useful only if they are credible and easy to follow.

Uptime Basics confirms failures before opening an incident. That reduces alert noise while still giving you prompt downtime and recovery notifications when a monitor genuinely changes state.

The alert history remains tied to the monitor, so if a site flaps or a client asks what happened, you have a clean record available.

  • Downtime and recovery alerts
  • Slow response warnings handled separately
  • Alert history visible on the monitor detail page
  • Multiple checks before incident creation
Alert flow

client-api.example

Incident
Failed checks confirmed
Incident opened
10:04 AM
Downtime alert queued
Email notification
10:05 AM
Recovery alert queued
Healthy response restored
10:21 AM
Incident History

Review what happened instead of relying on rough memory after the outage ends.

Incidents keep their own activity log. That means you can review when the incident opened, how long it lasted, whether alerts were queued, and what the checks looked like around recovery.

This is especially useful for customer reporting, vendor escalation, and understanding whether the failure was brief, repeated, or sustained.

  • Incident-specific activity history
  • Response time trends and uptime timelines
  • Detailed logs separated from the main dashboard
Incident review

status timeline

Resolved
11:03 AM
Incident opened after confirmed failures
down
11:09 AM
Failed checks grouped in activity log
ongoing
11:17 AM
Healthy response restored
resolved
SSL And Domain Monitoring

Prevent avoidable outages caused by expired certificates or forgotten renewals.

Websites can be “up” while still presenting a certificate problem or sitting too close to a domain expiry date. These checks are optional, but they are often the easiest problems to prevent once they are visible.

Each monitor can have its own warning thresholds so the right sites get the right amount of lead time.

  • Optional SSL expiry checks
  • Optional domain expiry checks
  • Per-monitor warning thresholds
Renewal tracking

agency-client.com

On
14 daysSSL warning lead time
30 daysDomain warning lead time
42 daysCertificate remaining
88 daysDomain remaining
Public Status Pages

Share a public-facing status page without exposing the rest of the customer dashboard.

Some incidents need an external page you can share with customers or stakeholders. Public status pages use monitor data you already have, can be owner-verified, and stay separate from private account information.

You decide when to enable them and which sections appear. That keeps them useful without forcing every monitor to become public.

  • Enabled per monitor
  • Optional owner verification workflow
  • Recent history, incident, and response sections can be configured
Public status

status.uptimebasics.com/client-site

Shared
Current status
Publicly visible summary
Up
Verification
Supports DNS, file, or meta check
Owner verified
Visibility
Recent history and uptime timeline
Configured
Dashboard And Logs

A customer dashboard that stays readable when you are checking multiple sites.

The dashboard is designed to answer the immediate operational questions first: which monitors are up, down, or paused, what the recent uptime looks like, and whether there is a current incident that needs attention.

From there you can drill into the monitor detail page, incident history, alert log, and exported raw checks only when you need that extra detail.

  • Overview cards for monitor health
  • Detailed monitor pages with response time and uptime views
  • Paginated detailed logs for deeper troubleshooting
Customer dashboard

Operational view

Ready
10Monitors
9Up
1Down
Functionally Useless
HTTP monitor | Up for 4d 12h
165 ms
Client Storefront
HTTP monitor | Incident open
503
Plan Comparison

Choose the monitoring coverage that fits how many sites you manage.

Every plan includes the core uptime monitoring workflow. Higher plans add more monitors and a controlled number of 1-minute checks for the sites where faster detection matters most.

Starter For small sites and simple portfolios.
$4.99 / month
  • 10 monitorsTrack websites, landing pages, client sites, or internal tools.
  • 5-minute checksReliable coverage without overcomplicating a first setup.
  • Email alertsDowntime and recovery notifications when monitor state changes.
  • Incident historyReview outages, response codes, response time, and recovery events.
Pro For higher-priority sites and agencies.
$19.99 / month
  • 50 monitorsDesigned for larger site portfolios without becoming noisy.
  • 10 one-minute slotsFaster checks for business-critical sites and services.
  • Status page customizationOwner-verified branding, custom domains, and SEO controls.
  • Detailed exportsUse detailed logs and CSV exports for troubleshooting and reporting.
Feature Starter Plus Pro
Plan limits
Monthly priceSimple monthly pricing before taxes. $4.99 $9.99 $19.99
Included monitorsHTTP and HTTPS website monitors. 10 25 50
Default check intervalThe recommended check frequency for most monitors. 5 minutes 5 minutes 5 minutes
1-minute monitor slotsReserved for high-priority monitors that need faster detection. - 5 10
Alerts and reliability
Downtime and recovery alertsEmail notifications when a monitor changes state. Included Included Included
Slow response alertsAlert when a site is reachable but slower than your threshold. Included Included Included
SSL certificate monitoringOptional daily checks with warning thresholds. Included Included Included
Domain expiry monitoringOptional daily domain expiry warnings. Included Included Included
Incident pagesOpen incidents, recovery events, diagnostics summary, and activity log. Included Included Included
Detailed logs and CSV exportFilter checks by date range, status, response code, and latency. Included Included Included
Raw check log retentionRecent detailed check records for troubleshooting and export. 30 days 30 days 30 days
Long-term uptime summariesRollup views for 24 hours, 7 days, 1 month, and 1 year. Included Included Included
Multi-region failure confirmationFailed checks can be confirmed from additional regions before alerting. Included Included Included
Status pages
Public status pagesOptional monitor-backed pages for customers or stakeholders. Included Included Included
Status page brandingOwner verification is required for logo, favicon, and custom branding. Verified sites Verified sites Verified sites
Custom status page domainsUse your own status subdomain after ownership verification. Included Included Included
Support and safeguards
Cost and abuse protectionAutomatic safeguards reduce noisy checks and suppress runaway alerts. Included Included Included
Email supportSupport is available 7 days a week with a 24-hour response target. Included Included Included
Why 1-minute checks are limited

Most websites do not need every monitor checked every minute. Uptime Basics keeps fast checks available for critical sites while protecting accounts from noisy, expensive, or unreliable monitors.

Ready To Start

Use a tool that tells you what happened without burying you in dashboards.

Start with the Starter trial, add the first few monitors, and keep the setup lean until your sites actually need more frequent checks.

Talk to support