Justin & Hailey Bieber split in 2026?
Probability
17¢
1h
+0.0pp
24h
-2.0pp
24h Vol
$45.71
Liquidity
$2.5K
Probability (last 7 days)
-3.0pp 7dWhy did it move?
Heuristic summary, generated from the public market metrics above: probability movement, volume, liquidity, spread, signals, and resolution status.
Timeline — news, trades, signals, price moves
- 0s agoResolveLOW
Market resolves in 6000.7h
- 23:16SignalLOW
Signal · Resolution risk
Expires in 6001h with open resolution ambiguity.
Active signals
Recent Trades
No recent trades visible from the Data API for this market.
Related Markets
6- 78¢+5.0pp
Celtics vs. 76ers
Other · Vol $3.9M
- 60¢+7.0pp
Spurs vs. Trail Blazers
Other · Vol $3.3M
- 37¢+11.0pp
Lakers vs. Rockets
Other · Vol $3.0M
- 0¢-52.4pp
Will Real Madrid CF win on 2026-04-24?
Other · Vol $2.9M
- 100¢0.0pp
U.S. forces seize another oil tanker by April 30?
Other · Vol $2.8M
- 2¢-1.5pp
Strait of Hormuz traffic returns to normal by end of April?
Other · Vol $2.1M
Market Description
This market will resolve to "Yes" if Justin Bieber and/or Hailey Bieber announce their intention to legally separate or divorce between market creation and December 31, 2026, 11:59 PM ET. Otherwise, this market will resolve to "No". An announcement by December 31, 2026, 11:59PM ET of their intention to separate or divorce will be sufficient for a "Yes" resolution, regardless of whether the separation or divorce later actually occurs, or whether the actual separation or divorce occurs outside of the timeframe of this market. The resolution source will be statements from Justin Bieber, Hailey Bieber, and/or their representatives, however a definitive consensus of credible media reporting may be considered.
Resolution & Risk
MEDIUM risk- End date
- Dec 31, 2026
- UMA status
- n/a
- Resolution source
- Not specified in metadata
- Market type
- Binary
- No primary resolution source listed — read the full market rules before acting.
- Wide spread (5.0¢) — liquidity risk on entry/exit.
Alerts
In-app banners work now. Email / Telegram / Discord delivery lands when the backend alert dispatcher ships (needs RESEND_API_KEY + per-user webhook storage).