**The August 6 GitHub Actions outage, which ran roughly 10 hours 42 minutes from the initial incident declaration at 15:22 UTC until resolution early on August 7, currently sets the benchmark for the longest critical incident this month.** That duration falls squarely in the 6–12 hour range and has anchored trader consensus at 85.5% implied probability. A second, platform-wide outage on August 17 lasted 7 hours 47 minutes and affected github.com, authentication, Actions, APIs, pull requests, issues, and Copilot, but did not surpass the earlier incident. GitHub’s August 20 post-mortem highlighted rapid traffic growth and scaling limits in its Central US data center as root causes, while confirming no longer-duration events have occurred since. With only days remaining in August and no new critical incidents reported, the market-implied odds reflect the standing record set by the August 6 event and the low likelihood of an extended disruption before month-end.
Polymarketデータを参照したAI生成の実験的な要約。これは取引アドバイスではなく、このマーケットの解決方法には一切関係ありません。 · 更新日6～12時間 86%
12時間以上 11%
1時間未満 1.3%
1～3時間 <1%
新規
新規
2026/08/31
1時間未満
1%
1～3時間
1%
3〜6時間
<1%
6～12時間
86%
12時間以上
11%
6～12時間 86%
12時間以上 11%
1時間未満 1.3%
1～3時間 <1%
新規
新規
2026/08/31
1時間未満
$674 Vol.
1%
1～3時間
$285 Vol.
1%
3〜6時間
$227 Vol.
<1%
6～12時間
$2,706 Vol.
86%
12時間以上
$807 Vol.
11%
This market will resolve according to the duration of the longest qualifying incident that begins between August 1, 2026, 12:00 AM ET and August 31, 2026, 11:59 PM ET.
If no qualifying incident begins during this period, this market will resolve to the lowest bracket (“<1 hour”).
An incident will qualify if the official GitHub Status Page (githubstatus.com) or the official GitHub Status API (githubstatus.com/api) classifies the incident's impact as "critical," unless its affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers. Incidents listing no affected components will qualify. GitHub classifies incident impact as None, Minor, Major, or Critical; only Critical will qualify. Component status labels (e.g. "Degraded Performance," "Partial Outage," or "Major Outage") will have no bearing on this market absent a qualifying critical incident.
Revisions published after an incident is marked “Resolved” will not be considered.
An incident's duration is the time between its official start timestamp and the time the incident is marked “Resolved,” as published by the GitHub Status Page or the GitHub Status API. An incident will be attributed to the month in which it begins, based on its official start timestamp converted to Eastern Time (ET); an incident that begins during the period and is resolved after the period ends will count in full.
If the determined value falls exactly on the boundary between two brackets, this market will resolve to the higher bracket.
If an incident that began during the period remains unresolved at the end of the period, this market will remain open and resolve at the earlier of: (i) when the incident is officially resolved, or (ii) the end of the seventh calendar day (ET) after the end of the period, at which point the market will resolve based on the official information available at that time, with any unresolved incident's duration measured from its official start timestamp to that time.
Incidents whose affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers will not qualify. Scheduled maintenance will not qualify.
The primary resolution source for this market will be official GitHub system-status information published at https://www.githubstatus.com/, including the official GitHub Status API (https://www.githubstatus.com/api); however, a consensus of credible reporting may also be used.**The August 6 GitHub Actions outage, which ran roughly 10 hours 42 minutes from the initial incident declaration at 15:22 UTC until resolution early on August 7, currently sets the benchmark for the longest critical incident this month.**
That duration falls squarely in the 6–12 hour range and has anchored trader consensus at 85.5% implied probability. A second, platform-wide outage on August 17 lasted 7 hours 47 minutes and affected github.com, authentication, Actions, APIs, pull requests, issues, and Copilot, but did not surpass the earlier incident. GitHub’s August 20 post-mortem highlighted rapid traffic growth and scaling limits in its Central US data center as root causes, while confirming no longer-duration events have occurred since. With only days remaining in August and no new critical incidents reported, the market-implied odds reflect the standing record set by the August 6 event and the low likelihood of an extended disruption before month-end.
This market will resolve according to the duration of the longest qualifying incident that begins between August 1, 2026, 12:00 AM ET and August 31, 2026, 11:59 PM ET.
If no qualifying incident begins during this period, this market will resolve to the lowest bracket (“<1 hour”).
An incident will qualify if the official GitHub Status Page (githubstatus.com) or the official GitHub Status API (githubstatus.com/api) classifies the incident's impact as "critical," unless its affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers. Incidents listing no affected components will qualify. GitHub classifies incident impact as None, Minor, Major, or Critical; only Critical will qualify. Component status labels (e.g. "Degraded Performance," "Partial Outage," or "Major Outage") will have no bearing on this market absent a qualifying critical incident.
Revisions published after an incident is marked “Resolved” will not be considered.
An incident's duration is the time between its official start timestamp and the time the incident is marked “Resolved,” as published by the GitHub Status Page or the GitHub Status API. An incident will be attributed to the month in which it begins, based on its official start timestamp converted to Eastern Time (ET); an incident that begins during the period and is resolved after the period ends will count in full.
If the determined value falls exactly on the boundary between two brackets, this market will resolve to the higher bracket.
If an incident that began during the period remains unresolved at the end of the period, this market will remain open and resolve at the earlier of: (i) when the incident is officially resolved, or (ii) the end of the seventh calendar day (ET) after the end of the period, at which point the market will resolve based on the official information available at that time, with any unresolved incident's duration measured from its official start timestamp to that time.
Incidents whose affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers will not qualify. Scheduled maintenance will not qualify.
The primary resolution source for this market will be official GitHub system-status information published at https://www.githubstatus.com/, including the official GitHub Status API (https://www.githubstatus.com/api); however, a consensus of credible reporting may also be used.
If no qualifying incident begins during this period, this market will resolve to the lowest bracket (“<1 hour”).
An incident will qualify if the official GitHub Status Page (githubstatus.com) or the official GitHub Status API (githubstatus.com/api) classifies the incident's impact as "critical," unless its affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers. Incidents listing no affected components will qualify. GitHub classifies incident impact as None, Minor, Major, or Critical; only Critical will qualify. Component status labels (e.g. "Degraded Performance," "Partial Outage," or "Major Outage") will have no bearing on this market absent a qualifying critical incident.
Revisions published after an incident is marked “Resolved” will not be considered.
An incident's duration is the time between its official start timestamp and the time the incident is marked “Resolved,” as published by the GitHub Status Page or the GitHub Status API. An incident will be attributed to the month in which it begins, based on its official start timestamp converted to Eastern Time (ET); an incident that begins during the period and is resolved after the period ends will count in full.
If the determined value falls exactly on the boundary between two brackets, this market will resolve to the higher bracket.
If an incident that began during the period remains unresolved at the end of the period, this market will remain open and resolve at the earlier of: (i) when the incident is officially resolved, or (ii) the end of the seventh calendar day (ET) after the end of the period, at which point the market will resolve based on the official information available at that time, with any unresolved incident's duration measured from its official start timestamp to that time.
Incidents whose affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers will not qualify. Scheduled maintenance will not qualify.
The primary resolution source for this market will be official GitHub system-status information published at https://www.githubstatus.com/, including the official GitHub Status API (https://www.githubstatus.com/api); however, a consensus of credible reporting may also be used.
マーケット開始日： Aug 19, 2026, 8:44 PM ET
音量
$4,700終了日
2026/08/31マーケット開始日
Aug 19, 2026, 8:44 PM ETResolver
0x69c47De9D...This market will resolve according to the duration of the longest qualifying incident that begins between August 1, 2026, 12:00 AM ET and August 31, 2026, 11:59 PM ET.
If no qualifying incident begins during this period, this market will resolve to the lowest bracket (“<1 hour”).
An incident will qualify if the official GitHub Status Page (githubstatus.com) or the official GitHub Status API (githubstatus.com/api) classifies the incident's impact as "critical," unless its affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers. Incidents listing no affected components will qualify. GitHub classifies incident impact as None, Minor, Major, or Critical; only Critical will qualify. Component status labels (e.g. "Degraded Performance," "Partial Outage," or "Major Outage") will have no bearing on this market absent a qualifying critical incident.
Revisions published after an incident is marked “Resolved” will not be considered.
An incident's duration is the time between its official start timestamp and the time the incident is marked “Resolved,” as published by the GitHub Status Page or the GitHub Status API. An incident will be attributed to the month in which it begins, based on its official start timestamp converted to Eastern Time (ET); an incident that begins during the period and is resolved after the period ends will count in full.
If the determined value falls exactly on the boundary between two brackets, this market will resolve to the higher bracket.
If an incident that began during the period remains unresolved at the end of the period, this market will remain open and resolve at the earlier of: (i) when the incident is officially resolved, or (ii) the end of the seventh calendar day (ET) after the end of the period, at which point the market will resolve based on the official information available at that time, with any unresolved incident's duration measured from its official start timestamp to that time.
Incidents whose affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers will not qualify. Scheduled maintenance will not qualify.
The primary resolution source for this market will be official GitHub system-status information published at https://www.githubstatus.com/, including the official GitHub Status API (https://www.githubstatus.com/api); however, a consensus of credible reporting may also be used.**The August 6 GitHub Actions outage, which ran roughly 10 hours 42 minutes from the initial incident declaration at 15:22 UTC until resolution early on August 7, currently sets the benchmark for the longest critical incident this month.**
That duration falls squarely in the 6–12 hour range and has anchored trader consensus at 85.5% implied probability. A second, platform-wide outage on August 17 lasted 7 hours 47 minutes and affected github.com, authentication, Actions, APIs, pull requests, issues, and Copilot, but did not surpass the earlier incident. GitHub’s August 20 post-mortem highlighted rapid traffic growth and scaling limits in its Central US data center as root causes, while confirming no longer-duration events have occurred since. With only days remaining in August and no new critical incidents reported, the market-implied odds reflect the standing record set by the August 6 event and the low likelihood of an extended disruption before month-end.
This market will resolve according to the duration of the longest qualifying incident that begins between August 1, 2026, 12:00 AM ET and August 31, 2026, 11:59 PM ET.
If no qualifying incident begins during this period, this market will resolve to the lowest bracket (“<1 hour”).
An incident will qualify if the official GitHub Status Page (githubstatus.com) or the official GitHub Status API (githubstatus.com/api) classifies the incident's impact as "critical," unless its affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers. Incidents listing no affected components will qualify. GitHub classifies incident impact as None, Minor, Major, or Critical; only Critical will qualify. Component status labels (e.g. "Degraded Performance," "Partial Outage," or "Major Outage") will have no bearing on this market absent a qualifying critical incident.
Revisions published after an incident is marked “Resolved” will not be considered.
An incident's duration is the time between its official start timestamp and the time the incident is marked “Resolved,” as published by the GitHub Status Page or the GitHub Status API. An incident will be attributed to the month in which it begins, based on its official start timestamp converted to Eastern Time (ET); an incident that begins during the period and is resolved after the period ends will count in full.
If the determined value falls exactly on the boundary between two brackets, this market will resolve to the higher bracket.
If an incident that began during the period remains unresolved at the end of the period, this market will remain open and resolve at the earlier of: (i) when the incident is officially resolved, or (ii) the end of the seventh calendar day (ET) after the end of the period, at which point the market will resolve based on the official information available at that time, with any unresolved incident's duration measured from its official start timestamp to that time.
Incidents whose affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers will not qualify. Scheduled maintenance will not qualify.
The primary resolution source for this market will be official GitHub system-status information published at https://www.githubstatus.com/, including the official GitHub Status API (https://www.githubstatus.com/api); however, a consensus of credible reporting may also be used.
If no qualifying incident begins during this period, this market will resolve to the lowest bracket (“<1 hour”).
An incident will qualify if the official GitHub Status Page (githubstatus.com) or the official GitHub Status API (githubstatus.com/api) classifies the incident's impact as "critical," unless its affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers. Incidents listing no affected components will qualify. GitHub classifies incident impact as None, Minor, Major, or Critical; only Critical will qualify. Component status labels (e.g. "Degraded Performance," "Partial Outage," or "Major Outage") will have no bearing on this market absent a qualifying critical incident.
Revisions published after an incident is marked “Resolved” will not be considered.
An incident's duration is the time between its official start timestamp and the time the incident is marked “Resolved,” as published by the GitHub Status Page or the GitHub Status API. An incident will be attributed to the month in which it begins, based on its official start timestamp converted to Eastern Time (ET); an incident that begins during the period and is resolved after the period ends will count in full.
If the determined value falls exactly on the boundary between two brackets, this market will resolve to the higher bracket.
If an incident that began during the period remains unresolved at the end of the period, this market will remain open and resolve at the earlier of: (i) when the incident is officially resolved, or (ii) the end of the seventh calendar day (ET) after the end of the period, at which point the market will resolve based on the official information available at that time, with any unresolved incident's duration measured from its official start timestamp to that time.
Incidents whose affected components, once the incident is marked "Resolved," consist solely of Copilot and/or Copilot AI Model Providers will not qualify. Scheduled maintenance will not qualify.
The primary resolution source for this market will be official GitHub system-status information published at https://www.githubstatus.com/, including the official GitHub Status API (https://www.githubstatus.com/api); however, a consensus of credible reporting may also be used.
音量
$4,700終了日
2026/08/31マーケット開始日
Aug 19, 2026, 8:44 PM ETResolver
0x69c47De9D...**The August 6 GitHub Actions outage, which ran roughly 10 hours 42 minutes from the initial incident declaration at 15:22 UTC until resolution early on August 7, currently sets the benchmark for the longest critical incident this month.** That duration falls squarely in the 6–12 hour range and has anchored trader consensus at 85.5% implied probability. A second, platform-wide outage on August 17 lasted 7 hours 47 minutes and affected github.com, authentication, Actions, APIs, pull requests, issues, and Copilot, but did not surpass the earlier incident. GitHub’s August 20 post-mortem highlighted rapid traffic growth and scaling limits in its Central US data center as root causes, while confirming no longer-duration events have occurred since. With only days remaining in August and no new critical incidents reported, the market-implied odds reflect the standing record set by the August 6 event and the low likelihood of an extended disruption before month-end.
Polymarketデータを参照したAI生成の実験的な要約。これは取引アドバイスではなく、このマーケットの解決方法には一切関係ありません。 · 更新日
外部リンクに注意してください。
外部リンクに注意してください。
よくある質問