← Back to all sparks
S

StatusPal

INFRA · APIS
Velocity5.0

Hosted status pages and incident communication for SaaS teams

StatusPal Next keeps closing gaps with Classic, now with adjustable incident history.

status-pagesincident-communicationnotificationsmonitoringplatform-migration
◆Current state
StatusPal runs two tracks: Next gets the structural work, Classic gets incremental refinements. Next's latest release lets page owners choose how many days of past incidents show on the home page and relaxes password rules so password-manager output is accepted. The week before, Next added named service groups, maintenance reminders and stopped monitoring checks from overriding an open incident's status.
◆Where it's heading
Release by release, Next is accumulating the organizational and subscriber-communication features a status-page buyer expects: groups, calendar feeds, more channels, maintenance scheduling, and now configurable history. Classic keeps receiving usability fixes, so both products are maintained in parallel for now.
◆Prediction
Expect Next to keep shipping parity features at a weekly cadence. The entries don't indicate when Classic will be retired or how customers will be migrated.

◆Recent moves

  1. 10d 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 ↗
  2. 15d 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 ↗
  3. 24d 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 ↗
  4. 28d ago

    [StatusPal Classic] Easier incident tracking and dashboard updates

    Classic adds incident IDs, status filters and dashboard information notices. It is maintenance-mode polish that keeps the legacy product usable while investment shifts to Next.

    View source ↗
  5. 1mo ago

    [StatusPal Next] Reach customers through more notification channels: Google Chat, MS Teams & SMS

    Microsoft Teams, Google Chat and Twilio SMS join Slack as notification channels in Next. It widens where incident updates reach subscribers, a core status-page function.

    View source ↗
  6. 1mo ago

    [StatusPal Next] Clearer status updates and incident management

    iCal feeds give subscribers another passive way to follow a status page, and in-product guidance helps new incident managers. It continues Next's work to make status information easier to consume.

    View source ↗