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.
We now support NinjaOne, so you can monitor your IT infrastructure and get alerts in Spike.
Connect your NinjaOne account to Spike and route device monitoring alerts, endpoint security issues, and system failures to the right team.
This keeps your IT operations team on top of infrastructure issues without switching tools.
We also launched an inbound integration for Jira.
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.
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.
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.
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.
Plan better this holiday season 🎄
You can now link any external calendar like your company’s holiday list, personal calendar, or another team’s on-call schedule directly inside Spike.
Just paste your public calendar link and see everything in one view. Perfect for planning shifts around holidays, vacations, and regional breaks.
👉 Live now for all plans.
We’ve added a brand-new integration for MongoDB Atlas to automatically trigger incidents on Spike when alerts fire.
Key highlights:
Automatic incident creation – Incidents are triggered instantly from your MongoDB Atlas alerts.
Incident grouping – Related alerts are grouped into a single incident to reduce noise.
Alert suppression – Prevents duplicate alerts for ongoing incidents.
Auto-resolution – When the MongoDB Atlas alert state returns to OK, the incident is automatically marked as resolved on Spike.
This integration helps you monitor MongoDB clusters, performance metrics, and system health seamlessly without manual checks.
You now have more options for syncing on-call shifts with your calendar:
You can also sync with any calendar with Spike's unique link. Documentation is available for Google Calendar, Apple Calendar, Outlook, and others.
These options give you better control over what shows up in your calendar, so you're not overwhelmed with shifts you don't need to track.
You can now choose from 15 different ringtones for your mobile app alerts.
There's a ringtone for every notification type. Loud ones for critical incidents, subtle ones for low-priority issues, and quick reminders for resolve notifications.
This means you can instantly tell if you need to drop everything or it's just a heads-up.
You can now sign in to our mobile app using your company's SSO with SAML.
This removes friction for teams using enterprise identity providers. If you can log into Okta or your company's SSO system, you can log into Spike too.
Both features are now live on iOS and Android.
You can now apply actions to all incidents with the new "Apply to all incidents" condition in Alert Rules.
Previously, you had to use regex patterns like "incident title starts with /*/" to target all incidents. Now, just select "Apply to all incidents" and you're done.
This condition works for specific integrations and services too. For example, set all Datadog incidents to Sev1, or add resolve timers to all incidents from your payment service.
It’s a simpler, more convenient way to manage your incidents.
We’ve added a new way to automatically resolve incidents: Resolve Timer. Incidents now close on their own after a set time, which keeps dashboards clear of stale incidents and prevents old incidents from suppressing new alerts. Resolve Timer is available on all Spike plans starting today.
You can apply Resolve Timer in:
Directly on integrations — for all incidents triggering on an integration
Alert Rules — only for alerts that match certain conditions
Playbooks — as part of your automation chain