> For the complete documentation index, see [llms.txt](https://about.oa.report/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://about.oa.report/help/oa.report-2026-04-29-incident.md).

# OA.Report 2026-04-29 incident

## Summary

On April 29, 2026, we experienced a loss of OA.Report data. Report figures are now accurate, and normal service has resumed. We've published a [post incident report](https://about.oa.report/help/oa.report-2026-04-29-incident.md) to summarise what happened, what we did about it, and what we’re changing as a result.

## Status updates

**2026-05-06 \~10:00:00 GMT+1**

We have released our fix. Reports are now up to date, and will continue to update. We are continuing to monitor data quality closely and investigate the root cause.

**2026-05-05 \~18:00:00 GMT+1**

We believe we have a fixed the issue that caused the data loss.

**2026-05-04 \~11:47:00 GMT+1**

We have resolved the issue with opening emails and downloading CSVs from actions.

**2026-05-03 \~12:00:00 GMT+1**

We are continuing to investigate the root cause, and monitor for data quality issues.

**2026-05-02 \~12:00:00 GMT+1**

We are continuing to investigate the root cause, and monitor for data quality issues.

**2026-05-01 \~08:47:00 GMT+1**

We have improved our ability to reproduce the issue that caused the data loss. This key step improves our ability to find the issue and develop/test a fix.

**2026-04-30 \~20:00:00 GMT+1**

We are continuing to investigate the root cause, and monitor for data quality issues.

**2026-04-30 \~10:49:00 GMT+1**

We have reproduced the issue that caused the data loss, a key step in the investigation of the root cause. While the exact issue is not clear, the reproduction supports our primary hypothesis.

**2026-04-30 \~09:00:00 GMT+1**

We are continuing to review, and resolve minor issues as we find them.

**2026-04-30 \~20:40:00 GMT+1**

We are continuing to review, and resolve minor issues as we find them.

**2026-04-29 \~14:57:00 GMT+1**

We have released a fix to resolve the minor data accuracy issues.

**2026-04-29 \~12:15:00 GMT+1**

We are aware of minor issues affecting data accuracy, we are investigating a fix.

**2026-04-29 10:33:00 GMT+1**

We have released a fix to restore normal service. We are continuing to investigate the root cause and any further mitigations required. Report figures should now be accurate, but please [alert us](mailto:help@oa.report) if you notice any issues.

**2026-04-29 10:10:00 GMT+1**

We are continuing to investigate and are working on deploying a mitigation.

**2026-04-29 09:50:00 GMT+1**

We are continuing to investigate and are reviewing options for immediate mitigation.

**2026-04-29 09:40:00 GMT+1**

We are continuing to investigate and are deploying changes to avoid further data loss.

**2026-04-29 09:33:00 GMT+1**

We have confirmed a loss of OA.Report data on our production systems. Report figures have major inaccuracies.

**2026-04-29 08:55:00 GMT+1**

We have deployed a website alert to notify users.

**2026-04-29 08:26:00 GMT+1**

We are investigating an issue with potential loss of OA.Report data. Report figures are likely to be have major inaccuracies.

**2026-04-29 \~03:00:00 GMT+1**

Additional automated alerts fire suggesting increased data quality issues.

**2026-04-29 \~01:00:00 GMT+1**

Automated alerts fire suggesting the start of data quality issues.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://about.oa.report/help/oa.report-2026-04-29-incident.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
