Skip to main content

​
Platform status: incident history and your shareable status page

Settings → Platform status is the trust surface for your organization. It answers two questions in one place: has a platform incident actually affected my channels recently, and what link do I give my customers so they can see the same for themselves — under your own branding when you run a white-label domain. The page is split into the org-scoped incident history for you, and the white-label status URL you share outward. Both are read models over the same public incident feed Orbit publishes, so the figure you quote to a customer and the page that customer opens always agree.

​
Org-scoped incident history vs the share URL

These are two different views of the same incident feed:
  • Org-scoped incident history (your dashboard view). The headline indicator plus the incident windows that affected your organization’s channels across the current and previous month, split into Active now (windows still open) and Recent history (resolved windows). A component-scoped incident maps to the channels you actually use; a platform-wide window counts against every channel. Incidents whose declared component never touched your channel universe don’t surface here at all — you only see the windows that could plausibly explain a dip in your own traffic.
  • White-label status URL (your customers’ view). The public status page — overall indicator, per-component health, active incidents with their update timeline, recent resolved history, and scheduled maintenance, readable without an account. Resolve it under your own host when you have an active white-label custom domain so customers see your brand, not Orbit’s.
Read Active now first — it’s the difference between “a degraded number on your dashboard” (see below) and “a declared platform event.” Then recent history when you need the exact window to quote back to a customer or attach to an internal review.

​
What the shared page tells customers — and what it leaves out

The page your link opens tells the customer four things: the overall indicator (Operational, Minor, Major, Critical, or Maintenance), per- component health (SMS, WhatsApp, email, voice, video, AI agents, API — grouped), the active incidents with a timestamped update timeline, and the recently resolved history over the last fortnight. Scheduled maintenance windows are upcoming too. What it deliberately leaves out: your organization name, any other tenant, per-tenant data, and anything about your specific traffic. The page is a platform-level trust document — customers read it to time their own retries and acknowledge planned impact, not to get a peek at your account. That’s what makes the link safe to share. The link needs no credentials, and the page is safe to hand to anyone. Get the copy-safe shape straight from the dashboard so the host and locale are baked in:
  1. Open Settings → Platform status (owner or admin role — the dashboard gates it to the roles trusted to share org-scoped history).
  2. Click Copy link in the white-label block. A toast confirms the copy; if the clipboard write fails, the card shows the URL in a pre-format block you can select manually.
  3. Hand the URL out — paste it into an internal wiki, your status footer, or a direct message. Anyone who opens it reads the current platform status without logging in.
If a white-label custom domain is blocked out, the share URL still falls back to the platform host (orbit.devotel.io/{locale}/status) so the link is always shareable. Register and activate a custom domain under Settings → Branding, and the same page resolves under your own host via Orbit’s edge-resolution — then the copied URL points at your brand.
Don’t build the URL by hand-splicing a string you lifted from the browser address bar — the dashboard copy action guarantees it’s either your active white-label host or the platform fallback, never an org-scoped token or a ?tenant= parameter dangling in the copy. If you see any unexpected query parameters in the URL, go back and copy it again — the toast or manual-select path only carries the bare path.

​
What surfaces, and what doesn’t

Incidents that surface: platform-declared incidents whose declared component could have affected your channels, plus every platform-wide window. Scheduled maintenance also surfaces on the shared page, and it shows on that page regardless of whether it affected any channel. What doesn’t surface: tenant-level delivery failures that aren’t declared platform events — carrier rejections, unregistered senders, filtered content, insufficient wallet balance, malformed recipients. Those lower your channel’s delivery success without ever appearing in the incident history, and your customers won’t see them on the shared page either. Cross-check them against your own analytics and the delivery_health tier on the SLA report (see Monthly SLA and availability report). Also excluded from the org-scoped view: incident windows whose affected component never mapped to a channel you use (a video-only incident won’t shadow a tenant that only runs SMS and email). Embed the copied URL as a plain redirect or link — it’s a full public page, not an iframe snippet, so a target="_blank" anchor is the standard pattern:
Typical spots: your account portal footer, an in-app **?” menu, or your own status route that proxies to the link. When the customer hits the page the overall indicator plus per-component health answers the question “is Orbit down?” without a support ticket. For programmatic checks — uptime monitors, Slack bots, status badges — the page also exposes a JSON summary at /api/status and an RSS feed the customer can subscribe to with no account (see the Status Page API reference). The indicator derivation there mirrors the dashboard pill, so what your customers read and what you see never disagree.

​
Screenshot

Screenshot placeholder — capture Settings → Platform status with the indicator card, the white-label URL block (copy action visible), and the Active now / Recent history cards, and drop the image under apps/docs/images/guides/status-page.png. Use a tenant with an active white-label domain so the copied URL shows the branded host.

​
See also

  • Monthly SLA and availability report — the monthly attestation the org-scoped incident view draws from, with per-channel availability percentages, CSV export, and the SLA credit endpoint
  • Settings → Reliability in the dashboard — the month-picker rendering of the same report for a longer horizon than the two-month window here
  • Status Page API reference — the public incident endpoints, JSON summary, and RSS feed behind the shared link