You no longer need to be a Spike user to create incidents from Slack.
Anyone in your workspace—clients, contractors, or teammates who aren't part of your on-call team can now use the /create-incident command.
Just add the Spike app to your Slack workspace, and everyone gets access to create incidents.
This makes it easier for your entire team to report issues, even if they're not part of your Spike account.
We've updated our Paessler PRTG integration.
It now auto-resolves incidents when the underlying issues clear up, so you won't see stale alerts cluttering your dashboard.
Also, incident titles are more descriptive and easier to understand at a glance.
This helps you better manage alerts from PRTG’s powerful monitoring of your entire IT infrastructure—including networks, servers, bandwidth, data centers, and more.
Spike now supports Live Call Routing in beta.
It’s a direct line that connects incoming calls to on-call engineers automatically. No more transferring calls or hunting down the right person.
Setup is quick:
After the call, you can create a new incident or link the call to an existing one.
Also, every call is logged with its recording and details, and a notification appears in your Slack or Teams channel.
Live Call Routing is now available in your account, and it works with your current schedules.
Our AWS integration now works across multiple AWS products including CloudTrail, CloudFormation, and others. You can connect everything with a single integration. No change is needed on your end.
The improved integration has better incident titles, auto-resolution, and grouping of incidents. This helps your team spot what’s important, group related issues, and respond faster.
We’ve upgraded our CrowdStrike integration to give you a richer set of security events. The integration now supports detection summaries, auth and audit events, XDR, and more.
You get more context and fewer duplicates for faster triage—all without writing any Title Remappers.
We’ve improved our Sentry integration to make incident titles much clearer and easier to understand. Now, error descriptions are more concise and to the point.
You can now choose who gets mentioned in Slack alerts from your escalation policies. Instead of always tagging everyone with @here, you can select:
@here@channelThis helps you cut down on noise and send alerts only to the right people. No more pinging the whole team for low-priority issues.
Note: By default, all your existing escalation policies mention @here.
We’ve made it easier to spot incidents that were auto-resolved.
On your dashboard and mobile app, these incidents now clearly show as Auto-Resolved instead of the regular status badge.
This makes it simpler to review incidents at a glance — especially with the growing number of auto-resolved alerts.
We’ve updated our Grafana integration to handle multiple events per alert more intelligently. Our data shows that nearly 6% of incidents from Grafana include multiple events — and now Spike will automatically destructure them to detect and apply any auto-resolving events.
This means fewer noisy incidents and better alignment with what’s actually happening in your systems.
No changes needed on your end. It just works.
You can now receive on-call shift notifications on specific Slack channels or Microsoft Teams channels for each schedule, instead of one global channel for everything.
Set up different channels for different on-call teams—Backend notifications go to #backend-oncall, Frontend to #frontend-oncall, and so on. You can also add multiple channels to one schedule if needed.
To set it up:
→ Go to your on-call schedule, click settings, and select Slack or Teams
→ Add your preferred Slack or Teams channels
Now, each team only sees the shift changes that matter to them. This cuts down noise and keeps notifications relevant, so important alerts don’t get buried in unrelated team updates.
On-call shift changes can now trigger webhooks to external systems—perfect for teams to extend automation when shifts rotate.
When shifts start or end, Spike triggers a GET/POST/PUT request to your webhook with shift details. Use this to notify external team members via SMS, mobile app, or any other system.
Find the Webhook section in your on-call settings and get started.
With our new Time of day alert condition, you can now trigger different actions for the same incident based on when it happens.
For instance, you can configure a Slack notification during the day, but a phone call alert if the same issue happens at midnight.
You can also
Change the escalation policy to wake people at midnight
Lower noise from low-severity alerts after hours
Set a higher priority on incidents after hours
To set it up: