Cloudflare's last critical (red/P0) incident occurred on February 20, 2026, a six-hour global outage triggered by a bug in Bring Your Own IP prefix deletion automation, affecting BGP routes for thousands of customer prefixes and causing widespread timeouts. Post-mortem analysis detailed preventive upgrades like API schema validation, deployment snapshots for rollbacks, and circuit breakers on large withdrawals. Since then, no critical incidents have been reported through April 29, with only elevated (orange/P1) issues such as March 31 R2 APAC error rates, late February Cache Purge 500s, and SLC datacenter 5xx spikes, plus a minor April 28 X-Forwarded-For header duplication. Traders monitor cloudflarestatus.com/history for red alerts ahead of resolution, amid stable operations and scheduled maintenances like April 29 Phoenix and Cleveland datacenters.
Экспериментальная сводка, созданная ИИ на основе данных Polymarket. Это не является торговой рекомендацией и не влияет на то, как разрешается этот рынок. · ОбновленоЕще один критический инцидент Cloudflare от...?
Еще один критический инцидент Cloudflare от...?
$698,190 Объем
31 мар. 2026 г.
28 февраля
Нет
31 марта
Нет
30 апреля
Да
31 мая
Да
30 июня
Да
$698,190 Объем
28 февраля
$113,449 Объем
Нет
31 марта
$126,980 Объем
Нет
30 апреля
$190,824 Объем
Да
31 мая
$79,298 Объем
Да
30 июня
$187,639 Объем
Да
This market will resolve to “Yes” if Cloudflare experiences any incident classified as Critical (red) as of the time it is marked as “Resolved” by the listed date (ET). Otherwise, this market will resolve to “No”.
Classifications of an incident while it is ongoing will have no bearing on the resolution of this market. Only classifications of events that are resolved will be considered.
Qualifying incidents include outages and other issues classified as critical when they are resolved, during this market's above specified timeframe.
An incident resolved outside this market’s timeframe will only qualify if ongoing at this market’s resolution time, in which case the market will remain open until that incident is marked as “Resolved,” and resolution will be based on the first impact classification thereafter, regardless of subsequent revisions or corrections.
Revisions that upgrade an incident’s impact classification to Critical will qualify if the incident was resolved and the revision is published within this market’s timeframe.
The primary resolution source for this market will be official information from Cloudflare (for example, on cloudflarestatus.com or cloudflarestatus.com/history); however, a consensus of credible reporting may also be used.Cloudflare's last critical (red/P0) incident occurred on February 20, 2026, a six-hour global outage triggered by a bug in Bring Your Own IP prefix deletion automation, affecting BGP routes for thousands of customer prefixes and causing widespread timeouts. Post-mortem analysis detailed preventive upgrades like API schema validation, deployment snapshots for rollbacks, and circuit breakers on large withdrawals. Since then, no critical incidents have been reported through April 29, with only elevated (orange/P1) issues such as March 31 R2 APAC error rates, late February Cache Purge 500s, and SLC datacenter 5xx spikes, plus a minor April 28 X-Forwarded-For header duplication. Traders monitor cloudflarestatus.com/history for red alerts ahead of resolution, amid stable operations and scheduled maintenances like April 29 Phoenix and Cleveland datacenters.
This market will resolve to “Yes” if Cloudflare experiences any incident classified as Critical (red) as of the time it is marked as “Resolved” by the listed date (ET). Otherwise, this market will resolve to “No”.
Classifications of an incident while it is ongoing will have no bearing on the resolution of this market. Only classifications of events that are resolved will be considered.
Qualifying incidents include outages and other issues classified as critical when they are resolved, during this market's above specified timeframe.
An incident resolved outside this market’s timeframe will only qualify if ongoing at this market’s resolution time, in which case the market will remain open until that incident is marked as “Resolved,” and resolution will be based on the first impact classification thereafter, regardless of subsequent revisions or corrections.
Revisions that upgrade an incident’s impact classification to Critical will qualify if the incident was resolved and the revision is published within this market’s timeframe.
The primary resolution source for this market will be official information from Cloudflare (for example, on cloudflarestatus.com or cloudflarestatus.com/history); however, a consensus of credible reporting may also be used.
Classifications of an incident while it is ongoing will have no bearing on the resolution of this market. Only classifications of events that are resolved will be considered.
Qualifying incidents include outages and other issues classified as critical when they are resolved, during this market's above specified timeframe.
An incident resolved outside this market’s timeframe will only qualify if ongoing at this market’s resolution time, in which case the market will remain open until that incident is marked as “Resolved,” and resolution will be based on the first impact classification thereafter, regardless of subsequent revisions or corrections.
Revisions that upgrade an incident’s impact classification to Critical will qualify if the incident was resolved and the revision is published within this market’s timeframe.
The primary resolution source for this market will be official information from Cloudflare (for example, on cloudflarestatus.com or cloudflarestatus.com/history); however, a consensus of credible reporting may also be used.
Открытие рынка: Feb 5, 2026, 4:06 PM ET
Объем
$698,190Дата окончания
30 июн. 2026 г.Открытие рынка
Feb 5, 2026, 4:06 PM ETResolver
0x65070BE91...Предложенный исход: Нет
Спор отсутствует
Окончательный исход: Нет
This market will resolve to “Yes” if Cloudflare experiences any incident classified as Critical (red) as of the time it is marked as “Resolved” by the listed date (ET). Otherwise, this market will resolve to “No”.
Classifications of an incident while it is ongoing will have no bearing on the resolution of this market. Only classifications of events that are resolved will be considered.
Qualifying incidents include outages and other issues classified as critical when they are resolved, during this market's above specified timeframe.
An incident resolved outside this market’s timeframe will only qualify if ongoing at this market’s resolution time, in which case the market will remain open until that incident is marked as “Resolved,” and resolution will be based on the first impact classification thereafter, regardless of subsequent revisions or corrections.
Revisions that upgrade an incident’s impact classification to Critical will qualify if the incident was resolved and the revision is published within this market’s timeframe.
The primary resolution source for this market will be official information from Cloudflare (for example, on cloudflarestatus.com or cloudflarestatus.com/history); however, a consensus of credible reporting may also be used.Cloudflare's last critical (red/P0) incident occurred on February 20, 2026, a six-hour global outage triggered by a bug in Bring Your Own IP prefix deletion automation, affecting BGP routes for thousands of customer prefixes and causing widespread timeouts. Post-mortem analysis detailed preventive upgrades like API schema validation, deployment snapshots for rollbacks, and circuit breakers on large withdrawals. Since then, no critical incidents have been reported through April 29, with only elevated (orange/P1) issues such as March 31 R2 APAC error rates, late February Cache Purge 500s, and SLC datacenter 5xx spikes, plus a minor April 28 X-Forwarded-For header duplication. Traders monitor cloudflarestatus.com/history for red alerts ahead of resolution, amid stable operations and scheduled maintenances like April 29 Phoenix and Cleveland datacenters.
This market will resolve to “Yes” if Cloudflare experiences any incident classified as Critical (red) as of the time it is marked as “Resolved” by the listed date (ET). Otherwise, this market will resolve to “No”.
Classifications of an incident while it is ongoing will have no bearing on the resolution of this market. Only classifications of events that are resolved will be considered.
Qualifying incidents include outages and other issues classified as critical when they are resolved, during this market's above specified timeframe.
An incident resolved outside this market’s timeframe will only qualify if ongoing at this market’s resolution time, in which case the market will remain open until that incident is marked as “Resolved,” and resolution will be based on the first impact classification thereafter, regardless of subsequent revisions or corrections.
Revisions that upgrade an incident’s impact classification to Critical will qualify if the incident was resolved and the revision is published within this market’s timeframe.
The primary resolution source for this market will be official information from Cloudflare (for example, on cloudflarestatus.com or cloudflarestatus.com/history); however, a consensus of credible reporting may also be used.
Classifications of an incident while it is ongoing will have no bearing on the resolution of this market. Only classifications of events that are resolved will be considered.
Qualifying incidents include outages and other issues classified as critical when they are resolved, during this market's above specified timeframe.
An incident resolved outside this market’s timeframe will only qualify if ongoing at this market’s resolution time, in which case the market will remain open until that incident is marked as “Resolved,” and resolution will be based on the first impact classification thereafter, regardless of subsequent revisions or corrections.
Revisions that upgrade an incident’s impact classification to Critical will qualify if the incident was resolved and the revision is published within this market’s timeframe.
The primary resolution source for this market will be official information from Cloudflare (for example, on cloudflarestatus.com or cloudflarestatus.com/history); however, a consensus of credible reporting may also be used.
Объем
$698,190Дата окончания
30 июн. 2026 г.Открытие рынка
Feb 5, 2026, 4:06 PM ETResolver
0x65070BE91...Предложенный исход: Нет
Спор отсутствует
Окончательный исход: Нет
Cloudflare's last critical (red/P0) incident occurred on February 20, 2026, a six-hour global outage triggered by a bug in Bring Your Own IP prefix deletion automation, affecting BGP routes for thousands of customer prefixes and causing widespread timeouts. Post-mortem analysis detailed preventive upgrades like API schema validation, deployment snapshots for rollbacks, and circuit breakers on large withdrawals. Since then, no critical incidents have been reported through April 29, with only elevated (orange/P1) issues such as March 31 R2 APAC error rates, late February Cache Purge 500s, and SLC datacenter 5xx spikes, plus a minor April 28 X-Forwarded-For header duplication. Traders monitor cloudflarestatus.com/history for red alerts ahead of resolution, amid stable operations and scheduled maintenances like April 29 Phoenix and Cleveland datacenters.
Экспериментальная сводка, созданная ИИ на основе данных Polymarket. Это не является торговой рекомендацией и не влияет на то, как разрешается этот рынок. · Обновлено
Не доверяй внешним ссылкам.
Не доверяй внешним ссылкам.
Часто задаваемые вопросы