Instatus
Hosted status pages that tell customers about outages and maintenance, with built-in uptime monitors that can open incidents, and on-call schedules for the team behind them.
- What it is
- Incident management
- Used for
- Synthetic monitoring,On-call
- Type
- Commercial product
- Made by
- Instatus, Inc.
- License
- Proprietary
- Facts checked
- 23 October 2026
What it is
Instatus started as a cheaper, faster status page and is still built around one. You list your components (API, dashboard, payments), group them, and post incidents and scheduled maintenance with updates as they progress. Subscribers hear about each update by email, SMS, webhook, Slack, Microsoft Teams, Discord, Google Chat or RSS, and a public API lets customers pull your status into their own tools. Pages can be public, private behind a login, or on your own domain, and third-party components show the status of services you depend on, such as AWS or Stripe, so customers can see when a problem is upstream.
Monitoring came later. Website, API, cron heartbeat, ping, TCP, UDP and DNS monitors check from one location at a time, rotating between the United States, Canada, Europe and Asia; when one fails or recovers, Instatus can open or resolve an incident, publish it to the page and notify subscribers. Alerts from other tools, such as Datadog, can drive incidents through a webhook. For the team, on-call schedules with rotations, escalation policies and routing rules decide who gets the email, SMS or phone call. A REST API at api.instatus.com covers pages, components, incidents, monitors and subscribers. The free Starter plan includes 15 monitors at 2-minute intervals and 200 subscribers; Pro starts at $20 a month.
Why teams pick it
- A full status page with incidents, maintenance windows, private pages and many subscriber channels on a free plan
- Cheaper than Statuspage for the same audience: Pro, from $20 a month, covers 5,000 subscribers and 50 team members, where Statuspage’s Business plan charges $300 a month for 5,000 subscribers and 25 team members
- Monitors, on-call and the status page in one tool, so a failed check can update customers without a human in the loop
- Third-party components show customers when the outage is at a provider you depend on
Watch out for
- Monitoring is basic next to dedicated synthetics tools: no scripted browser journeys, and each check runs from a single location at a time, so it can’t confirm a failure from several places at once
- Closed-source SaaS: the status page is only as available as Instatus itself, and there is no self-hosted version
- Plan limits on subscribers (200 free, 5,000 on Pro) and on-call members push larger audiences to Business or Enterprise
- SAML single sign-on needs the Business plan, and SCIM, multiple SSO connections and an uptime SLA need Enterprise
Alternatives
What all incident management have in common →Compare side by side →
incident.ioCommercialIncident response run from Slack or Microsoft Teams, with its own on-call paging, status pages and an AI agent that investigates, sold as one SaaS priced per user.
RootlyCommercialIncident response from Slack, Microsoft Teams or Google Chat, with on-call paging, status pages, retrospectives and an AI SRE agent, configurable almost entirely through a Terraform provider.How it fits with other technologies
What Instatus uses
See it in a real stack
No architecture uses Instatus yet. Drop it into the playground and wire it up yourself.Open playground →Where it came from2019–2026
Ali Salah, a developer from Cairo, quit his job and started Instatus in June 2019. The market leader was Atlassian’s Statuspage, which tiers its plans by subscribers and team members. By 2020 Instatus pitched itself directly against it: a status page in 10 seconds, “10x faster to load than Statuspage”, at under 5% of the price, with unlimited teammates and subscribers on a flat $20-a-month Pro plan.
The speed claim came from architecture. Instatus called itself a Jamstack status page: each page was static, regenerated within seconds of an update and served independently of any backend, so it stayed up when the customer’s own systems and Instatus’s app did not. Monitoring was left to others, with integrations for Pingdom, New Relic, UptimeRobot, Runscope, Freshping and Datadog.
Salah ran Instatus as a small, founder-led company; by late 2022 he reported about $10,000 in monthly recurring revenue and more than 350 paying customers. Instatus then added its own monitors, on-call schedules and escalation, turning the status page into a small incident-response product.
Why it’s built this way
- Static status pages
- A status page must be up when everything else is down. Generating static pages that load without a backend made them fast and independent of Instatus’s own app.
- Flat pricing with unlimited teammates and subscribers
- Statuspage tiers its prices by subscribers and team members, so one flat price with no such limits was the clearest way to win small teams. Today’s Instatus plans do cap both, at higher numbers.
- Integrate with monitors first, build them later
- Early Instatus took alerts from existing monitoring services; built-in monitors and on-call came later so smaller teams could use one tool.
Timeline
- 2019
Ali Salah starts Instatus in June
- 2020
Pitches a Jamstack status page, 10x faster and 5% of Statuspage’s price
- 2022
About $10K monthly revenue and 350+ paying customers, per the founder
- 2026
Sells status pages with built-in monitors, on-call and escalation
Sources10 · facts checked 23 October 2026
- Instatus homepage
- Instatus pricing (checked 23 October 2026)
- Instatus help center
- Instatus help: Monitoring (monitor types, locations, alerts)
- Instatus help: On-call (schedules, escalation policies, routing rules)
- Instatus help: Subscribers (notification channels)
- Instatus help: Third-party components
- Instatus help: Datadog integration
- Instatus API reference
- Atlassian Statuspage pricing (checked 23 October 2026)