Bans as they happen.
The same feed our Discord carries, without the names. Every one below was issued by a detection rather than a person, and either sat through the fifteen-minute hold we put on detection bans in case they were wrong, or was reviewed by our staff first.
Most recent
Showing 40 bans
Why there are no names
A ban is a claim about a person, and this page is public. A row carries the detection that fired, the country the server sits in, the time, and the capture the anticheat took at the moment it fired. Nothing that names anyone: no player name, no identifiers, no hardware ids, no server name. Manual bans never appear here at all, so every reason on this page was written by a detection rather than typed by an admin. A ban that is later reversed drops off the feed within seconds.
The capture is a frame of the cheater's own screen, so anything that was on their screen is in it. We publish it because a ban with no evidence is just an assertion, and the same captures already go out in our Discord. If one of these is yours and you want it taken down, ask us and it goes.
Questions about this feed
- Is this a real feed of live FiveM anticheat bans?
- Yes. Every row is a real ban or kick issued by a Raven Anticheat detection on a live FiveM server, published automatically as it happens. Nothing on this page is written by a person, and no row is added by hand. Over the last 30 days Raven published 1,421 bans on this page, from 53 distinct detection types, on servers in 10 countries. The counters above the feed are read from the same database the rows are, so they move together.
- How can I verify a FiveM anticheat actually catches cheaters?
- Ask to see the bans. A feature list costs nothing to write and a screenshot is trivial to fake, but a feed that keeps moving, that anyone can open at any hour, and that would be visibly empty if the product did not work is hard to fabricate. This page is Raven Anticheat publishing exactly that: the detection name in the anticheat's own words, the country of the server, the time, and the capture taken at the moment the detection fired.
- Why does a ban wait fifteen minutes before it appears?
- Because a published ban is a public claim about a person and false positives happen. A detection ban is held for fifteen minutes first, and if Raven Mind reverses it inside that window, or a staff member unbans, it never appears here at all. The one exception goes the other way: a ban carrying a network-wide global ban skips the wait, because a Raven Network entry has already been reviewed by staff.
- What happens to a ban that turns out to be wrong?
- It disappears from the page. If a ban is reversed after publication, whether Raven Mind cleared it on its own or an admin unbanned from the dashboard, the row stops being served within seconds, and it goes at every scroll depth rather than only from the top of the list. A Discord message cannot be taken back once posted, so on this specific point the page is more honest than the channel it mirrors.
- Does the live bans page identify the banned players?
- No. The player name, their identifiers, their hardware ids, the server name and the server IP are never selected from the database, so they cannot reach the page through any payload or later refactor. A row carries only the detection reason, the country the server sits in, the time it was published, and the capture. Manual bans are excluded entirely, which is why every reason here was written by a detection rather than typed by an admin about a person.
- What kinds of cheats does Raven Anticheat detect?
- The reasons in the feed are the detections themselves, so the page doubles as a live list of what Raven catches: aimbot, triggerbot and silent aim, ESP and wallhacks, godmode, noclip, speed and teleport, Lua executors and NUI injection, unauthorised weapons and spawned entities, plus event-validation and anti-tamper failures. 53 distinct detection types fired in the last 30 days. Detection updates ship daily.
- Can I use this data?
- The same snapshot the page renders is served as JSON at https://www.ravenac.net/api/live-bans, with no authentication, because it publishes exactly what the page already shows to anyone who opens it. It is a rolling window rather than a full archive: the feed serves the most recent rows and says so when a reader reaches the end.