December 31 · Internet Access restored in Iran by
December 31 is priced at 97¢ on Polymarket. Current book: 93¢ bid, 94¢ ask, 1¢ spread. This outcome ranks #1 of 4 inside Internet Access restored in Iran by...?.
Price history
97¢ current
+45¢Contract brief
On February 28, 2026, a nationwide internet blackout began in Iran amid military engagement with the United States and Israel. This market will resolve to “Yes” if internet access in Iran is restored by the specified date, 11:59 PM UTC. Otherwise, this market will resolve to “No.” For purposes of this market, internet access will be considered restored only if either of the following conditions is satisfied. 1. Internet access will be considered restored if there is a clear, broad, and unambiguous consensus of credible international reporting stating that general internet connectivity has been restored for a majority of people in Iran and across most common applications, and that such connectivity has been sustained for at least 24 consecutive hours. Reporting describing planned restorations, gradual easing, partial reconnection, access limited to specific regions, networks, user groups, or applications, or access restricted to filtered, throttled, or government-controlled networks will not qualify. The reporting must explicitly indicate that normal international internet access has materially resumed. 2. Alternatively, internet access will be considered restored only if both of the following requirements are met. - According to Cloudflare Radar data for Iran, the “Outage” annotation associated with the nationwide internet shutdown must cease to apply to newly published hourly data points for at least 24 consecutive hours in the “Traffic trends” chart for the last 4 weeks. During this same period, the same chart must show a clear increase in either Total bytes or HTTP bytes relative to the outage period, indicating a meaningful restoration of internet traffic. Only the first of the consecutive qualifying hourly data points must occur before the market’s resolution time. If necessary to confirm the full sequence, the market will remain open until all qualifying data points are observed. - In addition, NetBlocks must report that the Iranian national internet outage has been resolved, or must publish a clearly equivalent statement indicating that internet access has been restored for the majority of people and across applications. Reports describing only limited, partial, or localized connectivity; connectivity restricted to filtered or government-controlled networks; traffic increases that NetBlocks characterizes as attempts to generate a false or misleading narrative of restored connectivity, or similar reports, will not qualify, even if the Cloudflare threshold is met. The primary resolution sources for this market will be Cloudflare Radar (https://radar.cloudflare.com/traffic/ir?dateRange=28d) data for Iran and public reporting from NetBlocks (https://netblocks.org/); however, a consensus of credible international reporting meeting the standards described above may also be used.
Outcome
December 31
Rank
#1 of 4
Leader
December 31 94¢
Range
84¢-94¢
Family volume
$1.6M
Identifier
0xf67e9887...9a22
May 28, 2026, 5:38 PM UTC · 30m ago
Implied probability
Bid
93¢
Ask
94¢
Spread
1¢
24h volume
$46K
Family rank
#1 of 4
4 outcomes · Internet Access restored in Iran by...?
Closes
Dec 31, 2026
Family volume
$1.6M
Orderbook snapshot
93 / 94¢
Contract terms
What resolves this market.
YES condition
On February 28, 2026, a nationwide internet blackout began in Iran amid military engagement with the United States and Israel. This market will resolve to “Yes” if internet access in Iran is restored by the specified date, 11:59 PM UTC. Otherwise, this market will resolve to “No.” For purposes of this market, internet access will be considered restored only if either of the following conditions is satisfied. 1. Internet access will be considered restored if there is a clear, broad, and unambiguous consensus of credible international reporting stating that general internet connectivity has been restored for a majority of people in Iran and across most common applications, and that such connectivity has been sustained for at least 24 consecutive hours. Reporting describing planned restorations, gradual easing, partial reconnection, access limited to specific regions, networks, user groups, or applications, or access restricted to filtered, throttled, or government-controlled networks will not qualify. The reporting must explicitly indicate that normal international internet access has materially resumed. 2. Alternatively, internet access will be considered restored only if both of the following requirements are met. - According to Cloudflare Radar data for Iran, the “Outage” annotation associated with the nationwide internet shutdown must cease to apply to newly published hourly data points for at least 24 consecutive hours in the “Traffic trends” chart for the last 4 weeks. During this same period, the same chart must show a clear increase in either Total bytes or HTTP bytes relative to the outage period, indicating a meaningful restoration of internet traffic. Only the first of the consecutive qualifying hourly data points must occur before the market’s resolution time. If necessary to confirm the full sequence, the market will remain open until all qualifying data points are observed. - In addition, NetBlocks must report that the Iranian national internet outage has been resolved, or must publish a clearly equivalent statement indicating that internet access has been restored for the majority of people and across applications. Reports describing only limited, partial, or localized connectivity; connectivity restricted to filtered or government-controlled networks; traffic increases that NetBlocks characterizes as attempts to generate a false or misleading narrative of restored connectivity, or similar reports, will not qualify, even if the Cloudflare threshold is met. The primary resolution sources for this market will be Cloudflare Radar (https://radar.cloudflare.com/traffic/ir?dateRange=28d) data for Iran and public reporting from NetBlocks (https://netblocks.org/); however, a consensus of credible international reporting meeting the standards described above may also be used.
Venue
Polymarket
Closes
Dec 31, 2026
Identifier
0xf67e9887…9a22
Event family
Internet Access restored in Iran by.
The same race as a probability stack: rank, volume, and where this contract sits against the other outcomes.
Total volume
$1.6M
Outcomes
4
Highest price
December 31 94¢
Current share
5%
December 31
polymarket · 0xf67e9887876cf34d3b930c3c74ba444b77783e3a4b8a3fe5304dd3c2b6d09a22
June 30
polymarket · 0xb582fa41361aa4c9faea522e821cf0ec09783594fca42ef6c8aceb14445eafec
September 30
polymarket · 0x8ee699de4568d63c92a334dd9703fbd99ac0f614e5b7ffcc58f09557c86f08cf
May 31
polymarket · 0x5b4be999538e689a0f20055c215e5df11df4da7a6ca7a4bcd8b913ae922d6efb
Indicators
Yield, cliff risk, volatility, and regime.
Regime
neutral
Score
0.5
Full indicator table
Odds pages
Related prediction questions
Related readings
Matched from SimpleFunctions blog, opinions, technical guides, concepts, and learn pages.
Information Finance Has Arrived: A Material Map of Prediction Markets in Q2 2026
Combined Kalshi + Polymarket volume hit $66B in just four months of 2026 — already greater than the entire 2025 industry total. Bernstein projects $1T by 2030. Two venues hold 95% of US share. The distribution layer fragmented across nine retail surfaces. AI agents are 30% of Polymarket wallet activ
Why "Thesis Confidence" Is Not the Same as Market Price
A 70% subjective conviction is not the same number as a 70-cent price. The market price aggregates every active trader weighted by capital. The gap is only edge under specific conditions.
Resolution Risk Premium: Pricing the Rule, Not the Outcome
When the resolution rule is fuzzy, the price is the market's estimate of how the rule will be interpreted, not the outcome's probability. Three case studies and the discount math.
Liquidity Availability Is the Real Edge in Prediction Markets
Implied yield, cliff risk, and overround all describe what to trade. Liquidity Availability Score describes whether the orderbook can absorb the trade. Why LAS is the indicator that decides who actually books P&L.
Liquidity Migration Across Resolution: Where the Money Goes When a Market Closes
When a flagship prediction market closes, the capital that was in it migrates to next-period siblings, adjacent categories, or off the venue entirely. Three migration patterns and the receiving-market opportunity.
Market Making on Polymarket: Why Maker Status Cuts Loss Probability by 36 Points — and Why Spreads Persist Anyway
Akey et al.'s most economically significant finding: moving from pure taker to pure maker status reduces the probability of losing money by ~36 percentage points on Polymarket. Resolution-spec risk is why cross-platform spreads persist at 1.5–4.5% and why even Susquehanna and Jump can't fully arb them.
SimpleFunctions context
Index, screen, query, and monitor.
Prediction Market Index
Market-wide volatility, geo risk, breadth, and activity around this contract.
Market Screener
Filter adjacent contracts by volume, expiry, IY, CRI, venue, and theme.
Event Probability API
Read 97% as a structured event probability object for agents and apps.
Realtime Data API
Prices, orderbooks, movement, heat, and liquidity indicators across venues.
World State API
Compact market-aware context packets for agent sessions and scheduled refresh.
Hedging Workflows
Map a thesis or exposure to candidate event markets and monitoring paths.
How we compute these odds
SimpleFunctions aggregates live prediction-market contracts from Kalshi and Polymarket. Each slug groups contracts that resolve on the same underlying event, identified by venue event_id.
For binary slugs, the headline probability is the liquidity-weighted mid-price across all bound contracts. For multi-outcome slugs (e.g. elections with 3+ candidates), the headline is the leader’s price; we never arithmetically average disjoint outcomes — that would produce a number with no real-world meaning.
Snapshots refresh every 5 minutes during market hours; daily aggregates are computed at 04:00 UTC. The 30-day sparkline is drawn from per-ticker daily means stored in market_indicator_daily; 24h delta and movement events are derived from the same source.