Seven changes to how you work with incidents.

• Export incidents to CSV from the table. Pick a date range, keep whatever the table is already filtered by, and the file builds in the background.
• Delete an incident for good, one at a time or several at once. There is no undo, so it asks first, and the audit log keeps a row of who deleted what and when.
• Reference one incident from another. Mention an incident in a note with @ID and the two are linked both ways.
• Read timestamps whichever way suits you. A row can say triggered 3 minutes ago or give you the exact time.
• Incident emails now carry the alert's payload, with the fields that matter called out above it.
• Write, pin and archive notes with an API key, so a script or an agent can work on an incident without borrowing someone's login.
• Incidents load faster, and the difference is largest if you have a long history of repeated alerts behind you.

Open incidents →

Read the notes API docs →

Every open incident now has a Page button. Use it to pull someone in right away instead of waiting for an escalation to work its way to them.

Each person's row has three buttons.

• Bell reaches them on the app, by email, and with a Slack or Microsoft Teams DM.
• App sends a critical notification that breaks through Do Not Disturb and the silent switch.
• Phone rings their telephone. This one is on Business and above.

You can page people on the incident's own team, someone from another team, or another team's on-call. It works in the mobile app too.

Every page goes into the activity log with who sent it, who got it, and on which channel, so a page is as easy to trace as any other action on the incident.

A page wakes someone up. It does not make them a responder.

Open incidents →

Some incidents need the whole room. You can now reach every member of your organisation at once with @everyone, and there are two ways to use it.

Tag @everyone in a note to bring people to an incident. Each person is told as if you had named them individually, so it reaches their mobile, Slack and Microsoft Teams.

Or page @everyone from the incident itself. You hold the button down rather than press it, and everyone gets a critical notification on the app. Spike will not ring a crowd of telephones, so there is no Phone button on this row.

If everyone is more than you need, @team and a team's on-call work the same way.

Open incidents →

An escalation step can now alert everyone in a team. Pick the team and every member of it gets the alert.

Any team in your organisation works here, not only the one the policy belongs to. The step shows the head count, so you can see how many people it wakes up before you save it.

Thanks to those of you who asked for this while moving over from another tool. A small team often has no rota to point at, and a severe incident sometimes wants the whole roster rather than whoever happens to hold the pager.

Set up an escalation policy →

We are now bringing two new home screen widgets. One shows who is on call right now and until when. The other shows your open incidents. Both work on iOS and Android, and you pick what each one tracks.

Inside the app, the incident page has a status timeline in the activity log. You can see who moved an incident from acknowledged to resolved and when they did it. Adding a note is much nicer now.

We also cleaned up dropdowns, animated how incidents move between states, and fixed a few activity log bugs that had been hanging around.

If you want a different app icon, there are new ones to choose from.

Get it on iOS →

Get it on Android →

Notes are being used about ten times more than they were five months ago. You are writing more in them, and writing them with each other, so we rebuilt Notes around that.

The editor is rich text now and it takes Markdown. The writing area is much larger, so a long note stays readable while you write it.

Pin a note

You can pin a note to an incident. Open the incident and the pinned note is right there, so whoever picks it up next starts with the context instead of reading the whole thread for it.

Attachments

Incidents and notes now take attachments, in any file format. Most of what people wanted to add was a screenshot, and videos and documents come up often too, so all of it can go straight on the incident.

Reference other incidents

Reference an incident in a note with @ID and the two are linked. Open an incident and you can see every note that mentions it, which is how you find the last time this happened and what fixed it.

More improvements

• Every note keeps its edit history.
• You can delete a note.
• Mention a teammate and they get a mobile notification, a Slack DM, and a Microsoft Teams DM.

Open incidents →

Status pages now support nested components. Put a component under a parent and report an incident on exactly the part that is affected.

Take our own status page. Alerts is a component. Under it sit Phone alerts, SMS alerts, and Email alerts. When SMS delivery breaks, we mark SMS alerts as down. Phone and Email stay green.

• Any component can be a parent, a child, or both. There is no limit, and you can reorder them.
• When a child's status changes, the parent updates on its own.
• Pick the affected child component when you publish an incident from Spike to your status page.

The status page API now carries the parent and child relationship on components.

Read the API docs →

Set up nested components →

Five smaller changes to the incident dashboard.

Delete incidents

You can now delete an incident from the dashboard. Every deletion is written to the audit log with who deleted it and when.

Deleting is a dashboard action, there is no API endpoint for it.

Edit notes and resolution notes

Notes and resolution notes are now editable, and every edit keeps its history. You can see what a note said before and who changed it.

More improvements

• You can now search for incidents.
• Timestamps in the incident table can switch between absolute and relative time.
• When you tag a teammate on an incident note, they now get a mobile and a Slack notification.

Open incidents →

Today, we are introducing a new logo, a new website, and a whole new identity to Spike.

This new identity is a reflection of our commitment to help teams manage incidents better and make reliability a first-class citizen for every team.

Our new logo brings the spike behind incidents and escalation together. A symbol we believe we will carry forever.

Read the full story in our blog post →

Visit the new Spike →

Connect Spike to Claude, Cursor, or any MCP-compatible tool and manage incidents through natural language.

Ask your AI what's critical. Tell it to acknowledge an outage. Have it build an on-call schedule.

Spike is now wherever you work.

Connect Spike’s MCP →