We encountered an incident involving incorrect grouping of different incidents. Our postmortem has some extensive details for all our users. At Spike, we are committed to alerting you when things go awry so it’s only fair we keep it absolutely transparent regarding any incidents.

Please find the full postmortem here 👉 https://spike.sh/blog/postmortem-incident-grouping/

Got all the migrations finished and cleaned some previous data. More importantly, the new flow for incidents and their ids storage is up and running.

All grouping is now as intended before. We are monitoring the grouping and id service for incidents.

Thanks.

Postmortem to come soon.

🚧 We have identified the issue and working on an immediate fix for this. These are the 2 steps we will be doing

1. Installing a new flow for incident and their ids stored
2. Migrations on some older incidents to move them to new data storage - Incident History

We will keep you posted 👍

Different incidents are getting grouping together. This has led to incorrect repeated incident metrics for some incidents. We are currently investigating this incident.