Spike.sh

Welcome to Spike, it's nice to meet you 👋 Spike is an incident response and management platform with real-time alerts, on-call scheduling, and branded status pages. We make sure the right person gets the alert at the right time. Follow us to stay updated on all our latest features and improvements https://spike.sh Hundreds of engineering & ops teams across the globe rely on Spike to keep things running smoothly so they can sleep peacefully at night. 💤 Since day one, we’ve handled ∟15M incidents and ∟1M alerts Real-time alerts get through, no matter what: ∟ 200K phone calls ∟ 100K WhatsApp/SMS/Telegram messages ∟ 500K Slack/MS Teams notifications ∟ Phone calls & SMS in 100 countries ∟ Discord & Email too Manage incidents directly from Slack & MS Teams, and enjoy flexible on-call management—whether it's 24x7 coverage or follow-the-sun models. Common on-call schedules are ➝ Follow the sun model ➝ 24x7 coverage ➝ Separate weekend shifts ➝ After office hours ➝ and so much more... Responders can plan holidays and time off easily with on-call overrides. Our branded status pages keep everyone in the loop, handling all communications with users, team members, and stakeholders during incidents. Ready to get started or switch from PagerDuty or OpsGenie? We’re here to help. Meet with us ↓ #devops #sre #incidentresponse #oncall #statuspages

Resolution Alerts At Spike, we’ve always focused on alerting you when incidents trigger. But we know the incident lifecycle doesn’t end there—it ends when the issue is resolved. ✅ Spike now sends alerts when incidents are resolved—whether automatically or by team members. You’ll receive updates via SMS, Email, App notifications, WhatsApp, or Telegram instantly (within 0.5s). Only those previously notified or active responders will get the alerts. Customize how and when you receive these alerts via Personal Settings > Modes or on the mobile app. Spike keeps you informed from the moment an incident triggers until it's resolved, so you can stay informed. Learn more → https://lnkd.in/g55ef6Qy #DevOps #IncidentManagement #IncidentResponse #SRE #Automation #alerting #oncall

Hide Graphs on Status Page Components You can now further customise your status page by hiding/showing historical status graphs on each component. This would focus only on current status of your service. This update is especially useful when managing multiple components and streamlining your status page view. This feature was developed in response to user feedback, and we’re pleased to make it available. To start customizing, visit the status page dashboard > Themes. https://lnkd.in/g4tVGtda #DevOps #IncidentManagement #StatusPage #SRE #incidentresponse 

We’re rolling out RSS feeds as a new subscriber option for all status pages. Every time you declare an incident or schedule maintenance, your status page’s RSS feed will update automatically. This opens up opportunities for automation through tools like Zapier, and now, subscribers can also receive updates directly via Slack and Microsoft Teams. This would make it easier for your subscribers to stay updated, whether they prefer email, Slack, Teams, or their favorite RSS feed reader. With real-time notifications, they’ll know about incidents and maintenance as soon as they’re declared. They also include maintenance reminders. #incidentresponse #devops #sre #devops #statuspages

Spike now supports Critical Notifications on iOS. These alerts will sound even if your iPhone is muted or in Focus mode. We enabled Critical Notifications to help you stay informed of critical incidents at all times. You can configure these special notifications directly in your app settings. Thanks to Apple for approving this and recognizing Spike’s commitment to delivering timely alerts. A big win for responders everywhere! #DevOps #sre #CriticalIncident #oncall #incidentresponse #incidentmanagement

∟Improved Links in Incidents Links in incidents have long been providing important incident context. The below improvements brings more flexibility and some critical updates in improving your processes. ∟Add and manage reference links Spike now generates neat previews of links found in your incident. You can also manually add links to an incident, and these updates will be reflected in all Slack and MS Teams alerts in real-time. ∟Automated adding links Automate adding reference links dynamically when an incident triggers. You will find a new Add links action in Playbooks. Using conditions, identify the incident and add links that matter. This is perfect for referencing internal docs, support channels, last merged PRs, and more. Since playbooks trigger on status changes, you can also automate adding more reference links when an incident is resolved. Head over to playbooks and select "Add Links" to start dynamically adding links when incidents are triggered or resolved. ∟Use cases 1. Reference internal documentation for incident resolution steps. 2. Link to relevant wiki pages for background information. 3. Attach GitHub repositories for related code commits. 4. Include monitoring dashboards for real-time status updates. 5. Add tickets for tracking related issues. #devops #sre #incidentmanagement #incidentalerts #alerts #incidentresponse #mttr #mtta #automation

Status Pages on Spike now comes with subscriber control. The goal is for you to have public status pages but control who can receive real-time status updates. Admins can configure settings for who can subscribe and who can unsubscribe. This would allow you to more precisely control your subscribers. ∟ Allow new subscribers (enabled by default) ∟ Control email domains allowed for subscription ∟ Do not allow unsubscribe (subscribers can’t unsubscribe themselves) Read the docs ➞ https://lnkd.in/gp6Cps8S Configure your status page's settings ➞ https://lnkd.in/gayrD_a7 #statuspage #incidentmanagement #configuration #incidentmanagement #spike #incidentresponse #devops #sre

Download On-call shift breakdown Starting today, you can download a detailed breakdown of every on-call shift for all responders in CSV. It provides insights into all the time responders have spent on-call. With remote teams in mind, the report includes shift timings in both user and responder time zones. Some benefits: ∟Accutate on-call pay calculation ∟Performance analysis ∟Resource planning ∟Compliance and audit Hit the Download on-call report, select a timeline and get the CSV. Available for all Early adopters, and Business plans and higher. https://spike.sh/on-call → https://lnkd.in/gB28n36M → #incidentresponse #devops #sre #oncall #incidentmanagement #oncallpay #responders #automation #accountability

Spike's iOS app is updated to make it super sleek and fast. It is rebuilt entirely in React Native. This version brings a massive improvement in terms of speed and responsiveness. The new architecture also enables us to roll out future updates much faster. Both iOS and Android apps helps you to ⎣ Incident notifications ⎣ On-call shift notifications (start and end) ⎣ Acknowledge / Resolve incidents ⎣ Set severity and priority iOS → https://lnkd.in/g5vyCNR6 Android → https://lnkd.in/gzGkmUPj #incidentresponse #devops #sre #oncall #incidentmanagement #alerts

We’ve improved daily on-call rotation alerts by consolidating multiple shift alerts into one single alert. For teams with multiple on-call responders and schedules, this will significantly reduce alert distractions. The 4 alerts below are now 1 single alert BEFORE └ 8:00am A shift ended for Primary oncall └ 8:00am B shift started for Primary oncall └ 8:00am C shift ended for Secondary oncall └ 8:00am D shift started for Secondary oncall AFTER └ 8:00am A shift ended for Primary oncall B shift started for Primary oncall C shift ended for Secondary oncall D shift started for Secondary oncall Support for Slack, Microsoft Teams, WhatsApp, Email, and Telegram are built in. Customisation options remain the same and all updates are Real-time as usual. These consolidated alerts are now live for all users. No changes are needed on your end. ➞ https://spike.sh/on-call #incidentresponse #oncall #alerts #slackbot #incidentmanagement #devops #sre #spike