The day a -250 favourite collapsed inside six hours
On 1 November 2025, sitting at my desk watching the closing lines move on UFC Vegas 110, I saw something I had not seen on a featherweight prelim in years. Isaac Dulgarian had opened the week at -250 against Yadier del Valle and held that line through Thursday morning. By the time fight night closed in, the line had compressed to -130. Twenty-four hours of sharp action against a featherweight favourite, on a Vegas card with no significant injury news, with the money piling onto both the underdog and the “fight ends in round one finish” prop. That is the line shape that triggers an integrity monitor’s attention.
IC360 — the private integrity-monitoring vendor that most US-licensed sportsbooks subscribe to — flagged the fight before the cage door closed. After del Valle won inside the first round, Caesars Sportsbook and DraftKings voided all wagers on the bout. Dana White went on TMZ Sports and called the situation, in his words, absolute insanity.
The FBI opened an investigation. And the wider UFC betting community got a crash course in something that had been operating quietly in the background for years: real-time, vendor-driven integrity monitoring across the regulated sportsbook ecosystem.
This piece is about how that monitoring actually works. Not the rhetoric around it, not the marketing, but the operational mechanics of how an IC360 alert is generated, what data feeds it, and what changes (and what does not change) the moment a UFC fight gets flagged.
What IC360 actually is, and what it is not
The first thing to be clear about is that IC360 is not a regulator. It is a private company — formerly known as US Integrity, rebranded after a merger with Odds On Compliance in 2024 — that sells integrity-monitoring services to sportsbook operators, leagues, regulators and other clients on a subscription basis. Its leverage comes from the breadth of its data network, not from any statutory power.
What that means in practice: when IC360 flags a fight as suspicious, the company is not “ruling” anything. It is issuing an alert to its client network — sportsbooks, regulators, leagues, and law enforcement contacts — that something in the data deserves immediate human attention. The decision to void wagers, suspend a market, refer a case to law enforcement, or take any other action sits with the relevant operator or governing body, not with IC360. The monitor is the smoke alarm, not the fire brigade.
That distinction matters because casual coverage often frames IC360 alerts as authoritative judgments of fight-fixing. They are not. An alert says, “the betting pattern on this market is statistically anomalous and worth reviewing.” The eventual finding might be deliberate manipulation, inside information, a coincidental cluster of sharp opinion, or a misread by the algorithm. The alert itself is a triage step.
The other thing IC360 is not: a monitor of offshore sportsbooks. Its data network is built on relationships with regulated US books and a smaller number of international regulated operators. Offshore books — Bovada, BetUS, BetOnline, MyBookie, and the dozens of smaller sites that serve California bettors — are not in the data feed. Whatever was happening on the offshore side of the Dulgarian fight is invisible to IC360 in real time. That blind spot is structural, and it matters for a California bettor specifically.
The data sources that feed an alert
An integrity monitor lives or dies on its data network. IC360’s network ingests several distinct feed types and combines them to produce the signal that triggers an alert. Understanding what feeds the system tells you what kinds of manipulation it is positioned to catch — and what kinds it is positioned to miss.
The primary feed is wagering data from subscriber sportsbooks. That covers ticket volume, ticket counts, average stake size, line movement, and the time-stamped pattern of action on each market. For UFC, that means moneyline, method of victory, round totals, and prop markets are all reported into the IC360 system as the action accumulates. The granularity is meaningful. Not just “the line moved from -250 to -130,” but “60% of the volume on the underdog came in two clusters across a four-hour window, with average stake size three standard deviations above the market norm.”
The secondary feeds are odds-aggregation services that monitor line movement across regulated books in real time. These services capture the consensus market position at minute-level granularity. When one book’s line diverges sharply from the consensus and stays divergent, that is a signal. When all subscribed books move in the same direction at the same time on no public news, that is a different signal.
The tertiary feeds include external context — published injury reports, weight-cut news, training-camp disclosures, social media signal scraping for anomalous communications. This is the layer where machine processing meets human judgment. Algorithms surface candidates; analysts decide which candidates merit an alert.
What is conspicuously absent from the feed: the offshore market. Anyone who has watched offshore lines during a flagged event has seen the same dynamic. Lines on Bovada and BetOnline often move earlier and more dramatically than the regulated US lines during a manipulation event, because offshore books accept larger anonymous wagers and adjust their lines on softer triggers. IC360 cannot see those movements directly. It can only see the downstream effect when the regulated books eventually catch up.
What triggers an alert
The threshold for triggering an IC360 alert is not a single number. It is a multi-factor model where several anomalies need to coincide. From what is publicly described and what I have inferred from years of watching flagged fights, the trigger pattern looks roughly like this.
Factor one: line movement that significantly exceeds the typical volatility for the market in question. UFC moneylines have well-characterised volatility profiles. A featherweight prelim moves less than a heavyweight main event, and a -250 favourite collapsing to -130 inside the final 24 hours is well outside the historical distribution of movement on that kind of market.
Factor two: directional concentration of new money. A line move is suspicious when it is driven by a small number of large wagers rather than broad public action. The Dulgarian movement, as it was reported after the fact, fit that profile: most of the volume that drove the line came from a small cluster of ticket entries on the underdog and the round-one finish prop. The implied probability move was carried by ticket count behaviour that was inconsistent with typical fan engagement on a featherweight prelim.
Factor three: cross-market correlation. If the moneyline is moving and the related prop markets — method of victory, round totals — are moving in a way that implies the same outcome, that increases the alert probability. The Dulgarian movement saw simultaneous action on the underdog moneyline, the round-one finish, and the under on rounds. All three pointed at the same predicted outcome. That is a higher-confidence pattern than any one of those moves in isolation.
Factor four: external signal absence. If a line moves sharply because a fighter pulled out of the bout on weigh-in day, that is news. If the line moves sharply with no news, no injury report, no observable cause, the absence of a public explanation pushes the alert probability higher.
The Dulgarian case hit all four factors inside the same window. The line move was an outlier, the volume concentration was sharp, the cross-market action was coherent, and there was no public news to explain any of it. That is the textbook trigger pattern for an integrity monitor.
The Dulgarian fight as a case study in the alert pipeline
What happened on 1 November 2025 is the most concrete public example of an IC360 alert running its full pipeline on a UFC fight. The sequence is worth walking through because it shows the system doing what it is designed to do — for better and for worse.
Pre-fight, the line moved from -250 to -130 across roughly 24 hours of trading. The wagering data from subscriber books surfaced the movement and the concentration. The alert was generated and routed to relevant parties before the fight started. IC360 does not publicly disclose alert timing, but the post-fight statements from Caesars and DraftKings indicate they were operating with awareness of an integrity concern before the bell.
During the fight, del Valle won inside the first round. The outcome matched the late-week prop money perfectly — underdog wins, finish in round one, under on rounds. The settlement decision was where the alert system bit. Caesars and DraftKings voided wagers on the bout rather than paying out. That action is unusual on a US-regulated book. Most flagged fights still settle and pay; voiding is reserved for cases where the integrity concern is severe enough to override standard settlement obligations.
Post-fight, the FBI opened an investigation as part of its broader 2025 work on combat-sports integrity. Dana White went on TMZ and was unambiguous that the UFC would cooperate. The narrative shifted from “anomalous betting pattern” to “ongoing federal investigation” within 72 hours.
What the case study illustrates is the speed of modern integrity response. The system from pattern detection to alert generation to book-level action ran in well under 48 hours, which is fast by historical standards. What it does not illustrate — what no public case study can illustrate — is the rate of false positives in the underlying alert generation, the number of flagged fights that turn out to be artefacts of sharp opinion rather than manipulation, and the proportion of genuinely manipulated fights that the system misses entirely. For the deeper context on the broader UFC integrity environment in which the Dulgarian alert landed, see my analysis of UFC integrity scandals and what they have changed.
The limits of the monitoring perimeter
Every integrity-monitoring system is defined as much by its blind spots as by its coverage. For IC360 in the UFC market, those blind spots are worth naming.
First, the offshore market. As covered above, IC360 sees no direct data from books that serve California bettors. A manipulation event that runs primarily through offshore action would only surface in the IC360 system once it propagated to regulated US books. By that point the underlying transaction is already executed.
Second, prediction markets. Kalshi and Polymarket operate under CFTC rather than state gaming regulators, and they are not subscribers to the standard integrity-monitoring vendor stack. A UFC event contract on Kalshi can move in patterns that an integrity monitor would flag if it were monitoring those markets — but the monitoring is not happening, at least not on the same vendor rails.
Third, the system has a structural bias toward catching crude manipulation rather than sophisticated manipulation. Crude manipulation produces sharp, concentrated, multi-market anomalies — exactly what the algorithm is tuned to detect. Sophisticated manipulation that spreads action across many small tickets, across multiple books, across multiple markets, and through a long time window is much harder to surface above the noise floor. The visible enforcement record suggests the system catches crude. What it misses is, by definition, harder to know.
The honest assessment is that IC360 is a meaningful piece of the UFC integrity infrastructure, materially better than the no-monitoring world of fifteen years ago, and structurally unable to see large portions of the UFC betting market that California bettors actually use. Both things are true.
