About

People kept texting me, "Is this a hack?" Often I didn't know.

So I stopped answering off the cuff and built something that does the work, and shows it.

Why I built this

When something big breaks, people reach out to me and ask what is going on, and whether it is a hack. I get that question a lot, especially when an outage feels like it might be one. I would do my best to answer, but I am usually not sitting there watching the news, so a lot of the time I did not know.

When the FAA ground stop started on November 13, 2026, I set a group of AI agents to work on it. At one point there were fifteen of them, each chasing a different thread. I got pulled in, both by what was actually happening and by how many of the claims going around turned out to be myths.

I kept following the story for days. While I did, more incidents arrived that felt similar, and the texts came with them.

Instead of answering with what I thought might be right, why not put real work behind the answer? That is this site.

Who is behind it

One person, and a desk of AI agents.

  • The person

    Justin

    My day job is running SecureCoders, a security company where deep research is a large part of the work. We built Parallect to help with it: it sends one question to several research engines and shows where their answers agree and where they do not.

    On this site I make one call: the final verdict that closes a case. The agents do the rest.

  • The agents

    Research, verification, writing, editing

    AI models that gather and organize everything on these pages. Each has one job and a list of things it may not do. They read public sources, sort the claims, write the page and keep it up to date.

    How the desk works

Why agents

A breaking incident produces a flood of statements, reports and posts within hours. Agents can read all of it on a schedule, come back and read it again, and keep a log of everything they checked, including the checks that found nothing.

The one call that should not be automatic is the last one. Before a case is closed as a hack, or as not a hack, the evidence comes to me and I have to be convinced.

What we hold to

Public sources only
Nothing behind a login, nothing leaked, nothing we had to ask for.
Attribute, don't assert
We say who said it: "the company said", "according to" the outlet.
One set of labels, in full words
Six labels, the same on every page and in every data file.
Corrections in the open
A dated note says what was wrong. Nothing is edited quietly.
No personal information
No private names, handles or contact details, on the page or in our files.
Calm language
We lead with the answer, not the threat, and we do not present a worst case as the likely case.

What this is not

Made for entertainment using AI. Not endorsed by anyone named here.

It is not endorsed by any company, agency or person it mentions. It is not a source of security, legal, financial or safety advice. If you need to act on an incident, go to the official source. We link to it.

Get in touch

Found an error, a source we missed, or an incident we should be tracking? Pick whichever is easiest.