Status Pages

A public status page your users actually trust

Publish a hosted status page for your product, keep component states honest with uptime monitors, post incident updates as you work, and let users subscribe by email — in English, Arabic, or both.

When something breaks, say so — before support tickets do

During an outage, silence is the most expensive message you can send. Users refresh, retry, and file duplicate support tickets; your team answers the same question in ten channels while also trying to fix the problem. A public status page turns that chaos into one URL: here is what is affected, here is what we know, and here is the latest update. The teams that communicate well during incidents are remembered for the communication, not the outage.

AllStak gives you a hosted status page at allstak.sa/status/your-page with nothing to deploy. Define components for the parts of your product users care about, mark them operational, degraded, or in outage, and publish incidents with running updates. Connect uptime monitors so component status reflects what your checks actually observe, and let users subscribe by email — with verified subscribe and unsubscribe. Because AllStak is built bilingual, your status page speaks English and Arabic, which matters when your users do too.

What AllStak status pages include

Everything a public status page needs to be believed: honest component states, timely incident updates, and subscribers who hear it from you first.

Hosted, nothing to deploy

Your page lives at allstak.sa/status/your-page and is served by AllStak — no static site to build, no separate service to keep up while your own systems are down.

Components with clear states

Model your product as components — API, dashboard, ingestion, payments — each showing operational, degraded, or outage, so users see exactly which part is affected.

Incidents with running updates

Publish an incident on the page and post updates as you investigate, mitigate, and resolve — the full narrative stays visible so users stop guessing.

Email subscribers, verified

Users subscribe to your page by email with verified opt-in and one-click unsubscribe, so incident notices reach people who asked for them.

Uptime monitors drive status

Connect AllStak uptime monitors to components so the page reflects what your checks actually observe — status your users can verify against reality.

Bilingual English & Arabic

Status pages render in English and Arabic with proper RTL — your Saudi and GCC users read incident updates in their language, not a translation afterthought.

Publish your status page in minutes

  1. 1
    Create your page

    Pick a slug and your hosted page goes live at allstak.sa/status/your-page — no DNS, no deployment, no extra infrastructure.

  2. 2
    Add components and connect monitors

    Define the components users care about and link AllStak uptime monitors to them, so status reflects real check results rather than manual edits alone.

  3. 3
    Publish incidents as you work

    When something breaks, open an incident on the page, set the affected components, and post updates through investigation, mitigation, and resolution.

  4. 4
    Let users subscribe

    Share the page URL. Users subscribe by verified email and hear about incidents from you first — instead of discovering them through failures.

Why teams publish status with AllStak

  • Cut duplicate support tickets during outages — one URL answers "is it down?" for everyone at once.
  • Status backed by real checks: uptime monitors drive component state, so the page reflects reality rather than optimism.
  • Subscribers hear it from you first — verified email notifications turn outages into managed communication instead of rumors.
  • The only status page that speaks Arabic natively — EN + AR with proper RTL for your users in Saudi and the GCC.
  • No separate status-page vendor: it ships inside the same platform and bill as your uptime, errors, logs, and infrastructure monitoring.
  • Start free with SAR pricing and data residency in Saudi Arabia.

Status page FAQs

What is a hosted status page?

A hosted status page is a public page, served by your monitoring provider, that shows the live health of your product's components and the history of incidents. With AllStak, your page lives at allstak.sa/status/your-page — there is nothing to deploy, and it stays up even when your own infrastructure does not.

How does it compare to Statuspage or Better Stack on cost?

Statuspage and Better Stack price status pages as a product or tier of their own. With AllStak, the status page is included in the same platform and bill as uptime monitoring, error tracking, logs, and infrastructure — with SAR pricing, a free tier, and bilingual English/Arabic pages that neither offers natively.

Can uptime monitors update component status automatically?

Yes. You can connect AllStak uptime monitors to status page components so component state is driven by what the checks observe. You can still publish incidents and updates manually for the human narrative around what is happening.

How do subscribers work?

Users subscribe to your status page by email. Subscriptions are verified — a confirmation step prevents someone signing up another person's address — and every notice includes unsubscribe. Subscribers are notified about the incidents you publish on the page.

How long does setup take, and is it free?

Minutes: pick a slug, add components, and the page is live. Status pages are available on the free tier without a credit card, with SAR pricing as you grow — and your data stays in Saudi Arabia.

Put your status on the record — start free

Create your hosted status page, connect your uptime monitors, and give users one trustworthy URL for the next incident — in English and Arabic, on the same platform as the rest of your monitoring.