Is something broken?

Why dynamic features sometimes pause

We run on a tight hosting budget: a fixed number of interactive requests per day, resetting at midnight UTC. Right now that budget is being drained by targeted, automated attacks — bot software flooding several of our endpoints at once, far beyond real visitor traffic. So we've made a choice: the articles and evidence stay online no matter what, and the interactive features may pause while an attack is absorbed.Nothing is ever lost — signatures, comments, and counts are stored safely and return when service resumes.

What to do if something doesn't load

1. If petition signing, counts, comments, or certificates fail, the daily budget is spent — come back tomorrow, service restores automatically at midnight UTC. Your unsent text stays in the form; nothing was recorded half-way.
2. If things still fail the day after tomorrow, email defundminerva@proton.me with what you clicked and what you saw.

What we're doing about it

• Blocking bot traffic before it reaches our systems.
• Caching public counts so real visitors rarely touch the database.
• Publishing every article as a static file, so reading never touches the budget — the evidence stays up mid-attack, by design.