Status
These checks run against the live service at most once every 30 seconds, and the time below is when they last ran, not when you opened the page. So this can be up to 30 seconds behind.
Services operational. 1 published dataset is behind its official source, listed below.
CHECKED 2026-10-29 00:05:43 UTC
Components
- Parliamentary record databaseOperational
- Search and retrievalOperational
Search and retrieval degrades independently of the record itself. Emily keeps answering when it does; she answers from less.
Published data freshness
Being up and being current are different things. Each dataset below is graded against the rhythm its own official source publishes on, from the newest record we hold and the last time we added a row. Nothing here is asserted by hand.
- Hansard debate contributionsCurrent: newest record 1 day old, last added 1 day ago.Current
- Political donationsCurrent: newest record 122 days old, last added 16 days ago.Current
- Government contract awardsCurrent: newest record 2 days old, last added 1 day ago.Current
- Ministerial meetingsCurrent: newest record 121 days old, last added 34 days ago.Current
- Ministerial gifts and hospitalityCurrent: newest record 60 days old, last added 20 days ago.Current
- Consultant-lobbyist registrationsCurrent: last added 3 days ago.Current
- ACOBA appointment advice (the revolving door)Behind its source: last added 54 days ago.Behind source
- MPs' registered financial interestsCurrent: newest record 2 days old, last added 1 day ago.Current
- Select-committee oral evidence sessionsCurrent: newest record 3 days old, last added 1 day ago.Current
- Public petitionsCurrent: last added 1 day ago.Current
- Bills before Parliament (all sessions tracked)Current: newest record 2 days old.Current
- Sitting MPs and peers profiledCurrent: last added 13 days ago.Current
- Written parliamentary questionsCurrent: newest record 6 days old, last added 1 day ago.Current
The counts these datasets feed are on the statistics page, which carries the same verdicts.
Recovery objectives
These are the targets we hold ourselves to, and the mechanism behind each one. Where the mechanism is weaker than the target, it says so rather than rounding up.
| Objective | Target | Mechanism |
|---|---|---|
| Recovery point objective (RPO) | 24 hours | Supabase takes a daily automated backup of the production database, retained for 7 days. Point-in-time recovery is available on the platform but is not enabled on this project, so a restore returns the state of the most recent nightly backup. Reducing this target means enabling PITR, not editing this line. |
| Recovery time objective (RTO) | 4 hours | Restore of the most recent backup into the production project, followed by the documented smoke checks. Target, not yet rehearsed. It is derived from the restore procedure rather than from a timed run, and it stays a target until a drill has been carried out and recorded. |
| Application recovery | 15 minutes | The application layer is stateless on Vercel. A bad deploy is rolled back by promoting the previous production deployment; nothing has to be restored to do it. |
| Parliamentary corpus rebuild | 7 days | The public record is re-derivable from source: every sync script can replay from the upstream APIs and the RAG index can be rebuilt from the synced tables. Slow, and it costs embedding spend, but it is not lost. Customer data (conversations, CRM, briefings, documents) is NOT re-derivable and depends entirely on the backup above. |
Customer data is stored in a single Supabase project in AWS eu-west-2 (London). There is no second region and no read replica, so a full regional outage at that provider is an outage here too. We would rather write that down than let a buyer discover it.
More on how the service is built and run: Security · Sub-processors · Data processing agreement.
Something wrong that this page says is fine?
The checks above cover the database and the retrieval layer. They do not cover every way the product can disappoint you, and a green page is not a contradiction of what you are seeing. Tell us: support@emilypolitics.com.