Site Hush

Website monitoring, without the noise.

We keep watch. You can relax.

Site Hush checks your website and verifies outages. Get notified in Slack when something needs attention — and when your site responds again.

Sign in with Google

HTTP/HTTPS monitoring · Google sign-in · Slack alerts

Enter example.com or a full address. HTTPS is the default.

One-time check, not ongoing monitoring. We do not save the address or send alerts.

Try an incident, from first signal to recovery
Site HushExample account
Responding

Responding. Carry on with your day.

The latest check returned HTTP 200. The result goes into your history without a new incident alert.

MonitorsLatest result
Example shopexample.com
RespondingHTTP 200184 ms
Customer portalexample.org
RespondingHTTP 200202 ms
Homepageexample.net
RespondingHTTP 200149 ms
Recent checks · example
Latest checkHTTP 200184 msexample.com
Slack · #uptime-larmPreview
Site Hush

No incident alert

HTTP 200 · 184 ms · no open incident
Site HushExample account
Verifying

One failure. We check again.

The first attempt returned HTTP 503. Two confirmation checks remain before an outage is confirmed.

MonitorsLatest result
Example shopexample.com
VerifyingHTTP 503—
Customer portalexample.org
RespondingHTTP 200202 ms
Homepageexample.net
RespondingHTTP 200149 ms
Recent checks · example
Latest checkHTTP 503Verifyingexample.com
Slack · #uptime-larmPreview
Site Hush

No incident alert yet

1 of 3 failed checks · verification in progress
Site HushExample account
Down

The outage is confirmed.

Three consecutive checks failed. An incident opens and an alert is sent to the connected channel.

MonitorsLatest result
Example shopexample.com
DownHTTP 503—
Customer portalexample.org
RespondingHTTP 200202 ms
Homepageexample.net
RespondingHTTP 200149 ms
Recent checks · example
Latest checkHTTP 503Downexample.com
Slack · #uptime-larmPreview
Site Hush

DOWN — Example shop

HTTP 503 · 3 failed checks · the same incident is followed until recovery
Site HushExample account
Recovered

Back up. The same incident closes.

Two consecutive checks succeeded. The incident closes and the channel receives a recovery notification.

MonitorsLatest result
Example shopexample.com
RecoveredHTTP 200184 ms
Customer portalexample.org
RespondingHTTP 200202 ms
Homepageexample.net
RespondingHTTP 200149 ms
Recent checks · example
Latest checkHTTP 200184 msexample.com
Slack · #uptime-larmPreview
Site Hush

RECOVERED — Example shop

HTTP 200 · 2 successful checks · example downtime: 3 min 23 sec

Interactive example with fictional data. No checks or Slack messages are sent.

5min by default

Automatically every five minutes. Choose 5, 10, 15, 30 or 60 minutes for each monitor.

3failures confirm an incident

The first failure triggers two verification checks. Three consecutive failures open the incident and send a notification.

2successes confirm recovery

Two consecutive successful checks resolve the incident. Your team gets another notification when the site responds again.

LESS SEARCHING. MORE CLARITY.

See what needs your attention.

Status, check results and incidents in one place. Try the examples to see what you and your team will know.

Available now

Find the sites that need you.

Status, HTTP results and response times for your addresses. Filter for what needs attention.

Try the monitor list filters
MonitorsExample data
Example shopexample.com
DownHTTP 503—
Customer portalexample.org
VerifyingHTTP 503—
Homepageexample.net
RespondingHTTP 200184 ms

Try the filter above. In the app, you can search and sort too.

Slack

Down and recovered. In the right channel.

Slack gets notified when an incident is confirmed and when the site responds again. Follow the incident timeline in the app.

Try Slack outage and recovery notifications
# uptime-larmExample data
Site Hush 08:05

DOWN — Example shop

HTTP 503 · 3 failed checks · the same incident is followed until recovery

Incident timeline in the app
Site Hush 08:05

RECOVERED — Example shop

HTTP 200 · 2 successful checks · example downtime: 3 min 23 sec

Incident timeline in the app

READ THE RESULT

Responding means more than a green dot.

See the latest HTTP result and response time. A failure or timeout is shown as it was observed. Try three examples below.

Try different check results
184 ms · HTTP 200The address responded to this check.
HTTP 503The server returned an error. One failure needs confirmation.
12 s · no responseThe check reached its time limit. This is not a measured response time.

Example data

SHARE THE RESPONSIBILITY

The same picture for your whole team.

Invite colleagues to your account. Everyone sees the same monitors and incidents, with the permissions their role needs.

Who can do what?
  • AdminManages monitors, integrations and members.
  • MemberWorks with monitors and incidents.
  • ViewerSees results and incidents without changing settings.
How team roles work

Real addresses. Observed responses.

Big names. The same simple check.

20 familiar companies, with homepages and important pages checked by Site Hush. Expand a row to see each address and its response time.

Latest reading · saved result, not current status ·

  • AmazonLast: responded
    2 addresses567 msHTTP 200
  • StripeLast: responded
    2 addresses1049 msHTTP 200
    • Homepagestripe.comObserved:
      Last: responded 1049 msHTTP 200
    • Key subpagestripe.com/paymentsObserved:
      Last: responded 990 msHTTP 200
  • RampLast: responded
    2 addresses706 msHTTP 200
    • Homepageramp.comObserved:
      Last: responded 706 msHTTP 200
    • Key subpageramp.com/accounts-payableObserved:
      Last: responded 768 msHTTP 200
  • ClayLast: responded
    2 addresses442 msHTTP 200
    • Homepagewww.clay.comObserved:
      Last: responded 442 msHTTP 200
    • Key subpagewww.clay.com/pricingObserved:
      Last: responded 425 msHTTP 200
  • DoorDashLast: unverified
    2 addresses305 msHTTP 403
  • NotionLast: responded
    2 addresses743 msHTTP 200
    • Homepagewww.notion.soObserved:
      Last: responded 743 msHTTP 200
    • Key subpagewww.notion.so/productObserved:
      Last: responded 985 msHTTP 200
  • PostHogLast: responded
    2 addresses367 msHTTP 200
    • Homepageposthog.comObserved:
      Last: responded 367 msHTTP 200
    • Key subpageposthog.com/pricingObserved:
      Last: responded 414 msHTTP 200
  • AppleLast: responded
    2 addresses299 msHTTP 200
    • Homepagewww.apple.comObserved:
      Last: responded 299 msHTTP 200
    • Key subpagewww.apple.com/iphone/Observed:
      Last: responded 355 msHTTP 200
  • NikeLast: responded
    2 addresses898 msHTTP 200
  • AnthropicLast: responded
    2 addresses354 msHTTP 200
  • IntercomLast: responded
    2 addresses842 msHTTP 200
    • Homepagewww.intercom.comObserved:
      Last: responded 842 msHTTP 200
    • Key subpagewww.intercom.com/finObserved:
      Last: responded 2545 msHTTP 200
  • GitHubLast: responded
    2 addresses580 msHTTP 200
    • Homepagegithub.comObserved:
      Last: responded 580 msHTTP 200
    • Key subpagegithub.com/featuresObserved:
      Last: responded 766 msHTTP 200
  • LinearLast: responded
    2 addresses616 msHTTP 200
    • Homepagelinear.appObserved:
      Last: responded 616 msHTTP 200
    • Key subpagelinear.app/featuresObserved:
      Last: responded 501 msHTTP 200
  • VercelLast: responded
    2 addresses316 msHTTP 200
    • Homepagevercel.comObserved:
      Last: responded 316 msHTTP 200
    • Key subpagevercel.com/pricingObserved:
      Last: responded 358 msHTTP 200
  • FigmaLast: responded
    2 addresses277 msHTTP 200
    • Homepagewww.figma.comObserved:
      Last: responded 277 msHTTP 200
    • Key subpagewww.figma.com/design/Observed:
      Last: responded 488 msHTTP 200
  • ShopifyLast: responded
    2 addresses275 msHTTP 200
  • CloudflareLast: responded
    2 addresses273 msHTTP 200
  • SlackLast: responded
    2 addresses539 msHTTP 200
    • Homepageslack.comObserved:
      Last: responded 539 msHTTP 200
    • Key subpageslack.com/featuresObserved:
      Last: responded 559 msHTTP 200
  • DropboxLast: responded
    2 addresses1050 msHTTP 200
    • Homepagewww.dropbox.comObserved:
      Last: responded 1050 msHTTP 200
    • Key subpagewww.dropbox.com/plansObserved:
      Last: responded 1669 msHTTP 200
  • SpotifyLast: responded
    2 addresses666 msHTTP 200

Dated, one-off observations of individual addresses, not company-wide status or continuous live monitoring. Logos identify the websites; these companies are not presented as customers.

One address. Three simple steps.

Start with an important address. Then connect the channel where you handle outages.

  1. Add a web address

    Sign in with Google, create an account and add your first public address. A CSV file can contain several addresses.

    Example data

  2. See a verified result

    Run a manual check or wait for the next scheduled one. A single failure is verified before the website is marked down.

    Example data

  3. Connect the channel where you act

    Connect a Slack channel in Integrations and send a test. Events are logged even when no channel is connected.

    Example data

CONFIRM FIRST. THEN ACT.

A failure is a signal. An incident needs evidence.

Three consecutive failed checks open an incident. Two consecutive successful checks confirm recovery. Website status and notification delivery are shown separately.

  1. The first failure

    The monitor starts verifying. No DOWN notification is sent yet.

  2. Confirmed down

    Two further failures open an incident. A connected Slack channel can receive a DOWN notification.

  3. Verified recovery

    Two successful checks resolve the same incident. The channel can receive a RECOVERED notification.

A delayed check means the check sequence is behind, not that your website is down.

ONE APP. THE RIGHT CHANNEL.

Notifications where you already work.

Use your existing Slack app and add a webhook for monitor alerts. Operational alerts about Uptime itself belong in a separate internal channel.

Follow the Slack guide
1Choose the channel where your team acts
2Connect the webhook in Integrations
3Send a test and check that it arrives
Example data

GOOD TO KNOW

Common questions. Straight answers.

How checks, alerts and data work. Get the answers before you get started.

Guides
How often is my website checked?

Five minutes is the default and shortest allowed interval in the pilot. You can also choose 10, 15, 30 or 60 minutes. Confirmation checks run after an observed failure.

How do I connect Slack?

Create a Slack app with Incoming Webhooks enabled, choose a channel and copy its webhook address. In Site Hush, open Integrations, choose How to connect Slack and connect the address. Then send a test to the channel.

Which addresses can I monitor?

Public HTTP and HTTPS addresses. Private networks, loopback addresses and unsafe ports are rejected. A redirect cannot be used to reach a private network.

Can I add a sitemap that updates every day?

Not in the pilot yet. Daily sitemap sync and bulk page management are planned. For now, add addresses manually or preview a CSV file with up to 500 rows and 1 MB.

What data is stored?

The app stores accounts, memberships, monitors, check results and incident history. Target and webhook addresses are stored encrypted. Logs and notifications must not contain secret URL parts.

Can I replace UptimeRobot immediately?

CSV import helps you move addresses, but do not switch off existing monitoring just because the import succeeds. Verify notifications, compare incidents during a parallel run and make a separate decision about retiring the old service.

Is this an SLA or a global check?

No. The pilot checks from one region and has no published SLA. A successful HTTP check does not prove that all user journeys or all regions work.

YOUR FIRST CHECK STARTS HERE

Make the next check your first.

Sign in, add your first monitor and see a real result. Connect Slack once you have chosen where the team should hear about incidents.

Sign in with Google