How Can We Help?
How the service works, what it reads, what it holds back and why, and how to use it.
How Event Monitor works
Our methodology: what the record describes, how reports become events, and what we cannot infer.
5 articlesOur sources
Every feed, channel and instrument we read, live, and the rules we read them by.
4 articlesWhat we hold back and why
What we read and did not publish in the last day, and the reasons, in plain words.
3 articlesAlerts and accounts
Signing in, following events and places, and how alerts reach you.
2 articlesLimits
What every account can do today, and the limits on public data.
2 articlesData and API
Feeds, event records as JSON, the research dataset, and how to cite us.
4 articlesCorrections
How a published record changes, merges or is withdrawn, at the same address.
2 articlesPopular articles
- Every source we read, liveLive
Every feed, channel and instrument behind the map, whether it is answering, and when each last reported.
- What we held back in the last day, liveLive
Every candidate event judged in the last day, what was published, and why the rest was held back.
- Our methodology
What the record describes, what we cannot infer, how evidence is reviewed, and the limits of comparison.
- The reasons we hold a report back
Most of what reaches us is talk about events rather than events. These are the reasons, in plain words.
- How alerts work
Your alert is on the moment you save it. We email you a receipt naming it, with nothing to click.
- What every account can do
Today every account has the same levels: one standing alert and five event follows, with alerts right away.