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
You can now integrate N-able N-central with Spike to receive real-time alerts when your monitored servers, networks, or endpoints encounter issues.
You can now test your alert channels instantly after setting them up.
Receive test alerts for phone calls, SMS, WhatsApp, Telegram, and Mobile app to make sure you are setup when incidents trigger.
Admins can test alert setups for other members as well.
You get 3 phone call and SMS tests per user per day.
Find it in Settings → Team → Send test alerts.
You can now test your escalation policies with one click shortcut.
Just hit “Test Escalation” on any escalation policy to create an instant test incident and run through the entire escalation flow.
It’s an easy way to verify your rules and routing before a real incident occurs.
From Spike's dashboard
c⌘ + ↵ (Mac) or ctrl + ↵ (Windows/Linux)That’s it — incident created.
It takes just 6 seconds (including 3 to type the title).
No forms. No clicks. No distractions.
We’ve expanded our Azure integration to support more services across Azure Monitor, Application Insights, Log Analytics, and Security Center.
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.