Changelog

The biggest release yet: a new Knowledge Base and Developer Portal for your customers, shareable Uptime Certificates, a public Roadmap, and a top-to-bottom overhaul of support-ticket resolution.

New: Knowledge Base ("Docs")

• Publish a branded, searchable Help Centre on your status page — articles organised into categories, including step-by-step Guides.
• Readers get an automatic "On this page" table of contents, breadcrumbs, and a "Was this helpful?" feedback widget.
• A full rich-text editor for your team: image uploads, autosave, safe editing of published articles via working copies, live presence, and revision history with one-click restore.
• AI-friendly: every article offers Copy as Markdown, a plain .md view, and an llms.txt index so assistants can read your docs cleanly.

New: Developer Portal

• A per-tenant API reference on your portal with a live, interactive OpenAPI explorer.

New: Uptime Certificates

• Shareable, tamper-evident proof of uptime — a public certificate page (with print-to-PDF) you can hand to customers and prospects.

New: Roadmap & Feature Requests

• A Feature Requests queue to triage what customers are asking for.
• A public Roadmap where customers see what's planned and mark themselves "interested," and get notified automatically when a request they backed is declined or shipped.
• Interest counts from other organisations are never shown to customers.

Support tickets (major overhaul)

• Outcome-first Resolve flow — resolve through one modal and pick an outcome (Solved, Won't do, Feature request, Duplicate, No response); the form adapts, with an optional closing message in the same step.
• One terminal state — "Closed" is gone; tickets are Resolved, with the outcome recorded and a 7-day breakdown on the dashboard Pulse.
• Link as you resolve — tie a ticket to a feature request or mark it a duplicate right from the Resolve modal, with search.
• "Send & resolve" carries your typed reply into the modal (draft kept safe) — reply and close in one move.
• First-class Reopen with reopen counts; customers can reopen from their portal for 14 days after resolution.
• One-click claiming — assigning a new ticket auto-claims it to In progress; "Assign to me" is a single keystroke.
• Command palette (Cmd-K) drives the whole ticket; redesigned ticket view with a chip bar, Lead + Collaborators, and in-place subject/description editing.
• Stale-ticket follow-up — automatic "still need help?" nudge after 7 days, auto-resolve after 14 with a reopen window.
• Customers are now emailed on resolution and on every reply, linking back to their portal thread.

Your status portal

• New 4-state public status model with per-component incident overrides and clearer component descriptions.
• Portal branding — set a brand colour with a live preview; one consistent, branded header and navigation across the portal.
• Scheduled maintenance references (e.g. MNT-202606-001) and a per-window manual/auto-close choice.
• Clearer sign-in wording, page titles/subtitles, and breadcrumbs throughout.

Across the app

• Notifications moved to a header bell, top-right.
• A unified design system — consistent buttons, pills, and cards, and pop-up menus that no longer clip.
• Unified date/time tooltips with timezone info everywhere.

SLA

• Resolution SLA now runs on wall-clock (never pauses) for an un-gameable start-to-finish time, while first/next-response clocks respect business hours.

Uptime checks now capture detailed timing data for every request, giving you deeper visibility into where response time is spent.

Each check result now shows:

• DNS lookup time — how long it took to resolve the hostname
• Connect time — TCP connection and TLS handshake duration
• Time to first byte (TTFB) — how long the server took to start responding
• Resolved IP address — the exact IP your check connected to

These timings appear inline on every check result, making it easy to spot whether slowdowns are caused by DNS, network connectivity, or the server itself.

We've also improved the Run Now button so it always executes immediately, even if the check was recently run.

Uptime checks can now be configured with a slow response threshold which will be reflected on the response time graphs, and provide an additional alerting opportunity.

You now have the ability to properly schedule maintenance. You can load them in advance to notify your users, and manually start them to disable alerts during a possible downtime windows.

Scheduled maintenance is show to users on the status page, and historical maintenance windows when selecting viewing the affected date directly.