System status
Incident

Activity

Data recovery complete

We can confirm that all Crash Reporting data submitted on 14 June between 07:54 and 19:10 UTC that was previously missing from the Raygun application console is now fully accessible.

Our primary data storage system was not affected by this incident thus all Crash Reporting data that was accepted by Raygun had been successfully stored. This allowed us to replay the raw crash reports back through our ingestion pipeline as a recovery effort. We have now completed this recovery, and are confident missing crash reports which occurred during the window are restored.

Data recovery update

We have been running the recovering process for Crash Reporting data submitted between 14 June between 07:54 and 19:10 UTC and continue to run the this process. We expect to have all Crash Reporting data for the outage period restored in the next 12 hours.

Data recovery update

An update on our incident earlier today. No data was lost during this incident, however, data received in the incident time period is currently not visible in the Raygun application.
We’re currently transferring data from storage to our application and we’ll keep this page updated with our progress.

Ingestion Rates Recovering

We believe we have identified and fixed the root cause of this outage. We're now seeing ingestion rates recover. We will continue to investigate and post a full update once we know more.

Crash Reporting Ingestion Outage

We're investigating an issue with ingestion of crash reports into our system.