/MonitorMonitor
Get started free
Monitor

Know it's down before your customers do

Confirmed before you get paged. One incident, not a storm.

HTTP, SSL certificate and domain expiry checks. A failure has to repeat before an incident opens. Then Norcube alerts your team on Slack, Discord, email, SMS or a signed webhook, and repeats critical alerts until someone acknowledges them.

Start free in 60 secondsRead docs →
HTTP, keyword and API checksSSL and domain expirySlack, Discord, email, SMS, webhooksConfirmed before you get pagedPublic status pagesFree to start, no card

Why Norcube Monitor

A ping tells you a request failed. Norcube tells you when it matters and keeps reminding you about a critical incident until someone acknowledges it.

Confirmed

Downtime opens an incident only after the failures in a row you set, two by default. Is a service flapping? Raise the failures and recoveries it takes, up to 10.

Learn more

Covered

One HTTP monitor can also track its own certificate and the domain it runs on. Three common ways a site fails, watched from one place, with the details for each.

Learn more

Persistent

Slack, Discord, email, SMS or a signed webhook, routed per monitor and event. Critical incidents repeat hourly by default until acknowledged or resolved.

Learn more
Incidents

One incident, every alert, one timeline

A check fails. The next one fails too, so the incident opens and your alert channels get the alert. Someone acknowledges it and the reminders stop. The first clean check resolves it with a Recovered notice. Every step and every alert sits on one timeline.

  • Downtime opens an incident after the failures you set in a row (two by default). Expiry problems are certain, so they open at once
  • Warning or critical, with the status code, response time or days left as evidence
  • Acknowledge from the dashboard, the CLI or the API; a recovery closes it
Try Monitor free

Checks that keep your secrets

A monitor often needs an API key to reach what it checks. Norcube treats those like credentials, and its own checks like untrusted traffic.

Secret headers

Mark a header as secret and its value is encrypted at rest, never shown again, and never sent to another origin, not even on a redirect.

Checks can't reach private networks

Checks refuse private addresses and sensitive ports such as SSH, SMTP and databases, and never follow a redirect into them. A monitor is not a scanner.

Webhooks you can verify

Every webhook is signed to the Standard Webhooks spec, with a secret you see once and can rotate at any time. HTTPS only.

Three kinds of checks. Five alert channels

HTTP, SSL and domain monitors, checked as often as every 60 seconds on a new organization (domain monitors at most hourly), with alerts routed to the channel each event deserves.

HTTP and API checks

Any method, custom headers and body, the status codes you expect, a timeout and a slow-response threshold.

HTTP and API checks

Any method, custom headers and body, the status codes you expect, a timeout and a slow-response threshold.

GET, HEAD, POST, PUT, PATCH, DELETE or OPTIONS with up to 20 headers and a request body. Accept status codes as rules such as 2xx, 301 or 400-404. Set a timeout from 1 to 30 seconds and, separately, a slow-response threshold that raises a warning instead of a false "down". Follow redirects or not, verify TLS or not; a refused certificate is still reported with its reason.

Keyword and content

Require a word to be present, or absent, in the response. Catches a pricing page that lost its prices and an API that returns an error with status 200.

Keyword and content

Require a word to be present, or absent, in the response. Catches a pricing page that lost its prices and an API that returns an error with status 200.

Set the text that must appear (or must not) and whether case matters. The first 256 KiB of the body are searched after decompression, so a page that quietly degrades is a failure, not a green check.

SSL certificates

Expiry alerts at the days you choose, plus the chain, issuer and hostname checked on every connection.

SSL certificates

Expiry alerts at the days you choose, plus the chain, issuer and hostname checked on every connection.

An SSL monitor performs a TLS handshake, verifies the chain and the hostname, and judges the expiry against up to five thresholds (30, 14 and 7 days by default). The certificate panel shows the subject, issuer, SANs, validity and the presented chain, and keeps a history of renewals.

Domain expiry

Registrar, expiry date, nameservers and DNSSEC for the domain, looked up through DomainRadar at most once an hour.

Domain expiry

Registrar, expiry date, nameservers and DNSSEC for the domain, looked up through DomainRadar at most once an hour.

Domain monitors use the same registry data as DomainRadar: RDAP where the registry offers it, WHOIS or DNS otherwise. You see the expiry with days left, the registrar, nameservers and EPP status codes, and get alerted at the thresholds you set. An HTTP monitor on an https:// URL can watch its own certificate and domain too, tracked separately so they never affect its uptime.

Alerts and routing

Slack, Discord, email, SMS and signed webhooks. Default channels for the organization, or routes per monitor and per event.

Alerts and routing

Slack, Discord, email, SMS and signed webhooks. Default channels for the organization, or routes per monitor and per event.

Email goes to a verified address or to every member of your organization. SMS goes to verified mobile numbers. Slack and Discord use an incoming webhook URL. Pick which events each channel gets: down, warning, expiring, expired, recovered. Every send is retried with backoff, up to 8 attempts, and listed in the channel delivery log; a send that gives up is noted on the incident timeline, and a test button proves the whole path before you need it.

Incidents you can act on

A timeline per incident with the evidence and every alert it sent. Acknowledge to stop the reminders. Export the history as CSV.

Incidents you can act on

A timeline per incident with the evidence and every alert it sent. Acknowledge to stop the reminders. Export the history as CSV.

Open incidents come first, critical before warning. Each one shows what the check saw, when it escalated or eased, who acknowledged it and which deliveries went out. The incidents page sums up what is open, what resolved in the last 30 days and the mean time to resolve.

Uptime and response times

Uptime over 24 hours to 90 days, a daily availability bar and response times broken into DNS, TLS and transfer.

Uptime and response times

Uptime over 24 hours to 90 days, a daily availability bar and response times broken into DNS, TLS and transfer.

Every monitor keeps a 90-day availability bar and a chart of response times with the DNS, TLS and transfer phases, so a slow check points at the layer that caused it. Status changes are kept for a year.

From the CLI and CI

Create and run monitors from the terminal, and fail a pipeline while something is down.

From the CLI and CI

Create and run monitors from the terminal, and fail a pipeline while something is down.

The norcube CLI covers monitors, incidents and channels. In CI, nrc monitor status --fail-on critical fails the job while a critical incident is open, and nrc monitor monitors run <monitor> --wait runs a check now and fails when it finds the monitor down. CI tokens carry only the scopes you grant: read, check, write, channels or status pages. No other scope includes status pages, so a deploy token can't post a public outage unless you grant that one.

Monitor in the CLI reference

API

The same API the dashboard uses, with scoped CI tokens. Create monitors, acknowledge incidents and post status updates from your own code.

Read the API docs

Public status pages

A status page built from your monitors at your-name.norcubestatus.com, with incident posts you write, served from the edge.

Public status pages

A status page built from your monitors at your-name.norcubestatus.com, with incident posts you write, served from the edge.

Pick the monitors your customers care about, group them and give them public names; the URLs you monitor stay private. Each component shows its status and an availability bar of up to 90 days, and follows the monitor's open incidents, so the page and your alerts agree. Post incidents and updates from the dashboard, the CLI or the API; resolved ones stay in the history for the window you set, up to a year. Every page has an Atom feed and a JSON version. It is rendered at the edge from a snapshot, so it keeps serving the last known state when your stack, or ours, is down, and says when live updates are delayed.

How status pages work
Status pages

A public status page, built from your monitors

Pick the monitors your customers care about, group them and give them public names; the URLs you monitor stay private. The page lives at your-name.norcubestatus.com and is served from the edge, so it keeps showing the last known state even when your stack, or ours, is down.

  • Component status follows its monitor's open incidents, so the page and your alerts agree
  • Availability bars of up to 90 days, incident posts with updates, an Atom feed and a JSON version
  • Every page carries a small "Powered by Norcube Monitor" footer, and you can't remove it today
  • Next: email subscribers, maintenance windows and page colors
Set up a status page

What a status page gives you today

Your own domain

Use status.yourcompany.com. Prove ownership with a TXT record, point a CNAME at us and the certificate is issued for you. Billed per active domain.

Your logo

PNG, JPEG, WebP or SVG, up to 48 KB each. Add a dark-mode version and visitors see the one that matches their theme.

Eight languages

Fixed page text in eight languages, machine-translated and matched to the visitor's browser. Your own names and posts stay as you wrote them.

No cookies, no analytics

Status pages set no cookies and load no analytics, and their content security policy blocks third-party scripts. No consent banner from us.

Components and posts

Components follow your monitors, or you set their status by hand. Resolved posts stay for as long as you choose, from 7 days to a year.

Publishing

Check a draft with a 15-minute preview link and choose whether search engines index it. Change the address and the old one redirects for 30 days.

For teams where downtime costs real money

Engineering · DevOps · SRE

SaaS platforms

Watch your API and checkout with the status codes and response times you expect. A slow endpoint raises a warning, an outage opens a critical incident and pages the on-call channel.

MonitorsAll up
api.acme.comHTTP142 ms
checkout.acme.comHTTP89 ms
acme.comSSL certificate47 days left
Agencies · Freelancers · MSPs

Agencies managing clients

Every client site, certificate and domain in one account, with an organization per client if you prefer. Nothing lapses on your watch, and the incident timeline shows the client what happened.

Alert channels4 active
Slack#ops
Email[email protected]
SMS+420 ••• ••• 842
Webhookapi.acme.com/hooks/…
Online stores · Payments

E-commerce

Every minute of downtime costs revenue. Watch the storefront, the checkout and the payment callback, and route the checkout monitor to SMS so the right person wakes up.

DevOps · Platform · Cloud

Infrastructure teams

HTTP checks for services, SSL monitoring for certificates, domain tracking for the portfolio, and a CI gate that stops a deploy while production is down.

InfoSec · Compliance · Audit

Compliance & security

Expiry alerts for every certificate and domain, a year of status history and an incident record with who acknowledged what and when.

Solo founders · Indie hackers

Startups & side projects

Free to start: ten monitors at one-minute intervals, alert channels of your choice and a public status page. Enough to watch a production app at zero cost.

SSL certificates3 tracked
acme.com47 days left
api.acme.com12 days left
shop.acme.com89 days left

Free to start. We'll publish prices before anyone is charged

Sign up and start right away: free, no credit card. Usage is counted per check, notification and custom domain from day one, and we'll publish prices here before anyone is charged.

Free tier: Everything

These are the default limits of a new organization. If you need more, email [email protected] and we'll raise them.

Included today : Free to start. No credit card.
Monitors 10 per organization
Check interval As often as every 60 seconds
Alert channels Up to 100
Slack, Discord, webhooks Included
Email 500 a day
SMS 10 a day, verified numbers
Status pages 1 per organization
Custom domains Billed per active domain, one per page
History 90 days of availability, 1 year of status changes

Questions, answered

Common questions about Norcube Monitor. Need something else? Email [email protected].

Where do the checks run from?
From one region today, Frankfurt (eu-central-1), from the fixed IP address 18.185.27.174, which you can allow in your firewall. Checks from more regions, with a second region confirming a failure before an incident opens, are on the roadmap.
How quickly will I know something is down?
A new organization can check as often as every 60 seconds, and as rarely as once a day; 30 seconds is available if you ask us. Domain monitors check at most once an hour. A downtime incident opens after the number of failed checks in a row you set, two by default, so at a one-minute interval you are alerted within about two minutes of the failure starting, and one blip alerts nobody. Expired certificates, expired domains and expiry thresholds alert at once.
Which alert channels are there?
Email (a verified address or every member of your organization), Slack and Discord (an incoming webhook URL), SMS (verified mobile numbers; currently Czechia, Slovakia, Germany, Austria, Poland and the United Kingdom, ten a day per organization by default) and webhooks (HTTPS, signed to the Standard Webhooks spec). We don't offer phone calls.
Will I get an alert storm when a monitor flaps?
Not while an incident stays open. There is one open incident per monitor for each thing it watches. Escalating from warning to critical alerts once; falling back to warning is noted on the timeline without an alert; a certificate already alerting as down doesn't alert again for expiry. Reminders apply to critical incidents and repeat every hour by default (every 15 minutes to once a day, or off) until someone acknowledges the incident or it resolves. If a monitor recovers and fails again, that is a new incident with its own alerts, so raise the failures and recoveries needed (up to 10) to quiet a flapping service.
Can one monitor watch the certificate and the domain too?
Yes. An HTTP monitor on an https:// URL can watch its own certificate expiry and the expiry of the domain it runs on. Each has its own incident and thresholds, and neither affects the uptime or response times of the HTTP check.
Can I use it from CI?
Yes. Create a CI token with the scopes you need, then run nrc monitor status --fail-on critical to fail a job while a critical incident is open, or nrc monitor monitors run <monitor> --wait to run a check now and fail when it finds the monitor down. The CLI also creates, pauses and resumes monitors, acknowledges incidents and tests channels.
Do I get a public status page?
Yes. Create one in the dashboard or with nrc monitor status-pages create, pick a name and it lives at your-name.norcubestatus.com. It shows components grouped from your monitors under public names, with availability bars of up to 90 days and the incident posts you write, and is served from the edge so it keeps showing the last known state when your infrastructure is down. Email subscribers, maintenance windows and page colors are next.
How many custom domains can a status page have?
One per page, and it has to be a subdomain such as status.yourcompany.com, not a bare domain such as yourcompany.com. Each active domain is billed.
Are the feed and page.json translated?
No. A page's fixed text follows the visitor's language, but the Atom feed and the JSON data stay in English, and your own names and posts stay as you wrote them.
What doesn't Monitor do yet?
No ping, port, heartbeat or DNS checks yet. No phone call alerts. Status pages have no private mode, email subscribers, maintenance windows or custom colors yet. The MCP server has no Monitor tools.
What happens if Norcube itself is down?
Checks run from one place, so if our checker is down, checks and alerts stop and you will not get alerted. Published status pages keep showing the last known state and say live updates are delayed. Watch status.norcube.com for our own health.
What happens if an invoice goes unpaid?
While an organization is blocked for unpaid invoices, its checks stop and it can't create or publish status pages. Pages already published, and their custom domains, stay up.
Where does my data go?
Monitor data is stored in AWS Frankfurt. Public status page content is stored and served by Cloudflare worldwide, SMS alerts go through BulkGate in the Czech Republic and email through Mailgun in the EU. See security, the DPA and the subprocessors for the details.
Is this PulseCheck?
Yes. Norcube Monitor was built under the working name PulseCheck and renamed before launch. Old /pulsecheck links redirect here.

Your first monitor in two minutes

A URL and a name are all it takes. The first check runs the moment you save.

About 2 min

  1. Create a monitor

    In the Monitor section of the dashboard, choose New monitor, pick HTTP, SSL certificate or Domain expiry, paste the URL or domain and name it. The first check runs immediately.

  2. Tune what counts as up

    For HTTP: the status codes you accept, a timeout, an optional keyword and an optional slow-response threshold. For certificates and domains: the days before expiry you want to hear about. Pick an interval from 60 seconds to 24 hours (30 seconds if you ask us; domain monitors at most hourly).

  3. Add an alert channel

    Open Alert channels and add Slack, Discord, email, SMS or a webhook. Email addresses and phone numbers are verified with a code; webhooks show their signing secret once. Mark the channel as a default and send a test.

  4. Route and confirmOptional

    On a monitor, open the Alerts tab to route specific events to specific channels, and set how many failures open an incident and how often reminders repeat.

  5. Gate your deploysOptional

    Create a CI token and add nrc monitor status --fail-on critical to your pipeline, so the deploy fails while a critical incident is open.

Stop finding out from your customers

Free to start, no credit card. Set up your first monitor in two minutes.

Start free in 60 secondsRead the docs
  • Free to start
  • Confirmed incidents
  • 5 alert channels
  • CLI and CI gate

Other products on the platform

Monitor shares its account, invoice and dashboard with every other Norcube product.

BackupBackups for the databases you monitorPostgreSQL and MongoDB dumps, restore-tested, downloadable as gzip.CMSBetaA visual editor for the site you watchGit-based editing with live preview and AI assistance for static sites.DomainRadarDomain checks and brand monitoringCheck 100,000 domains in one job and watch for lookalikes of your brand.LangSyncAI translations for the apps you runMulti-language sync with glossary-aware AI translation and i18n JSON export.
// tick. tick. tick.
0 ticks since founding
Coming soon

Join the PromptHub waitlist

PromptHub is in active development. Leave your email and we'll invite you as soon as it opens, with a free tier and no credit card.

One email when access opens. No newsletter, no spam.