August 25
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
August 12
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.
August 07
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.
July 30
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.
June 29
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.
May 21
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.
April 30
Admin Portal
Notifications
Status Page
Incident Management
April 30
New
- Added a warning banner to the SMS verification screen so users are told why two-factor verification is being requested before they continue.
Fixed
- Fixed an issue where an update added with the "Add Post" button on a resolved incident was published as a root cause entry instead of a normal update.
- Fixed an issue where the auto-close message was cleared from the incident form whenever an existing incident was edited.
- Fixed an issue where a group mapped to all components was not included in the affected groups of a new incident.
- Fixed an issue where the component count shown on the groups list was wrong for groups mapped to all components.
- Fixed an issue where users whose account had been changed or removed saw a 500 error instead of being signed out.
- Fixed an issue where a service component could not be deleted.
- Fixed an issue where incident notification emails rendered font colors incorrectly in classic Outlook.
Maintenance
- Reduced false-positive monitoring alerts and log noise from expected 401 and 404 responses.
- Added caching to incident search so status page and admin incident lists load faster.
March 27
API
Admin Portal
Notifications
Beacons
March 27
New
- Added a new flag to the Status Page configuration, allowing administrators to disable CAPTCHA requirements as needed.
- Introduced support for templates within Beacon messaging rules, streamlining the creation of incidents.
- SMS notifications : The system now clearly distinguishes between new incident alerts and post-incident RCA updates.
Fixed
- Resolved an error occurring when moving subscribers via the API as a standard user. The behavior now correctly aligns with admin end of the application.
- Fixed a UI issue on mobile where the "hamburger" menu icon remained visible even when no navigation items were enabled in the page design.
- Patched a vulnerability where tokens from one page were inadvertently accepted on different page domains. Cross-page token authentication is now strictly prohibited.
March 04
Admin Portal
Status Page
Incident Management
March 04
Fixed
- 1 Resolved an issue where SSO-enabled employees were incorrectly redirected to the login page
- 2 Fixed an bug causing blank template names during incident creation.
January 27
Subscribers
Status Page
January 27
New
- SMS Security for 2FA Users
SMS Pumping Mitigation: Added rate limits to 2FA to prevent fraudulent high-volume messaging and toll fraud.
IP-Based Throttling: Users are now restricted to 5 SMS requests per minute per IP address to block automated bots.
Geo-Specific Controls: Implemented customizable delivery limits per country to manage regional risk and prevent cost spike