You can now use Change Integration in Alert Routing Rules to automatically route incidents to the right integration and team.
For example, an incident comes in under the API integration. But if its title contains "payments", Spike routes it to the Payments integration and alerts the payments team instead.
This way, the right team always gets paged with the right context. And over time, you can see which integrations receive the most incidents.
We also added two new routing conditions: Incident suppressed and Incident suppressed within a time window.
You can use these to switch integrations when an incident gets suppressed too many times.
For example, if an incident is suppressed 5 times, Spike can move it from the API integration to the Payments integration and start alerting the right team.
We added a new action in Alert Routing Rules called Route to other teams.
Now, when an incident comes in, you can automatically route it to the team that owns it.
For example, if Ops team picks up a security incident, you can route it to the Security team instead.
To set it up:
Toggle Route to other teams
Pick the destination team
Save the rule
You can also change the incident’s priority and severity while routing.
Once the incident is routed, the destination team’s escalation policies and alert rules take over, so the right people get alerted based on how that team works.
Alert Rules now support number comparisons under the Incident details condition.
You can choose from:
Greater than >
Less than <
Greater than or equal to >=
Less than or equal to <=
With these, you can create rules like setting priority to P1 if the CPU usage percentage is greater than 80. Or load a specific escalation policy if the number of days until SSL expiry is less than 3.
These operators give you more precise control over incident automations. You can triage, route, and run playbooks based on numerical values without manual intervention.
We updated the AWS integration to auto-resolve more incident types.
Simple Notification Service (SNS) incidents now resolve automatically when the underlying issue clears up. This reduces stale incidents on your dashboard.
You see only what actually needs attention, not incidents that are already fixed. This keeps your incident queue clean and helps your team focus on active issues.
Previously, only individual users could enable their Out of Office mode. Now, admins can add OOO for anyone on the team. This makes it easier to plan coverage, especially during holidays.
Also, now the entire team gets visibility into everyone's scheduled time off. They can see exactly who's away and when. This helps to fill gaps and keep rotations running smoothly.
You can now route alerts by day of the week using the new condition "Day of week" in Alert Rules.
This is useful if your traffic spikes on specific days. For example, you might want phone calls on high-traffic weekends but only Slack messages on slow Mondays.
It gives you more control over when and how your team gets alerted.
Now, you can automatically trigger incidents in Spike when Jira issues are created. So, if a bug gets logged in Jira, it instantly alerts the person on-call in Spike.
This keeps your dev and support teams in sync without manual pings.
Today, we are introducing some new on-call features: Add Gaps to on-call, Scheduled Layers, Handoff Days, and more. Flexibility in on-call schedules has been the single focus point in this release.
Add Gaps to on-call
Gaps let you insert an empty slot into a rotation. When a gap occurs, the next layer automatically steps in.
For example, you can set up a daily rotation like: Person A → Gap → Person B
You can add as many gaps as you’d like.
Scheduled layers
On-call Layers now support start and end dates.
If you need to set up holiday coverage now that automatically kicks in on December 25th and disappears after New Year's, then you can make that happen!
Every layer now has a "Set duration" option. Spike automatically activates the layer on the start date and deactivates it after the end date. No manual activation needed. Both start and end dates are optional.
Introducing day in handoff
You can now choose which day of the week your on-call rotation should switch—every Monday, every Tuesday, and so on. This gives you control over when handoffs happen, instead of tying them to the day the schedule was originally created.
It’s backward compatible as well, so you can add handoff days to your existing schedule.
More improvements
Ready-to-Use Schedule Templates: When creating a new layer, you'll see four pre-built templates: Weekday Layer, Weekend Layer, Night Shift, and Business Hours. Click one, and the time ranges and rotation patterns are already configured.
Holiday Calendar Integration: Add your company's holiday calendar to Spike, and holidays display directly on your on-call calendar. This gives you a visual reference while building schedules so you can spot conflicts early. There are plans to bring automation here. Please upvote on our roadmap.
