Status page

A status page is a public state page for your service: a list of components (site, API, payments, account) with an “operational / degraded / down” indicator, an incident history with updates, scheduled maintenance announcements and an uptime percentage. Users and clients can subscribe to notifications and learn about outages first. When something goes down, the status page takes over the communication: fewer “is it down for you?” calls and less panic. Ready services (Statuspage, Instatus) are cheap and fast — for a standard page they are often enough, and if so, use a ready one. Your own status page pays off when you need more: complex architecture (several regions, component dependencies), deep integration with your monitoring, SLA or compliance requirements, hosting in your own environment, no per-subscriber fee with a large audience and a single brand. The base price starts from 60,000 ₽; the total depends on the number of components, subscriptions and integrations.

• During an outage, users flood support with “is it down for you?” — load at the worst moment.
• Clients do not know what happened and when it will be fixed — frustration and churn grow.
• There is no place to honestly show uptime and incident history — this lowers trust in the service.
• Scheduled maintenance catches users off guard — no one warned them.

• Service components with status: operational / partial outage / down
• Incident history with updates: what happened, what we are doing, when it was fixed
• Scheduled maintenance announcements with date and time
• Uptime metrics: availability percentage by component and over a period
• Notification subscription: email, Telegram, SMS, webhook (of your choice)
• Your own brand and domain (e.g., status.yoursite.com), hosting in your own environment
• Monitoring integration: automatic status updates when you have monitoring or an API — separate integration work (optional)
• Responsive, fast loading; SEO foundation

• Fewer requests during an outage — users see the status themselves
• Honest communication builds trust — clients see you keep everything under control
• Subscribers learn about outages and maintenance first — without panic and guesswork
• The uptime history is visible — an argument in negotiations and for an SLA

• You leave a request and describe the service components and notification channels
• We design the components, incidents, subscriptions and monitoring integration
• We develop, connect notifications and launch

• How is your own status page better than ready services (Statuspage, Instatus)?

  Ready services are cheap and fast — for a standard page they are often enough, and that is a fine choice. Your own pays off with complex architecture (several regions, component dependencies), deep integration with your monitoring, SLA or compliance requirements, hosting in your own environment, a large subscriber audience (no fee for volume) and a single brand.

• Can the status be updated automatically from monitoring?

  Yes, if you have monitoring with an API or webhook — we connect it so the status changes automatically on an outage and notifications go to subscribers. If you have no monitoring, we will help set up checks — this is separate integration work.

• How much does it cost and what does the price depend on?

  The base price starts from 60,000 ₽ for a status page with components, incident history and subscription. The price includes a custom design, development for your stack and environment, subscription and notification setup, and a one-time rollout without a monthly fee. If a ready service on a subscription is enough, it is cheaper to start with. Auto-updates from monitoring, SMS and complex integrations are estimated separately.