GitHub reports reduced availability of Grok 4.6 and Grok 4.7 in Copilot
According to GitHub, Grok 4.6 and Grok 4.7 have reduced availability in Copilot, including within the IDE. The report attributes the disruption to an issue at the model provider. The company recommends selecting another model or the Auto option.
GitHub announced reduced availability of Grok 4.6 and Grok 4.7 in Copilot, including within the IDE. According to its status report, the cause is an issue at the model provider, which GitHub is working with to resolve it.
The company announced an investigation into reports of degraded performance on 23 October at 23:41 UTC. An update at 23:42 UTC specified the affected models and their reduced availability. To continue working, GitHub recommends selecting another model or the Auto option.
Why it matters
The disruption also affects work with AI directly within the IDE. The ability to switch models may therefore be important for users of the affected models to continue working; this is the approach GitHub recommends.
Two audiences, two different impacts
What this means
For individuals
If you use Grok 4.6 or Grok 4.7 in Copilot for coding, the model’s availability may be limited even directly within the IDE.
For a business
For development teams relying on the affected models, the incident poses a risk of workflow disruption due to their dependence on an external model provider.
ProcessesCheck the original
Event sources
clearly official source · 1 publisher, 0 independent. We count feeds from the same owner only once.