Groups Admin Portal Subscribers Beacons Services/Components Status Page Incident Management
November 17
New
  • Remind at start for beacon maintenances. Beacon rulesets that create a Scheduled Maintenance now have a “Remind at start” option, on the default incident type and on each type rule. Turn it off to skip the email at the start of the maintenance.
  • Remove a user from one status page. The Users tab has a new action, “Remove From This Page”. The user keeps their login and their access to your other pages.
  • Export after “select all records”. On the Subscribers page, Export now covers every subscriber that matches your search and filters, across all pages. With no search or filter, the full export is emailed to you as a download link.

Security

  • Password reset links now expire after 30 minutes and work one time only. The reset page limits repeated attempts.
  • A password change now signs the user out of all other sessions. The browser that made the change stays signed in.
  • “Maximum password re-use history” now applies on every screen where a password can change, including the admin profile.
  • “Force password reset after (x) days” now counts from the last password change.
  • Status pages with Issue Reporting turned off no longer accept problem reports.
  • SMS and sign-in rate limits are applied consistently.

Improved

  • Status pages with large incidents and many subscriber groups load much faster for signed-in subscribers.
  • After you sign out of a page that uses single sign-on, the login page shows a “Sign in” button and does not sign you back in at once.
  • StatusCast support staff no longer appear in your user lists or pickers. Where they acted on an incident, they show as “StatusCast Support”.
  • Application Performance Service beacons now appear in the Create Beacon test window.
  • The subscriber Activity Feed now shows when a subscriber was deactivated, with the reason (for example, a bounced email).
  • Reordering components no longer fills the audit report with one entry per component.
Fixed
  • New subscribers on single sign-on pages could get a 401 error on first sign-in when the account had reached its manager and admin limit.
  • A subscriber deleted and added again as Employee was saved as Subscriber.
  • Service CSV import could go past the component limit of the plan. The result email now names the limit and lists each row that failed.
  • The hourly Subscription Deactivation Report counted the same subscriber more than once.
  • Incident and Incident SLA reports failed when filtered by group.
  • Deleting a user could fail partway.
  • Users with access to several accounts could sign in with the wrong role.
  • A slow or interrupted connection could show “Incident not found” when posting an incident update. You now get a clear message to try again.
  • Beacon rules with a wait time and an empty incident title now notify admins at once.
  • Broken or mistyped links to admin pages and sign-in pages now show a clear message or the list page, not an error page.
  • Third-party status feeds for MixMax, TeamDynamix, Veeva and Panopto missed some incidents


API Admin Portal Notifications Status Page Incident Management
October 30
New

Opt-in settings (these are off by default, there is no change until they are turned on)

  • Added the Allow Duplicate External IDs setting under Incidents, which lets more than one open incident on a page share the same External ID.
  • Added a setting that lets external subscribers sign in with a password on pages that use Xurrent sign-in, while internal users keep the Sign in with Xurrent button.
  • Added a setting to turn off password login for roles that use single sign-on, so those users must sign in through their SSO provider.

Applies to all pages

  • Added the Twilio error code and reason to failed SMS rows in the Deliveries report and its CSV export.
Fixed
  • Fixed an issue where SMS delivery statuses did not update in the Deliveries report and subscribers with permanently failing phone numbers stayed subscribed to SMS.
  • Fixed an issue where the Incidents API returned an error for incidents whose root cause was no longer available.
  • Fixed an issue where saving a large brand template did not record an audit log entry.
  • Fixed an issue where Microsoft Teams notifications failed for incidents with many affected components and Teams connection errors showed a generic error in the admin portal.
  • Fixed an issue where third-party cloud provider incidents were imported in bulk as new incidents, which sent notifications for old events.
  • Fixed an issue where the summary.json feed and the API returned a server error for cached or interrupted requests.


Admin Portal Notifications Subscribers Status Page Incident Management
October 07
New
  •  Added a Selected Range column to the Uptime SLA report, so the date picker now drives the tables and the CSV export.
  • Added a Group Deleted entry to the Audit report that shows who deleted a group and from where.
Fixed
  • Fixed issues on the Dashboard, Incident, Incident SLA and Uptime SLA reports where incident counts, weekday and hour groupings, downtime figures and time between incidents were wrong or did not match the Incidents list.
  • Fixed an issue on the Incidents list where statuses could not be combined and the View Incidents link ignored its type filter. The type filter now accepts several types.
  • Fixed issues where auto-closed maintenance showed as In Progress, and the Incident List widget's open maintenance filter hid maintenance already in progress.
  • Resolved an error occurring when deleting a group, which also removed the group's services without deleting the group.
  •  Fixed issues in subscriber bulk actions where Select All ignored the active filter, the component filter missed parent and sub-component subscribers, and adding or removing a component mishandled subscribers on all components.
  • Fixed issues where new SSO and API subscribers showed as subscribed to SMS without a phone number, and SMS subscribers were unsubscribed after failures not caused by their number.
  • Fixed an issue where a subscriber without a sign-in account got no email after a password reset request. An invitation to set a password is now sent.
  • Fixed an issue where notifications were not sent for incidents that affect a very large number of components.
September 02
Notifications Subscribers Status Page Incident Management
September 02
Fixed
  • Fixed an issue where, when cached incident component data was inconsistent,  status pages may fail to load.
  • Fixed an issue where incident posts created from saved templates could lose the component list and the text after it on publish.
  • Fixed an issue where subscribers who texted STOP to opt out of SMS had their phone number erased and could not opt back in with START.
  • Fixed an issue where some third-party provider incidents stopped copying to some status pages, so subscribers on those pages were not notified.
API Admin Portal Notifications Subscribers Beacons Status Page Incident Management
August 25

Fixed
  • Fixed an issue where scheduled maintenance appeared in the admin services grid only on its start day instead of across its whole window.
  • Fixed an issue on the Status Page history grid where scheduled maintenance without an estimated duration was not shown.
  • Fixed an issue where the bulk Modify action on the Subscribers page showed "No Components", preventing components from being added to or removed from subscribers.
  • Fixed an issue where the auto-close toggle was missing when editing an existing incident.
  • Fixed an issue where subscriber email notifications could be switched off without the subscriber's action and without appearing in the deactivation report.
  • Fixed an issue where incidents copied by an internal beacon arrived with notifications disabled even though the beacon was set to notify subscribers.
  • Fixed an issue where the Get Incident API returned "not found" for draft incidents to admins, and searching by incident number failed.
  • Fixed an issue where third-party status page beacons stopped detecting outages after the provider's feed address changed; the feed is now discovered automatically.
  • Fixed an issue where an information post that was first drafted as an outage stayed open after publishing, and where a post drafted as information then changed to an outage closed on publish.
  • Fixed an issue where posts added to a draft incident could be marked as published.
  • Fixed an issue where Incident Exports returned an error, or the export email never arrived, for incidents created through the queue API.
  • Fixed an issue where the fullscreen incident post editor was hidden behind the admin portal sidebar.
  • Fixed an issue where incidents imported from a status page provider without a component list were silently dropped instead of being attached to the root component.
  • Fixed an issue where status page beacons whose provider returned an error or redirect page showed stale component status.
  • Resolved an error occurring when a cached status page entry could not be read, which caused status pages and the Incidents API to return errors, including after deployments.
  • Fixed an issue on the Uptime SLA Report where an incident spanning midnight was charged to a single day instead of split across both in the page timezone.
  • Fixed an issue where the Calendar Widget ignored the Week and Day display setting and always showed the month view; visitors can now switch between month, week and day.
  • Fixed an issue where Calendar Widget event tooltips appeared above the calendar, or not at all, in week and day views


API Admin Portal Subscribers Status Page Incident Management
August 12
New
  • Added rate limiting to the sign-in and password reset forms, limiting repeated attempts from a single source address. 
Fixed
  • Fixed an issue where API integration tokens created on behalf of another user were issued with the creating administrator's permissions instead of that user's own role.
  • Fixed an issue where incidents saved as a draft with auto close enabled closed immediately on publish rather than at the configured time.
  • Fixed an issue where the audit report and subscriber tile counts used the viewer's browser timezone, so records near midnight were counted on the wrong day.
  • Improved status page load performance, most noticeably on mobile.
  • Patched high severity vulnerabilities in third party components used for email delivery, data mapping and XML signature handling.
Notifications Beacons Incident Management
August 07
Fixed
  • Fixed an issue where the same incident or scheduled maintenance could appear multiple times in incident list widgets for signed-in subscribers who belong to more than one group.
  • Fixed an issue where incidents imported from a third-party provider status page were re-saved on every poll, adding repeated "Incident Edited" timeline entries and notification emails.
  • Fixed an issue where a provider's resolution update was not applied to an incident that had already auto-closed, leaving the last visible update stuck at monitoring.
  • Fixed an issue where updates to long-running incidents imported from a provider status page could time out and fail to reach the page.
  • Fixed an issue on Beacons where a rule whose component expression matched nothing stopped the beacon from processing instead of extracting no components.
  •  Fixed an issue where notification emails sent through a custom SMTP server could be dropped when the mail server closed the connection mid-send.
Maintenance
  • Reduced repeated retries and error noise when a beacon rule builds an incident that fails validation, so a misconfigured beacon is now reported once.
  • Internal tooling and build maintenance with no change to product behavior.


Notifications Subscribers Beacons Status Page Incident Management
July 30
New
  • Added the ability to map an OpenID Connect group claim to status page groups, so group membership is provisioned and removed by the identity provider at sign-in.
  • Added the ability to suppress notification emails when bulk-adding subscribers.
Fixed
  • Patched a vulnerability where an API integration token kept working after it was deleted; deleted tokens are now rejected immediately.
  • Fixed an issue where a beacon on an internal or external status page failed with an error and created no incident whenever a ruleset was attached.
  • Fixed an issue where a beacon published incidents automatically even when its integration was configured not to.
  • Fixed an issue where deleted beacons continued to generate "component mapping missing" admin emails from third-party provider incidents.
  • Fixed an issue where the HTML widget ignored a group applied from the page URL while other widgets honored it.
  • Fixed an issue where component status widgets set to hide when empty were still shown as an empty box for subscribers whose group had no visible components.
  • Fixed an issue on the History Grid where recurring future maintenance was displayed incorrectly.
  • Fixed an issue where system admin notifications continued to be sent to a user after their administrator role was removed.
  • Fixed an issue where administrators belonging to another company received system admin notifications without appearing in the Users list.
  • Fixed an issue where the Subscriber Report grouped subscriptions by UTC date rather than the page's time zone, shifting counts by a day.
  • Fixed an issue where the incident end date macros rendered empty when an incident was resolved from the incident edit screen.
  • Fixed an issue where the Groups settings page was slow to load on pages with many groups.
Maintenance
  • Added logging when subscribers are unsubscribed at the SMS provider.


API Subscribers Status Page Incident Management
June 29
New
  • Added a keyword search to the public incident history page so visitors can find incidents by title, incident ID, or update text.
  • Added an incident duration macro for use in incident updates and notification templates.
Fixed
  • Patched a vulnerability by updating the bundled jQuery Validation library to a current release.
  • Fixed an issue where the incident history page could time out on pages holding a large number of incidents.
  • Fixed an issue where the Subscribers page intermittently failed to load its list of services.
  • Fixed an issue where incidents submitted through the API with historical timestamps failed to save their updates.
  • Fixed an issue where the incident end date macros rendered empty when an incident was resolved from the admin portal.
Admin Portal Subscribers Beacons Status Page Incident Management
May 21
New
  • Added the ability to send notifications to Slack or Microsoft Teams directly from a Beacon rule.
  • Added a configurable single sign-on logout URL so users are returned to the identity provider when they sign out.
Fixed
  • Fixed an issue where the Affected Groups field on a new incident was pre-populated with every group.
  • Fixed an issue on the History Grid where an incident spanning consecutive days left one of those days blank.
  • Fixed an issue where the auto-close option was switched off when the incident start date or time was changed.
  • Fixed an issue where auto-close could not be enabled for incidents in a maintenance status.
  • Fixed an issue where the start date and estimated end date could not be amended on a draft incident.
  • Fixed an issue where the groups screen did not indicate that no components were selected.
  • Fixed an issue where subscriber invitations ignored the advanced subscriber security setting.
  • Fixed an issue where incidents on components marked "treat as cloud component" were excluded by the local and cloud incident filters.
  • Fixed an issue where the subscriber count on the Groups page did not match the Subscribers page.
  • Fixed an issue where the Users list displayed the wrong created date for an admin user.
  • Fixed an issue where the users API returned users belonging to pages no longer linked to the company.
  • Fixed an issue where Google Analytics cookies were stored on status pages that had not installed the integration.
Maintenance
  • Added operator logging for subscriber-limit failures during single sign-on, page deactivation, and provider imports.
  • Reduced log volume for image uploads and improved cached list serialization.