LoginSign Up
← Back to all sparks
S

StatusPal

INFRA · APIS
Velocity5.0

Hosted status pages and incident communication for SaaS teams

statuspal.io ↗

StatusPal Next makes notices read the same across email, Slack and Teams.

status-pagesincident-communicationmonitoringplatform-migrationnotifications
◆Current state
StatusPal runs two tracks: Next gets the structural work and Classic gets reliability fixes. On 10 November Next made notice notifications consistent across email, Slack, Microsoft Teams and Google Chat, added About text, search-engine visibility, incident history limits and Reply-To addresses for status pages, and tied planned maintenance times to the page's timezone. Earlier in November Classic's Monitoring V2 began opening and closing incidents automatically, and Next added Critical incident templates.
◆Where it's heading
Next is collecting the page settings and notification behaviour that larger Classic customers rely on, which points to an eventual move off Classic. Recent releases favour consistency and control over new surfaces: matching labels across channels, timezone-safe maintenance and configurable page details.
◆Prediction
Expect more Next releases covering Classic features such as monitoring-driven incidents, and continued Classic fixes around migrations.

◆Recent moves

  1. 3d ago

    [StatusPal Next] Clearer notifications and more control over status pages

    Notices now show the same status, labels and colours across email and chat channels, status pages gain SEO, About and Reply-To controls, and maintenance times follow the page timezone. It is another batch of the admin depth Next needs before Classic customers move over.

    View source ↗
  2. 10d ago

    [StatusPal Classic] Smoother monitoring, and service management

    Monitoring V2 checks with auto-creation on now open incidents when a service goes down and close them on recovery, and service migrations survive webhook subscribers connected elsewhere. Classic is still getting fixes that matter for teams mid-migration.

    View source ↗
  3. 10d ago

    [StatusPal Next] Notice templates for Critical incidents

    Next adds notice templates for Critical incidents, including on existing pages. It is a small step in the run of incident-communication gaps Next has been closing against Classic.

    View source ↗
  4. 25d ago

    [StatusPal Next] More flexible security and incident history

    Page owners can now set how many days of past incidents appear on their status page, and long password-manager passwords are accepted. Both are small, but configurable incident history is the kind of public-page control buyers check for when comparing Next against Classic.

    View source ↗
  5. 1mo ago

    [StatusPal Next] Service groups, maintenance notifications, and consistent monitoring statuses

    Service groups and maintenance reminders are the kind of admin features Next needs before it can replace Classic for larger status pages. The monitoring fix matters as much: an automated check overriding a manually managed incident status is the sort of inconsistency that erodes trust in a status page.

    View source ↗
  6. 1mo ago

    [StatusPal Next] Clearer navigation and reliable service status updates

    Next gets a reorganized sidebar and a fix so API updates actually change global services' live status and the page's overall status. The fix matters more than the navigation: it makes the Global Services model dependable for automated status pushes.

    View source ↗