Skip to content

For SaaS companies

An outside view of your SaaS availability.

UptimeWire requests your public addresses from the outside, confirms failures before it raises an incident, and tells your team when a service stops answering and when it recovers.

Service addresses Demo data
  • Public app212 ms

    app.example · HTTP 200

  • Sign-in page188 ms

    app.example/login · HTTP 200

  • Health endpointIncident confirmed

    api.example/health · HTTP 503

  • Documentation240 ms

    docs.example · HTTP 200

What to monitor

Pick the addresses your customers depend on.

Each exact address counts as one website, with its own uptime, certificate, domain, and DNS checks.

Choose addresses that answer without signing in

UptimeWire sends a plain request and counts an answer from 200 to 399 as up. It cannot send credentials or custom headers, so an address that needs them answers 401 or 403, and that counts as a failure.

Make a health endpoint say more

You can also raise a failure when the page lacks a given text, or contains one, such as an error message. The match is exact, and only the first megabyte of the page is read.

Incidents

A confirmed incident, not a single failed request.

Alerts that cry wolf get ignored, so a failure is checked again before anyone is paged.

  1. 1

    A check fails

    The address does not answer, or answers outside 200 to 399.

  2. 2

    It is repeated

    The check runs again shortly afterwards, about 20 seconds later, and can be repeated from a second location where one is set up.

  3. 3

    The incident opens

    Your channels get an outage alert with the reason, for example HTTP 503.

  4. 4

    It closes on recovery

    You get a recovery alert, and the history keeps the start, the cause, and the duration.

Confirmation reduces false alarms. It does not remove them, and it does not make detection instant: the time to an alert depends on your plan's check interval (Free 5 minutes, Starter 3 minutes, Business 1 minute, and Agency 1 minute).

Where it fits

Use it next to your observability tools, not instead of them.

UptimeWire sees your service the way an outside visitor does. Your own tools see inside.

What an outside check shows

  • Whether each address answered, and with what status code
  • How long it took to answer
  • When a problem began, how long it lasted, and when it ended
  • Whether the certificate, the domain, and DNS are in order

What it does not show

  • Why the service failed: no logs, traces, or error reports
  • Whether sign-in, an API call, or a payment works from end to end
  • Server load, queues, or database health
  • Anything behind a login, because requests carry no credentials

Your team

Send alerts where your team already works.

Alerts reach people in the channels they watch. A public status page can show everyone else.

  • Email and Telegram

    On every plan, for outage and recovery as well as certificate, domain, and DNS warnings.

  • Webhooks and Discord

    From Starter, for outage and recovery. A webhook is signed, so your own code can check where a message came from.

  • Slack and Microsoft Teams

    From Business, for outage and recovery.

A public status page

From Starter, a status page fills in from monitoring results and planned maintenance. Pages by plan: Starter 2, Business 5, and Agency 25. Monitoring and a status page are separate things: monitoring tells your team, the page tells your customers.

Team access

Larger plans allow more users. Everyone on the account sees all of its websites. There are no per-person or per-project permissions.

The notification channels are built, but delivery to live services is still being verified. See the integrations directory for the status of each.

Plan fit

Starter to get going. Business when the service grows up.

Pricing stays the one place to compare every plan.

Starter

  • 10 websites, checked every 3 minutes
  • 2 public status pages
  • Webhooks and Discord

Starter plan details

Business Recommended

  • 25 websites, checked every 1 minute
  • 5 status pages, with your own logo and domain
  • Slack and Microsoft Teams
  • Monthly SLA reports on screen, CSV export, an incident log export with a file check, a read-only API, and an MCP server

Business plan details

History kept by plan: Free 30 days, Starter 90 days, Business 1 year, and Agency 2 years. The Free plan covers one website and is a fair way to try the checks first.

Frequently asked questions

Before you start.

Does UptimeWire replace observability or APM tools?

No. It checks your public addresses from the outside. It does not collect logs, traces, errors, or server metrics. Use it as an independent signal that your service is reachable, next to the tools that explain why it is not.

Can I monitor an API that needs authentication?

Not directly. Requests carry no credentials or custom headers, so a protected address answers 401 or 403, which counts as a failure. Monitor a public health address instead.

Is a status page the same as monitoring?

No. Monitoring watches your addresses and alerts your team. A status page shows customers the result. UptimeWire fills a page in from monitoring results and planned maintenance. It does not publish messages you write by hand.

How quickly will I know about an outage?

That depends on your check interval (Free 5 minutes, Starter 3 minutes, Business 1 minute, and Agency 1 minute) and on confirmation, which repeats a failed check before an incident opens. There is no fixed number of seconds.

Can UptimeWire guarantee my SLA?

No. It measures availability as seen by its checks. Business and Agency show monthly SLA figures on screen and export them to CSV. They can also export the incident log, and a page checks that the file is still as we issued it. Whether you meet a commitment to your customers is still your call.

Watch your service from the outside.

Monitor your first address for free. All four checks are included.