Recent infrastructure strain at xAI’s compute partners, highlighted by the September 3 models outage lasting over three hours due to a Memphis data center issue, has shaped trader views on Grok web reliability. That event coincided with similar disruptions at OpenAI and Anthropic, underscoring shared scaling challenges for large language models amid rising usage. Current status pages show full operational uptime since then, yet historical patterns of multiple 2026 incidents and the ongoing Grok Bot Galaxy event through September 17 suggest elevated load risks. Delayed Grok 4.7 refinements and new connector features add further variables that could influence uptime through October.
Експериментальне резюме, згенероване ШІ з посиланням на дані Polymarket. Це не торгова порада і не впливає на вирішення цього ринку. · ОновленоGrok (Web) Outage by...?
September 30
50%
October 31
48%
December 31
62%
$0.00 Обс.
September 30
50%
October 31
48%
December 31
62%
Only incidents listed under Grok (Web) will be considered. Incidents affecting Grok in X, Grok (iOS), Grok (Android), or similar but not Grok (Web), will not qualify.
Incidents labeled “disruption” or “info” will not qualify.
An incident’s status while it remains ongoing will not determine the market’s resolution; only incidents marked “Resolved” will be considered.
An incident which is marked "Resolved" outside this market’s timeframe will only qualify if ongoing at the end of the listed calendar date (ET), in which case the market will remain open until that incident is marked “Resolved,” and resolution of this market will be based on the incident classification displayed immediately after it is marked "Resolved."
The primary resolution source for this market will be the official xAI Grok (Web) status page at https://status.x.ai/grok-com. If this resolution source is unavailable at check time, this market will remain open until it comes back online and resolve based on the first check after it becomes available. If it becomes permanently unavailable, this market will resolve to "No".
Ринок відкрито: Sep 8, 2026, 2:19 PM ET
Вирішувач
0x65070BE91...Only incidents listed under Grok (Web) will be considered. Incidents affecting Grok in X, Grok (iOS), Grok (Android), or similar but not Grok (Web), will not qualify.
Incidents labeled “disruption” or “info” will not qualify.
An incident’s status while it remains ongoing will not determine the market’s resolution; only incidents marked “Resolved” will be considered.
An incident which is marked "Resolved" outside this market’s timeframe will only qualify if ongoing at the end of the listed calendar date (ET), in which case the market will remain open until that incident is marked “Resolved,” and resolution of this market will be based on the incident classification displayed immediately after it is marked "Resolved."
The primary resolution source for this market will be the official xAI Grok (Web) status page at https://status.x.ai/grok-com. If this resolution source is unavailable at check time, this market will remain open until it comes back online and resolve based on the first check after it becomes available. If it becomes permanently unavailable, this market will resolve to "No".
Вирішувач
0x65070BE91...Recent infrastructure strain at xAI’s compute partners, highlighted by the September 3 models outage lasting over three hours due to a Memphis data center issue, has shaped trader views on Grok web reliability. That event coincided with similar disruptions at OpenAI and Anthropic, underscoring shared scaling challenges for large language models amid rising usage. Current status pages show full operational uptime since then, yet historical patterns of multiple 2026 incidents and the ongoing Grok Bot Galaxy event through September 17 suggest elevated load risks. Delayed Grok 4.7 refinements and new connector features add further variables that could influence uptime through October.
Експериментальне резюме, згенероване ШІ з посиланням на дані Polymarket. Це не торгова порада і не впливає на вирішення цього ринку. · Оновлено



Обережно з зовнішніми посиланнями.
Обережно з зовнішніми посиланнями.
Часті запитання