Monitoring

Forecasts — call what happens next

Free to play: set your chance, see the crowd, get scored when the source decides. Leaderboard · Your calls · Propose a question

Earthquakes

6 open

Will a magnitude 5.5+ earthquake strike the California region between 1–30 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Earthquakes of magnitude 5.5 or more with the epicentre in the California box
Window
2026-11-01 00:00 → 2026-12-01 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
USGS earthquake catalog
Read order
USGS event API (earthquake.usgs.gov/fdsnws) → USGS earthquake map (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if the USGS earthquake catalog lists an event of magnitude 5.5 or more with its epicentre inside 32° to 42° latitude, -125° to -114° longitude (the California box), from 2026-11-01T00:00:00.000Z up to (not including) 2026-12-01T00:00:00.000Z.

Resolver: MonitoringRoom, automatic from USGS earthquake catalog

Calls close 29 Nov, 00:00 UTC · Resolves from earthquake.usgs.gov

Will a magnitude 6.0+ earthquake strike the Japan region between 23–29 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Earthquakes of magnitude 6.0 or more with the epicentre in the Japan box
Window
2026-11-23 00:00 → 2026-11-30 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
USGS earthquake catalog
Read order
USGS event API (earthquake.usgs.gov/fdsnws) → USGS earthquake map (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if the USGS earthquake catalog lists an event of magnitude 6.0 or more with its epicentre inside 24° to 46° latitude, 122° to 154° longitude (the Japan box), from 2026-11-23T00:00:00.000Z up to (not including) 2026-11-30T00:00:00.000Z.

Resolver: MonitoringRoom, automatic from USGS earthquake catalog

Calls close 29 Nov, 00:00 UTC · Resolves from earthquake.usgs.gov

Will a magnitude 7.0+ earthquake strike anywhere in the world between 1–30 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Earthquakes of magnitude 7.0 or more anywhere in the world
Window
2026-11-01 00:00 → 2026-12-01 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
USGS earthquake catalog
Read order
USGS event API (earthquake.usgs.gov/fdsnws) → USGS earthquake map (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if the USGS earthquake catalog lists an event of magnitude 7.0 or more anywhere in the world, from 2026-11-01T00:00:00.000Z up to (not including) 2026-12-01T00:00:00.000Z.

Resolver: MonitoringRoom, automatic from USGS earthquake catalog

Calls close 29 Nov, 00:00 UTC · Resolves from earthquake.usgs.gov

Will a magnitude 5.5+ earthquake strike the California region between 1–31 December 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Earthquakes of magnitude 5.5 or more with the epicentre in the California box
Window
2026-12-01 00:00 → 2027-01-01 00:00 UTC (end not included); calls close 2026-12-30 00:00 UTC
Source
USGS earthquake catalog
Read order
USGS event API (earthquake.usgs.gov/fdsnws) → USGS earthquake map (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if the USGS earthquake catalog lists an event of magnitude 5.5 or more with its epicentre inside 32° to 42° latitude, -125° to -114° longitude (the California box), from 2026-12-01T00:00:00.000Z up to (not including) 2027-01-01T00:00:00.000Z.

Resolver: MonitoringRoom, automatic from USGS earthquake catalog

Calls close 30 Dec, 00:00 UTC · Resolves from earthquake.usgs.gov

Will a magnitude 6.0+ earthquake strike the Indonesia region between 1–31 December 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Earthquakes of magnitude 6.0 or more with the epicentre in the Indonesia box
Window
2026-12-01 00:00 → 2027-01-01 00:00 UTC (end not included); calls close 2026-12-30 00:00 UTC
Source
USGS earthquake catalog
Read order
USGS event API (earthquake.usgs.gov/fdsnws) → USGS earthquake map (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if the USGS earthquake catalog lists an event of magnitude 6.0 or more with its epicentre inside -11° to 6° latitude, 95° to 141° longitude (the Indonesia box), from 2026-12-01T00:00:00.000Z up to (not including) 2027-01-01T00:00:00.000Z.

Resolver: MonitoringRoom, automatic from USGS earthquake catalog

Calls close 30 Dec, 00:00 UTC · Resolves from earthquake.usgs.gov

Will a magnitude 7.0+ earthquake strike anywhere in the world between 1–31 December 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Earthquakes of magnitude 7.0 or more anywhere in the world
Window
2026-12-01 00:00 → 2027-01-01 00:00 UTC (end not included); calls close 2026-12-30 00:00 UTC
Source
USGS earthquake catalog
Read order
USGS event API (earthquake.usgs.gov/fdsnws) → USGS earthquake map (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if the USGS earthquake catalog lists an event of magnitude 7.0 or more anywhere in the world, from 2026-12-01T00:00:00.000Z up to (not including) 2027-01-01T00:00:00.000Z.

Resolver: MonitoringRoom, automatic from USGS earthquake catalog

Calls close 30 Dec, 00:00 UTC · Resolves from earthquake.usgs.gov

Crypto hacks

3 open

Will a crypto hack of $10M or more happen between 23–29 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Crypto hacks of US$10,000,000 or more, by the incident's listed date (UTC)
Window
2026-11-23 00:00 → 2026-11-30 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
DefiLlama hacks dataset
Read order
DefiLlama hacks dataset (live) → MonitoringRoom's stored copy of the dataset — a YES only; a NO waits for the live feed
Void
If the source stops publishing before close, the question is void and unscored.

YES if DefiLlama's hacks dataset lists an incident dated 23–29 November 2026 (UTC) with an amount of US$10,000,000 or more. Late listings count until 7 days after the window ends.

Resolver: MonitoringRoom, automatic from DefiLlama hacks dataset

Calls close 29 Nov, 00:00 UTC · Resolves from defillama.com

Will a crypto hack of $50M or more happen between 1–30 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Crypto hacks of US$50,000,000 or more, by the incident's listed date (UTC)
Window
2026-11-01 00:00 → 2026-12-01 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
DefiLlama hacks dataset
Read order
DefiLlama hacks dataset (live) → MonitoringRoom's stored copy of the dataset — a YES only; a NO waits for the live feed
Void
If the source stops publishing before close, the question is void and unscored.

YES if DefiLlama's hacks dataset lists an incident dated 1–30 November 2026 (UTC) with an amount of US$50,000,000 or more. Late listings count until 7 days after the window ends.

Resolver: MonitoringRoom, automatic from DefiLlama hacks dataset

Calls close 29 Nov, 00:00 UTC · Resolves from defillama.com

Will a crypto hack of $50M or more happen between 1–31 December 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Crypto hacks of US$50,000,000 or more, by the incident's listed date (UTC)
Window
2026-12-01 00:00 → 2027-01-01 00:00 UTC (end not included); calls close 2026-12-30 00:00 UTC
Source
DefiLlama hacks dataset
Read order
DefiLlama hacks dataset (live) → MonitoringRoom's stored copy of the dataset — a YES only; a NO waits for the live feed
Void
If the source stops publishing before close, the question is void and unscored.

YES if DefiLlama's hacks dataset lists an incident dated 1–31 December 2026 (UTC) with an amount of US$50,000,000 or more. Late listings count until 7 days after the window ends.

Resolver: MonitoringRoom, automatic from DefiLlama hacks dataset

Calls close 30 Dec, 00:00 UTC · Resolves from defillama.com

Outages

5 open

Will Coinbase report a major or critical incident between 1–30 November 2026?

25%— 0 pts 24 hcrowd · 1 calleras of 17:36 UTC
Rules
Measured
Coinbase incidents of major or critical impact, by creation time
Window
2026-11-01 00:00 → 2026-12-01 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
Coinbase status page (status.coinbase.com)
Read order
status.coinbase.com/api/v2/incidents.json, read hourly → status.coinbase.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if status.coinbase.com lists an incident created from 2026-11-01T00:00:00.000Z up to (not including) 2026-12-01T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from Coinbase status page (status.coinbase.com)

Calls close 29 Nov, 00:00 UTC · Resolves from status.coinbase.com

Will GitHub report a major or critical incident between 23–29 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
GitHub incidents of major or critical impact, by creation time
Window
2026-11-23 00:00 → 2026-11-30 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
GitHub status page (www.githubstatus.com)
Read order
www.githubstatus.com/api/v2/incidents.json, read hourly → www.githubstatus.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if www.githubstatus.com lists an incident created from 2026-11-23T00:00:00.000Z up to (not including) 2026-11-30T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from GitHub status page (www.githubstatus.com)

Calls close 29 Nov, 00:00 UTC · Resolves from githubstatus.com

Will Kraken report a major or critical incident between 1–30 November 2026?

5%— 0 pts 24 hcrowd · 1 calleras of 17:36 UTC
Rules
Measured
Kraken incidents of major or critical impact, by creation time
Window
2026-11-01 00:00 → 2026-12-01 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
Kraken status page (status.kraken.com)
Read order
status.kraken.com/api/v2/incidents.json, read hourly → status.kraken.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if status.kraken.com lists an incident created from 2026-11-01T00:00:00.000Z up to (not including) 2026-12-01T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from Kraken status page (status.kraken.com)

Calls close 29 Nov, 00:00 UTC · Resolves from status.kraken.com

Will Coinbase report a major or critical incident between 1–31 December 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Coinbase incidents of major or critical impact, by creation time
Window
2026-12-01 00:00 → 2027-01-01 00:00 UTC (end not included); calls close 2026-12-30 00:00 UTC
Source
Coinbase status page (status.coinbase.com)
Read order
status.coinbase.com/api/v2/incidents.json, read hourly → status.coinbase.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if status.coinbase.com lists an incident created from 2026-12-01T00:00:00.000Z up to (not including) 2027-01-01T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from Coinbase status page (status.coinbase.com)

Calls close 30 Dec, 00:00 UTC · Resolves from status.coinbase.com

Will Kraken report a major or critical incident between 1–31 December 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Kraken incidents of major or critical impact, by creation time
Window
2026-12-01 00:00 → 2027-01-01 00:00 UTC (end not included); calls close 2026-12-30 00:00 UTC
Source
Kraken status page (status.kraken.com)
Read order
status.kraken.com/api/v2/incidents.json, read hourly → status.kraken.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if status.kraken.com lists an incident created from 2026-12-01T00:00:00.000Z up to (not including) 2027-01-01T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from Kraken status page (status.kraken.com)

Calls close 30 Dec, 00:00 UTC · Resolves from status.kraken.com

Exploited vulnerabilities

1 open

Will CISA add 7 or more vulnerabilities to its Known Exploited Vulnerabilities catalog between 23–29 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Vulnerabilities added to CISA's Known Exploited Vulnerabilities catalog, counted by each entry's dateAdded (UTC date): 7 or more
Window
2026-11-23 00:00 → 2026-11-30 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
CISA Known Exploited Vulnerabilities catalog
Read order
the catalog's JSON feed (cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json), read hourly → the catalog page (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if CISA's Known Exploited Vulnerabilities catalog lists 7 or more entries whose dateAdded is 23–29 November 2026 (UTC dates). Entries dated in the window count until 1 day after it ends.

Resolver: MonitoringRoom, automatic from CISA Known Exploited Vulnerabilities catalog

Calls close 29 Nov, 00:00 UTC · Resolves from cisa.gov

Space weather

2 open

Will NOAA's planetary K-index reach 7− or higher (a G3, strong geomagnetic storm) between 18–30 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
NOAA's planetary K-index (3-hour values) at 7− (6.67) or higher in any 3-hour period that starts in the window
Window
2026-11-18 02:00 → 2026-12-01 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
NOAA Space Weather Prediction Center, planetary K-index
Read order
services.swpc.noaa.gov/products/noaa-planetary-k-index.json, read hourly → swpc.noaa.gov planetary K-index page (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if NOAA SWPC's planetary K-index lists a value of 6.67 (Kp 7−) or more for a 3-hour period starting from 2026-11-18T02:00:27.103Z up to (not including) 2026-12-01T00:00:00.000Z. MonitoringRoom reads the feed hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from NOAA Space Weather Prediction Center, planetary K-index

Calls close 29 Nov, 00:00 UTC · Resolves from swpc.noaa.gov

Will NOAA's planetary K-index reach 7− or higher (a G3, strong geomagnetic storm) between 1–31 December 2026?

No calls yetas of 17:36 UTC
Rules
Measured
NOAA's planetary K-index (3-hour values) at 7− (6.67) or higher in any 3-hour period that starts in the window
Window
2026-12-01 00:00 → 2027-01-01 00:00 UTC (end not included); calls close 2026-12-30 00:00 UTC
Source
NOAA Space Weather Prediction Center, planetary K-index
Read order
services.swpc.noaa.gov/products/noaa-planetary-k-index.json, read hourly → swpc.noaa.gov planetary K-index page (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if NOAA SWPC's planetary K-index lists a value of 6.67 (Kp 7−) or more for a 3-hour period starting from 2026-12-01T00:00:00.000Z up to (not including) 2027-01-01T00:00:00.000Z. MonitoringRoom reads the feed hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from NOAA Space Weather Prediction Center, planetary K-index

Calls close 30 Dec, 00:00 UTC · Resolves from swpc.noaa.gov

Wildfires

2 open

Will NASA's EONET list a new wildfire of 50,000 hectares or more between 18–30 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
New wildfire events in NASA EONET (first reported in the window) with a burned area of 50,000 hectares or more on a reading dated in the window (acres converted at 1 acre = 0.4047 ha)
Window
2026-11-18 02:00 → 2026-12-01 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
NASA EONET (Earth Observatory Natural Event Tracker), wildfires category
Read order
eonet.gsfc.nasa.gov/api/v3/events?category=wildfires, read hourly → the event's own source link in EONET (GDACS, IRWIN — staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if NASA EONET lists a wildfire event first reported from 2026-11-18T02:00:27.103Z up to (not including) 2026-12-01T00:00:00.000Z with a magnitude of 50,000 hectares or more (acres converted) on a reading dated in that window. Readings dated in the window count until 3 days after it ends.

Resolver: MonitoringRoom, automatic from NASA EONET (Earth Observatory Natural Event Tracker), wildfires category

Calls close 29 Nov, 00:00 UTC · Resolves from eonet.gsfc.nasa.gov

Will NASA's EONET list a new wildfire of 50,000 hectares or more between 1–31 December 2026?

No calls yetas of 17:36 UTC
Rules
Measured
New wildfire events in NASA EONET (first reported in the window) with a burned area of 50,000 hectares or more on a reading dated in the window (acres converted at 1 acre = 0.4047 ha)
Window
2026-12-01 00:00 → 2027-01-01 00:00 UTC (end not included); calls close 2026-12-30 00:00 UTC
Source
NASA EONET (Earth Observatory Natural Event Tracker), wildfires category
Read order
eonet.gsfc.nasa.gov/api/v3/events?category=wildfires, read hourly → the event's own source link in EONET (GDACS, IRWIN — staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if NASA EONET lists a wildfire event first reported from 2026-12-01T00:00:00.000Z up to (not including) 2027-01-01T00:00:00.000Z with a magnitude of 50,000 hectares or more (acres converted) on a reading dated in that window. Readings dated in the window count until 3 days after it ends.

Resolver: MonitoringRoom, automatic from NASA EONET (Earth Observatory Natural Event Tracker), wildfires category

Calls close 30 Dec, 00:00 UTC · Resolves from eonet.gsfc.nasa.gov

Closed and resolved

Earthquakes

Will a magnitude 6.0+ earthquake strike the Japan region between 16–22 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
Earthquakes of magnitude 6.0 or more with the epicentre in the Japan box
Window
2026-11-16 00:00 → 2026-11-23 00:00 UTC (end not included); calls close 2026-11-22 00:00 UTC
Source
USGS earthquake catalog
Read order
USGS event API (earthquake.usgs.gov/fdsnws) → USGS earthquake map (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if the USGS earthquake catalog lists an event of magnitude 6.0 or more with its epicentre inside 24° to 46° latitude, 122° to 154° longitude (the Japan box), from 2026-11-16T00:00:00.000Z up to (not including) 2026-11-23T00:00:00.000Z.

Resolver: MonitoringRoom, automatic from USGS earthquake catalog

Calls closed — awaiting the source · Resolves from earthquake.usgs.gov

Outages

Will GitHub report a major or critical incident between 16–22 November 2026?

No calls yetas of 17:36 UTC
Rules
Measured
GitHub incidents of major or critical impact, by creation time
Window
2026-11-16 00:00 → 2026-11-23 00:00 UTC (end not included); calls close 2026-11-22 00:00 UTC
Source
GitHub status page (www.githubstatus.com)
Read order
www.githubstatus.com/api/v2/incidents.json, read hourly → www.githubstatus.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if www.githubstatus.com lists an incident created from 2026-11-16T00:00:00.000Z up to (not including) 2026-11-23T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from GitHub status page (www.githubstatus.com)

Calls closed — awaiting the source · Resolves from githubstatus.com

Crypto hacks

Will a crypto hack of $10M or more happen between 17–22 November 2026?

No calls yetas of 17:36 UTC

Resolved: Yes

Rules
Measured
Crypto hacks of US$10,000,000 or more, by the incident's listed date (UTC)
Window
2026-11-17 00:00 → 2026-11-23 00:00 UTC (end not included); calls close 2026-11-22 00:00 UTC
Source
DefiLlama hacks dataset
Read order
DefiLlama hacks dataset (live) → MonitoringRoom's stored copy of the dataset — a YES only; a NO waits for the live feed
Void
If the source stops publishing before close, the question is void and unscored.

YES if DefiLlama's hacks dataset lists an incident dated 17–22 November 2026 (UTC) with an amount of US$10,000,000 or more. Late listings count until 7 days after the window ends.

Resolver: MonitoringRoom, automatic from DefiLlama hacks dataset

· Resolves from defillama.com

Earthquakes

Will a magnitude 6.0+ earthquake strike the Indonesia region between 1–30 November 2026?

75%— 0 pts 24 hcrowd · 1 calleras of 17:36 UTC

Resolved: Yes

Rules
Measured
Earthquakes of magnitude 6.0 or more with the epicentre in the Indonesia box
Window
2026-11-01 00:00 → 2026-12-01 00:00 UTC (end not included); calls close 2026-11-29 00:00 UTC
Source
USGS earthquake catalog
Read order
USGS event API (earthquake.usgs.gov/fdsnws) → USGS earthquake map (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if the USGS earthquake catalog lists an event of magnitude 6.0 or more with its epicentre inside -11° to 6° latitude, 95° to 141° longitude (the Indonesia box), from 2026-11-01T00:00:00.000Z up to (not including) 2026-12-01T00:00:00.000Z.

Resolver: MonitoringRoom, automatic from USGS earthquake catalog

· Resolves from earthquake.usgs.gov

Crypto hacks

Will a crypto hack of $10M or more happen between 16–22 November 2026?

No calls yetas of 17:36 UTC

Resolved: Yes

Rules
Measured
Crypto hacks of US$10,000,000 or more, by the incident's listed date (UTC)
Window
2026-11-16 00:00 → 2026-11-23 00:00 UTC (end not included); calls close 2026-11-22 00:00 UTC
Source
DefiLlama hacks dataset
Read order
DefiLlama hacks dataset (live) → MonitoringRoom's stored copy of the dataset — a YES only; a NO waits for the live feed
Void
If the source stops publishing before close, the question is void and unscored.

YES if DefiLlama's hacks dataset lists an incident dated 16–22 November 2026 (UTC) with an amount of US$10,000,000 or more. Late listings count until 7 days after the window ends.

Resolver: MonitoringRoom, automatic from DefiLlama hacks dataset

· Resolves from defillama.com

Earthquakes

Will a magnitude 6.0+ earthquake strike the Japan region between 9–15 November 2026?

75%— 0 pts 24 hcrowd · 1 calleras of 17:36 UTC

Resolved: No

Rules
Measured
Earthquakes of magnitude 6.0 or more with the epicentre in the Japan box
Window
2026-11-09 00:00 → 2026-11-16 00:00 UTC (end not included); calls close 2026-11-15 00:00 UTC
Source
USGS earthquake catalog
Read order
USGS event API (earthquake.usgs.gov/fdsnws) → USGS earthquake map (staff review)
Void
If the source stops publishing before close, the question is void and unscored.

YES if the USGS earthquake catalog lists an event of magnitude 6.0 or more with its epicentre inside 24° to 46° latitude, 122° to 154° longitude (the Japan box), from 2026-11-09T00:00:00.000Z up to (not including) 2026-11-16T00:00:00.000Z.

Resolver: MonitoringRoom, automatic from USGS earthquake catalog

· Resolves from earthquake.usgs.gov

Crypto hacks

Will a crypto hack of $10M or more happen between 3–8 November 2026?

No calls yetas of 17:36 UTC

Resolved: No

Rules
Measured
Crypto hacks of US$10,000,000 or more, by the incident's listed date (UTC)
Window
2026-11-03 00:00 → 2026-11-09 00:00 UTC (end not included); calls close 2026-11-08 00:00 UTC
Source
DefiLlama hacks dataset
Read order
DefiLlama hacks dataset (live) → MonitoringRoom's stored copy of the dataset — a YES only; a NO waits for the live feed
Void
If the source stops publishing before close, the question is void and unscored.

YES if DefiLlama's hacks dataset lists an incident dated 3–8 November 2026 (UTC) with an amount of US$10,000,000 or more. Late listings count until 7 days after the window ends.

Resolver: MonitoringRoom, automatic from DefiLlama hacks dataset

· Resolves from defillama.com

Crypto hacks

Will a crypto hack of $10M or more happen between 9–15 November 2026?

56%— 0 pts 24 hcrowd · 2 callersas of 17:36 UTC
Rules
Measured
Crypto hacks of US$10,000,000 or more, by the incident's listed date (UTC)
Window
2026-11-09 00:00 → 2026-11-16 00:00 UTC (end not included); calls close 2026-11-15 00:00 UTC
Source
DefiLlama hacks dataset
Read order
DefiLlama hacks dataset (live) → MonitoringRoom's stored copy of the dataset — a YES only; a NO waits for the live feed
Void
If the source stops publishing before close, the question is void and unscored.

YES if DefiLlama's hacks dataset lists an incident dated 9–15 November 2026 (UTC) with an amount of US$10,000,000 or more. Late listings count until 7 days after the window ends.

Resolver: MonitoringRoom, automatic from DefiLlama hacks dataset

Calls closed — awaiting the source · Resolves from defillama.com

Outages

Will GitHub report a major or critical incident between 10–15 November 2026?

No calls yetas of 17:36 UTC

Resolved: Yes

Rules
Measured
GitHub incidents of major or critical impact, by creation time
Window
2026-11-10 01:00 → 2026-11-16 00:00 UTC (end not included); calls close 2026-11-15 00:00 UTC
Source
GitHub status page (www.githubstatus.com)
Read order
www.githubstatus.com/api/v2/incidents.json, read hourly → www.githubstatus.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if www.githubstatus.com lists an incident created from 2026-11-10T01:00:22.107Z up to (not including) 2026-11-16T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from GitHub status page (www.githubstatus.com)

· Resolves from githubstatus.com

Outages

Will GitHub report a major or critical incident between 9–15 November 2026?

No calls yetas of 17:36 UTC

Resolved: Yes

Rules
Measured
GitHub incidents of major or critical impact, by creation time
Window
2026-11-09 20:00 → 2026-11-16 00:00 UTC (end not included); calls close 2026-11-15 00:00 UTC
Source
GitHub status page (www.githubstatus.com)
Read order
www.githubstatus.com/api/v2/incidents.json, read hourly → www.githubstatus.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if www.githubstatus.com lists an incident created from 2026-11-09T20:00:27.139Z up to (not including) 2026-11-16T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from GitHub status page (www.githubstatus.com)

· Resolves from githubstatus.com

Outages

Will GitHub report a major or critical incident between 9–15 November 2026?

No calls yetas of 17:36 UTC

Resolved: Yes

Rules
Measured
GitHub incidents of major or critical impact, by creation time
Window
2026-11-09 13:00 → 2026-11-16 00:00 UTC (end not included); calls close 2026-11-15 00:00 UTC
Source
GitHub status page (www.githubstatus.com)
Read order
www.githubstatus.com/api/v2/incidents.json, read hourly → www.githubstatus.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if www.githubstatus.com lists an incident created from 2026-11-09T13:00:27.145Z up to (not including) 2026-11-16T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from GitHub status page (www.githubstatus.com)

· Resolves from githubstatus.com

Outages

Will GitHub report a major or critical incident between 9–15 November 2026?

95%— 0 pts 24 hcrowd · 1 calleras of 17:36 UTC

Resolved: Yes

Rules
Measured
GitHub incidents of major or critical impact, by creation time
Window
2026-11-09 00:00 → 2026-11-16 00:00 UTC (end not included); calls close 2026-11-15 00:00 UTC
Source
GitHub status page (www.githubstatus.com)
Read order
www.githubstatus.com/api/v2/incidents.json, read hourly → www.githubstatus.com/history (staff review of a coverage gap)
Void
If the source stops publishing before close, the question is void and unscored.

YES if www.githubstatus.com lists an incident created from 2026-11-09T00:00:00.000Z up to (not including) 2026-11-16T00:00:00.000Z whose impact is "major" or "critical". MonitoringRoom reads the page hourly; a NO needs the whole window read without a gap.

Resolver: MonitoringRoom, automatic from GitHub status page (www.githubstatus.com)

· Resolves from githubstatus.com