Monitoring & Status
Customers stop asking “is it down?”, and the updates write themselves
Your status page follows your monitors, so it changes when they do. When something really breaks, InfraNest drafts the update in plain words. You read it and post it. Customers see what is going on without having to write to you.
Free plan · No credit card · Publish a page in 5 minutes
- Follows your monitors, with nothing to update by hand
- A drafted update for every real outage
- Customers told by email, Slack, Teams or Discord
- One link per incident that keeps working
One incident, not several: the effects are grouped under the cause.
- 2:33 PMDeploy of northwyndr/storefront (f19e6c7)Deploys
- 2:36 PMCheckout flow failed: Checkout returning 503Monitoring
- 2:36 PMAPI health failed too, grouped under this incidentMonitoring
- 2:36 PMAlert sent to Ops team — email, On-call — critical only, #infra-alerts, Engineering — Discord, Northwind on-call — PagerDutyNotifications
MonitoringThe failover is live and checkout is succeeding again. Watching error rates before we call this resolved.
Public
Developer
An outage drafts its own status update, and you press post
During an outage, writing to customers is the job that gets left. So InfraNest writes the first version. Once a monitor on your status page has been down for three minutes from two locations, its incident shows a ready update: what is affected and since when. Read it, change it if you like, and post it. When the site is back, a second draft says it is over and how long it took. Your next outage takes one click to explain.
- You choose how long before a draft appears
- Names your provider when the outage is theirs
- Posts without asking, only if you turn that on
Status page update, drafted
Down for 5 min from 3 of 3 locations, so not a blip. Nothing has been posted on Northwind Cloud Status yet.
We are seeing an outage of Checkout & payments since 15:36 CET. We are looking into it and will post an update here.
Notify subscribers
Post to the status page
Status page update, drafted
It is working again. Tell the visitors of Northwind Cloud Status that it is over.
The outage of Checkout & payments is over: everything has worked again since 21:18 CET, after 45 minutes. Sorry for the inconvenience.
Notify subscribers
Post that it is resolved
When to draft
When an outage gets a draft
Down for at least this many minutes3
Seen down from at least this many locations2
A monitor that checks from fewer locations needs all of them. Shorter outages are blips and get no draft.
Post drafts without askingAn outage that meets this rule is posted to your status pages and their subscribers straight away, and “resolved” is posted when it recovers. Off: someone sends each draft.
Planned work? Warn customers in one click, before they ask
A maintenance window is easy to schedule and easy to forget to announce. InfraNest works out which status pages it touches and drafts the notice for you. Press “Add this notice” and it is on the page, with subscribers told. The name you gave the window stays inside your team, and a window without a notice stays internal. Schedule your next upgrade and see the notice appear.
- Maintenance windows are on Pro and up
- Subscribers hear when it is planned, starts and ends
- Planned work can stay out of your uptime figure
New maintenance window
Name
Database cluster upgrade
Starts at
Nov 2, 02:00 AM
Ends at
Nov 2, 03:00 AM
Affected monitors
API healthSearch API
Visitors of Northwind Cloud Status are not told about this window yet.
“Planned maintenance on API and Search API. Expect short interruptions during this window.”
Scheduled Maintenance
Planned maintenance on API and Search API. Expect short interruptions during this window.
Nov 2, 02:00 AM – 03:00 AM UTC
APISearch API
Status updates that reach customers by email, Slack, Teams or Discord
Most customers will not check your page, so it goes to them. Visitors subscribe with an email address, or paste a webhook for their Slack, Teams or Discord channel. A webhook is a link that lets us post in that channel. They hear when an incident opens, when you post an update and when it ends. Emails link straight to the incident. Put your page in your footer and let the list grow.
- Email addresses are confirmed before anything is sent
- You see who subscribed and can remove anyone
- Replies can land in your support inbox
Get notified
Subscribe to receive updates when this page's status changes.
Your address goes to Northwind Cloud Status, who may use it only to send status updates for this page.
Post to Slack, Teams or Discord
- Slack · Apps → Incoming Webhooks → Add to Slack
- Teams · Workflows → “Post to a channel when a webhook request is received”
- Discord · Edit Channel → Integrations → Webhooks
What lands in their channel
[Northwind Cloud Status] Incident detected: Checkout returning 503View status page
One link per incident, so you only explain it once
When a customer asks what happened, send the link. Each incident has its own page: what was affected, when it started and every update you posted. The link keeps working after the incident is over, so the one you pasted in a ticket last week still lands on the right story. Paste it once, and the follow-up questions answer themselves.
- Keeps working after the incident is over
- Says how the problem was detected
- Password-protected pages ask before showing anything
Back to status
OngoingStarted 40m ago
Checkout & payments
Latest updates
Detected automatically by our monitoring.
Monthly client reports that arrive without you building them
If you look after sites for clients, the monthly report eats an afternoon. On Business, pick a client’s status page or tag and the month is written up: uptime, every incident with its cause and a summary, response time and the maintenance done. When the month closes, it goes to the addresses you list, as a PDF in the language you pick. Your client needs no login. Open last month’s report and see what your client would get.
- Client reports are on Business and up
- Shows each uptime target as met or missed
- Also as a web page or a spreadsheet
Client report
Northwind Cloud Status in 2026-10.
Uptime on the status page
100.00%
Lowest monitor uptime
99.944%
Downtime
55 min
Incidents
5
Monitors
- Docs99.944%25 min down139 ms
- Marketing site99.966%15 min down179 ms
- Signup page copy99.966%15 min down209 ms
- 5 more monitors in the report
Incidents
Signup page copy missingDrafted summary
Signup page copy · Oct 15, 09:01 PM · cause: One check location
Signup page copy was down for 5 minutes, from Oct 15, 2026, 9:01 PM UTC to Oct 15, 2026, 9:06 PM UTC. What it was A false alarm. Cause: One check location.
Send this every month
client@example.comEnglish
A private view for your team: who is on call, and how to fix it
Your public page answers one question: is it broken? The person fixing it needs more. The team view is the same page behind your login. It shows who is on call, what is open right now and a runbook link for each service. A runbook is your own guide to fixing that service. It refreshes itself, so you can leave it open during an outage. None of it reaches the public page.
- The team view is on Business and up
- Only people in your workspace can see it
- Add a runbook link per service
Overall
Major outage
Services up
6/8
On call
Primary: Sam Okoye · +31 6 12 34 56 78 · #northwind-oncall on Slack. Escalation after 15m: Alex Rivera.
Open right now
MajorCheckout returning 503Public write-up
Services · last 30 days
Everything else it handles
The parts that are only interesting when you need them.
Built from your monitors
Each service on the page follows one of your monitors. You choose which ones appear and what they are called, so “App, northwyndr-app.dev” can read “Web app”, and internal checks stay internal.
Your own domain
On Pro and up, use status.yourcompany.com, with HTTPS arranged and renewed for you. If that name sits in a DNS zone you manage in InfraNest, “Set it up for me” adds the record.
Your look
Your logo, header image, colour and footer. One column or two, light or dark or following the visitor’s device. Whatever the layout, an outage stays at the top.
Announcements
Post a message at the top of the page without opening an incident, and choose how long it stays. An automation can post one too.
Badges and widgets
Show your live status in a README, your docs or your footer. A badge works anywhere an image does. The live widget comes in four layouts, including a banner that stays hidden while everything is fine.
See who reads it
Page views, unique visitors and subscribe clicks over 7, 30 or 90 days, so you can see if customers look here first. Counted without cookies, and approximate.
Services you depend on
On Pro and up, list third parties you rely on beside your own services, so customers can see when the trouble is elsewhere.
Uptime targets
On Pro and up, publish a target such as 99.9% and show the month’s progress against it on the page.
Private pages
On Business and up, put a password on a page for an internal or customer-only audience, and choose whether search engines may index it.
How many pages
One status page on Free, three on Pro, and as many as you need on Business and up. Removing the “Powered by InfraNest” line is on Enterprise.
Publish a page in about five minutes
Point it at the monitors you already run. Nothing goes public until you say so.
A hand-made status page vs InfraNest
The difference between a page you have to remember and a page that already knows.
By hand
- A page someone must remember to update during the outage
- Customer emails asking “is it down?”
- Maintenance nobody announced
- The same explanation, typed into every ticket
- A monthly client report built by hand
With InfraNest
- A page that follows your monitors
- Subscribers told by email, Slack, Teams or Discord
- A notice drafted from the window, one click to add
- One link per incident that keeps working
- A report sent when the month closes, on Business
Comparing tools? See Better Stack vs InfraNestFreshping vs InfraNestInstatus vs InfraNestOh Dear vs InfraNestStatuspage vs InfraNestUptime Kuma vs InfraNestUptimeRobot vs InfraNest
One login, ten modules
Nine modules are on every plan, Free included, and firewalls start on Pro. What changes is how much of each you get, plus a few advanced features from Pro.
Build on it
The cost of doing it separately
Buy each piece from a different tool and it adds up fast:
- Uptime monitoring
- ~€26
- SSL tracking
- ~€15
- Status page
- ~€26
- Across 3 separate tools
- ~€67/mo
Also in Pro, not counted above: 100 domains with DNS, 10 servers across your cloud providers, 25 automations, Dynamic IP and Drop Catch.
Each line is that tool’s cheapest paid plan. Pro covers all of it: 50 monitors, 100 certificates and 3 status pages on your own domain.
Prices checked October 2026 · dollar prices at the ECB rate
Built for how you work
Try it with a free tool
Frequently asked
How do I create a status page?
Add your monitors, pick the ones customers should see, give them public names and publish. It takes about five minutes, and the free plan includes one page. Nothing goes public until you say so.
Does a status page update itself?
The status does. Each service follows its monitor, so the page changes when the monitor does. The words are yours: for a real outage InfraNest drafts the update, and you read it and post it. If you want, turn on “Post drafts without asking”, and drafts that meet your rule go out straight away.
Are subscribers told before I have read the draft?
Yes. A subscriber gets a short notice with the incident’s title as soon as an incident opens on their page, and another when it ends. That also goes for short outages that get no draft. The draft is the update you add on top. Work inside a maintenance window that silences alerts tells nobody.
Can customers subscribe to status updates in Slack, Teams or Discord?
Yes. On your public page they paste a webhook for their channel, and it starts receiving updates. The form shows where to find that webhook in each product. If a webhook stops working, the Subscribers tab says so.
Can customers subscribe to just one service?
No. Everyone on a page gets all of that page’s notices. If a client only cares about their own services, give them a status page of their own.
Can I use my own domain for my status page?
Yes, on Pro and up. Point a CNAME record at us and HTTPS is arranged and renewed for you. If the name sits in a DNS zone you manage in InfraNest, “Set it up for me” adds the record, and verification starts by itself.
Can I send clients a monthly uptime report?
Yes, on Business and up. Pick a client’s status page or tag and list the addresses. When the month closes, they get uptime, incidents with their causes, response time and maintenance, in the language you chose. They need no login, and a month with nothing in it is not sent.
What happens to subscriber email addresses?
The form says who gets the address and what for: status updates for that page and nothing else. Addresses are confirmed before anything is sent. You can see who subscribed, remove one person or remove everyone. There is no export.
Do incident links keep working after the incident is over?
Yes. A link to an incident keeps working after it is resolved, and after it has left the page’s history list. If you rename the page, old links still find their way. The one exception: if you switch off incident history on a page, its resolved incidents stop being public.
Can I keep a status page private?
Yes, on Business and up. A page can have a password, and a protected page asks for it before naming an incident. You also choose whether search engines may index it.
Let your status page answer “is it down?”
Pick the monitors you already run. In about five minutes you have a live page customers can subscribe to.
Free plan · No credit card required · Set up in minutes