TL;DR: New live feed at /regulatory/tracker. We poll 16 national gambling authorities every day and publish every regulatory action our extractor can parse from their notices — not just the fines. Filter by who it's about (operators, affiliates, payment processors, game suppliers, industry-wide) and what kind of news (fines, warnings, license decisions, AML, player protection, policy, consultations). Around 230 actions in the archive at launch, growing daily. Wagie, the AI auditor at /wagerx-ai-agent, pulls the most recent 25 enforcement actions into context on every relevant question, so when you ask "is this casino in trouble?" the answer is grounded in what the regulator actually said.
We are running this site for people about to deposit real money at a casino. That comes with a duty most affiliate sites quietly skip: telling you what is going on behind the scenes. When a regulator slaps a license holder with a six-figure fine, when an authority opens a consultation on bonus advertising, when a payment processor gets warned for handling unlicensed flows — those events change the picture. If your only source is the casino itself, you will never hear about them.
So we built the opposite of that. Today we are turning on a new section of the WagerX Regulatory Hub: a live, filterable news tracker that mirrors what 16 national gambling authorities publish, the day they publish it. Live now at /regulatory/tracker.
Why we built this — the transparency argument
The crypto-gambling internet is full of "top 10 casinos 2026" pages that update their rankings the day a casino starts paying better commission and never once mention that the same casino was warned by a regulator three weeks earlier. That gap is the whole reason this tool exists.
Our position is simple: if our users are going to trust our rankings, they should be able to see the same regulator news we see. Not a curated highlight reel — the full feed. If the UK Gambling Commission published it, the Malta Gaming Authority published it, Spillemyndigheden in Denmark published it, Spelinspektionen in Sweden published it — it is on our tracker. Fines, warnings, license grants, license revocations, AML actions, player-protection updates, policy notices, public consultations. The boring ones too. Because picking only the dramatic ones is itself a form of editorial spin, and the goal here is zero spin.
This is also why the page is not behind a paywall, not behind an email gate, not gated to logged-in users. Anyone can read it, anyone can link to a specific update, the JSON-LD on every action is set up so AI assistants can cite individual entries. The data is too important to hide.
What it tracks right now
16 authorities configured at launch, across Europe, the UK, Ireland, Australia and Canada:
- UK & Ireland: UK Gambling Commission (UKGC), Gibraltar Regulatory Authority (GRA), Gambling Regulatory Authority of Ireland (GRAI)
- Nordics: Spillemyndigheden (Denmark), Spelinspektionen (Sweden), Lotteritilsynet (Norway), Poliisihallitus — Arpajaishallinto (Finland)
- Continental EU: Malta Gaming Authority (MGA), Kansspelautoriteit (Netherlands), Autorité Nationale des Jeux (France), Agenzia delle Dogane e dei Monopoli (Italy), Dirección General de Ordenación del Juego (Spain), Gemeinsame Glücksspielbehörde der Länder (Germany), Eidgenössische Spielbankenkommission (Switzerland)
- Outside Europe: Australian Communications and Media Authority (ACMA), Alcohol and Gaming Commission of Ontario (AGCO)
Honesty about coverage on launch day. Seven of the sixteen authorities are actively producing extracted actions in the database right now — UKGC, Spillemyndigheden, GRAI, Lotteritilsynet, Spelinspektionen, MGA, and GGL. The other nine are configured but not yet contributing rows: ACMA and Finland's Poliisihallitus block our infrastructure at the network edge (we are working on a routing fix); the Swiss ESBK and Saudi-style page layouts on some authorities return parse errors; AGCO, ANJ, ADM, DGOJ, KSA and Gibraltar GRA are polled successfully but our extractor has not yet learned their notice format, so items are queued in the backlog without being published. None of these gaps are hidden — the public source list on /regulatory reflects what is actually flowing through.
Filter by who it's about, and by what kind of news
The tracker has two independent filter rows so you can narrow the feed to exactly what you care about:
- Who it's about — All · Operators · Affiliates · Payment processors · Game suppliers · Industry-wide
- What kind of news — All · Fines & penalties · Suspensions · Revocations · Warnings · AML & integrity · Player protection · License decisions · Policy & rules · Consultations · Other
Both axes combine in the URL. /regulatory/tracker?t=operator&cat=fine gives you "every fine, against an operator, across every authority we track". Each tab carries its live count, so you can see at a glance which categories are most active. As of launch the archive splits into roughly 53 policy notices, 50 fines, 31 warnings, 22 consultations, 14 revocations, 9 license decisions, 6 AML actions, 3 suspensions, 2 player-protection updates and 39 "other" — the live counts on the tabs are read directly from the database, so they move as new actions land.
The taxonomy is normalized in the database, so when an authority writes "Financial penalty notice" and another writes "Sanction — pecuniary" and a third writes "Civil monetary penalty", all three land in Fines & penalties and you can compare them like-for-like. This was the boring engineering work that took the most time, and the reason filtering actually works.
How Wagie uses it
This is the part we are most excited about. Wagie, the conversational forensic auditor at /wagerx-ai-agent, now has the last 90 days of regulator news wired directly into context on every relevant answer. When you ask Wagie about a specific operator, a specific bonus, a specific jurisdiction — the most recent 25 enforcement actions are in the same block of context the model reads before it writes its answer.
That means when you ask "is Casino X in good standing right now?", Wagie is not making a vibe call from training data that is six months old. It is looking at the same updated row in our database that you see on the tracker page, with the authority name, the date, the target, the type, the amount, and the source URL. If a regulator hammered an operator on Monday, Wagie knows on Tuesday.
The discipline is the same as everywhere else on the site: Wagie cites the authority URL when it makes a regulatory claim, and the chat renderer adds rel="nofollow noopener" to every external link automatically. No claim without a source.
The archive — around 230 actions and counting
Launch day numbers, so you know what you are getting:
- UK Gambling Commission — 108 actions
- Spillemyndigheden (Denmark) — 56 actions
- Gambling Regulatory Authority of Ireland — 22 actions
- Lotteritilsynet (Norway) — 15 actions
- Spelinspektionen (Sweden) — 14 actions
- Malta Gaming Authority — 9 actions
- Gemeinsame Glücksspielbehörde der Länder (Germany) — 5 actions
That is the volume that exists in our database at this moment. New items are polled every 24 hours. Each entry has its own detail page with the authority's original notice URL, the date the action was issued, the target it was issued against, the type, the monetary amount when applicable, and a short plain-English summary.
What this tracker deliberately does not do
- It does not editorialise. Summaries describe what the authority said. We do not add opinions about whether the operator deserved it, whether the fine was too small, or whether the authority is overreaching. Those takes belong in an opinion column, not a citation reference.
- It does not predict outcomes. "This means the operator is finished" is not a sentence on the tracker. We summarise, we link, we date — and we move on.
- It does not filter by partner status. If a casino we have an affiliate relationship with gets fined, that action appears on the tracker the same day it appears anywhere else, with the same prominence as any other operator's. There is no quiet exclude-list. We would rather lose a partner than be the kind of site that hides a fine.
- It does not replace legal advice. The disclaimer at the bottom of every regulatory page repeats this in plain language.
What's next
- Coverage expansion — fixing the ACMA and Finland egress block, teaching the extractor to parse GGL and AGCO notice formats, fixing the parse errors on KSA and ESBK. We want all 16 authorities live in the next six weeks.
- Bilingual rollout — DE first, given our existing German coverage. The hub itself is already EN+DE so this is the obvious next step.
- RSS / JSON feed per category so compliance teams and journalists can subscribe to "every UK fine" or "every consultation closing this month" directly into Slack or a feed reader.
- Per-operator history — once we have six months of archive, every casino review on the site will carry a "regulatory history" panel pulled from this database. The data is already accumulating.
Why this matters to us
We are a crypto-casino review site. We make money when readers click an affiliate link and sign up. That business model has a known failure mode: it pays you to talk casinos up and stay quiet when they get in trouble. Most affiliate sites accept that trade-off. We do not.
The regulator news tracker is the practical answer to "how do you stay honest while taking affiliate revenue". The honest answer is: you build the tool that makes hiding things impossible, you point it at yourself first, and you let the reader see the same data you see. If we ever rank a casino at the top of a list while the same casino is sitting on a fresh UK Gambling Commission fine, you will see it on this tracker, on the same day, on the same site. That accountability is the entire point.
Live now at /regulatory/tracker. Bug reports, missing authority requests and source corrections go to /contact-us.
Shipped 20 May 2026 by the WagerX product team. 16 authorities configured (7 actively contributing rows at launch), around 230 actions in the archive, daily polling, normalized taxonomy across 10 categories, Wagie reads the most recent enforcement actions into every relevant answer. Not legal advice — see disclaimer on each regulatory page.