New features and major updates to ServiceAlert.
Receive product release announcements by email.
Browse all monitor types in one compact list, group them by service, tag or type, and search across paginated results. Health counts are separate from missing alert routes. History loads for the displayed page.
View monitorsSave named connections for a team, including multiple destinations for the same provider. Run history distinguishes provider acceptance, rejected requests and unconfirmed delivery. Supported rate-limit rejections can retry automatically, with up to three attempts.
Manage workflow connectionsJira workflow alerts reuse the recorded issue for routed status updates and recovery comments. Workspace Jira connections can also apply a configured transition on recovery. Run history links to the recorded issue.
Configure Jira routingConnect a Teams Workflows webhook to receive service and monitor alerts as Adaptive Cards. Existing Microsoft Graph connections show a reconnect notice with setup instructions. Saved webhook URLs remain private.
Set up Teams alertsStarter costs $29 per workspace per month and includes 20 vendor services, 10 one-minute monitors, one status page, 30-day history, and standard chat and webhook alerts. Eligible accounts can try Starter, Team or Business for 14 days without a card. Existing Pro subscriptions keep their current terms.
Compare plansAdd an acknowledgement wait to SaaS and monitor alert workflows. If nobody acknowledges, notify another destination or email the current on-call responder. Acknowledgement or recovery stops pending notifications. Includes a five-minute escalation template and delivery history.
Open the integration editorRoute monitor outages, recoveries and expiry alerts in the integration editor. Filter by monitor or check type, choose delivery destinations, set hours and delays, and review delivery history. Available on Starter, Team, Business and Enterprise.
Open the integration editorRoute watched-service alerts with templates, product and region conditions, delivery hours and delays. Review delivery history and replay events without sending messages. Teams can use shared connections with existing access permissions. The editor includes undo, redo, branch duplication, double-click branch creation, card dragging, canvas panning and recovery of unsaved edits in the same browser tab. Available on Starter, Team, Business and Enterprise; existing Pro subscriptions retain their routing access.
Open the integration editorAdded official status feeds for 49 services, including Manus, Firecrawl, Apify, N-able, Action1, Deel, Mercury, Raycast and ScrapingBee.
View the service directoryAdded status pages for GitHub Actions, Copilot, Claude Code, IT Glue, and Autotask. Each page shows official status, related incidents, and alert options.
View Claude Code statusGitHub and Zscaler status pages now support filters for supported products, clouds, or locations. Saved filters also apply to alerts. The “Am I affected?” check compares reported symptoms with official updates and provides a summary to copy into a support request.
View Zscaler statusAdded a one-time email alert for individual incidents. The watch lasts up to seven days and sends an email if the provider confirms resolution during that time. It does not subscribe you to other incidents for the service.
Browse current incidentsStatus pages show community report charts and a regional report map alongside official incidents and maintenance. Official updates and user reports are labeled separately. GitHub and Zscaler reports also support additional details and a follow-up when service recovers.
View GitHub statusAdded guides for queued GitHub Actions jobs, Azure DevOps agent waits, Cloudflare gateway errors, Zscaler connection problems, and Claude issues. Each guide includes troubleshooting steps and links to official sources.
Read the troubleshooting guidesAdded embeddable status badges and cards with Markdown and HTML snippets. Cards support light and dark themes and display the status source and last check time.
Create a status badgeStatus pages can now be unlisted or password-protected. Public pages also support incident-update emails for subscribers and embeddable status badges.
Edit a status pageAdded conversion goals, funnel reports, and optional aggregated click and scroll heatmaps. A multi-site overview shows traffic and conversion totals for each site. Analytics alerts support configurable thresholds.
Open Web AnalyticsThree new monitor types check common blocklists, crawl a page for broken links and mixed content, and record scheduled Lighthouse results. They use the same alerting and incident history as other ServiceAlert monitors.
Create a monitorA public status page can now show the current status of selected third-party providers. Provider issues appear as context and do not change the status of your own components.
Edit a status pageThe Slack integration can collect monitor evidence, recent deployments, and related incidents in one investigation thread. A person reviews the findings before they are promoted to an incident update.
Open incident managementInstall a monitoring agent in a cloud region, data center, or private network. Monitors can require any, a majority, or all selected regions to fail before an alert is sent.
View monitoring agentsTeams can create rotation schedules, publish an iCal feed, request shift coverage, and use the active on-call responder when assigning an incident commander.
Set up on-callPublic status pages can use a verified customer domain. The setup checks domain ownership, guides the required DNS change, and provisions TLS for the status-page hostname.
Configure a custom domainTransaction monitors can run browser steps for sign-in, checkout, and other JavaScript flows. Each run records the first failed step and its timing.
Configure a transaction monitorWeb Analytics now separates connection stages and groups results by country, connection type, and CDN point of presence when that information is available.
Open Web AnalyticsMonitors can be grouped under a named service such as Checkout, Authentication, or API. Incidents, on-call schedules, and status-page components can use the same service grouping.
Open servicesHTTP monitors now support mTLS, OAuth client credentials, and JSON assertions. An existing monitor can also be cloned and retargeted.
Open monitorsMonitor, team, service, and MCP guides are available without signing in. The REST API reference is public as well.
Read the help centerTeams can declare an incident, assign responders, post timeline updates, publish selected updates to a status page, and coordinate through a Slack incident channel.
Open incident managementServiceAlert alerts and recoveries can open, update, and resolve incidents in an existing PagerDuty or Opsgenie workflow.
Configure integrations