Última hora
United States flag Teerão tem armas biológicas? Trump pondera atacar o Irão Observador · agora mesmo•France flag França: Estrasburgo lidera mercados de Natal mais acessíveis da Europa Euronews · agora mesmo•Europa quer que as famílias estejam preparadas para as crises. Mas e se não for possível preparar-se? Euronews · agora mesmo•Assista ao Jornal da Manhã g1 · agora mesmo•Tânia Graça: “Não odeio os homens, o que odeio é este sistema patriarcal” Público · há 1 h•“Será difícil abrir mão de armas nucleares”, diz Trump diante de Putin e Xi CNN Brasil · há 1 h•Gil de graça em Niterói, eventos da Semana da Consciência Negra, Honk! Rio: o que fazer no Rio g1 · há 1 h•Portugal flag Isaltino deve achar que em Portugal vale tudo Observador · há 1 h•United States flag Teerão tem armas biológicas? Trump pondera atacar o Irão Observador · agora mesmo•France flag França: Estrasburgo lidera mercados de Natal mais acessíveis da Europa Euronews · agora mesmo•Europa quer que as famílias estejam preparadas para as crises. Mas e se não for possível preparar-se? Euronews · agora mesmo•Assista ao Jornal da Manhã g1 · agora mesmo•Tânia Graça: “Não odeio os homens, o que odeio é este sistema patriarcal” Público · há 1 h•“Será difícil abrir mão de armas nucleares”, diz Trump diante de Putin e Xi CNN Brasil · há 1 h•Gil de graça em Niterói, eventos da Semana da Consciência Negra, Honk! Rio: o que fazer no Rio g1 · há 1 h•Portugal flag Isaltino deve achar que em Portugal vale tudo Observador · há 1 h

This revision as JSON · Prints cleanly from your browser's print command.

1What changed since the last material update?

Compared with brief revision 1 (incident revision 1):

  • Status changed: investigating → monitoring · incident revision 2
FieldBeforeNow
statusinvestigatingmonitoringchanged
provider impactminorminorsame
servicesCopilot AI Model ProvidersCopilot AI Model Providerssame
regionsnone namednone namedsame
mitigation or recoverythe provider is investigatingthe provider reports a fix in place and is monitoring
From the provider's status term, not from a separate statement.
changed
cause——
Not stated by the provider in a structured field.
same

2Who says so, and when?

ClaimValueEvidence
Incident statusmonitoringProvider statement GitHub · published 2026-11-18 09:13 UTC · incident revision 2 · fonte ↗
Provider impact levelminorProvider statement GitHub · published 2026-11-18 09:00 UTC · incident revision 1 · fonte ↗
Services namedCopilot AI Model ProvidersProvider statement GitHub · published 2026-11-18 09:00 UTC · incident revision 1 · fonte ↗
Regions namednone named in a structured fieldProvider statement GitHub · published 2026-11-18 09:00 UTC · incident revision 1 · fonte ↗
Latest provider updateThe degradation affecting Copilot AI Model Providers has been mitigated. We are monitoring to ensure stability.Provider statement GitHub · published 2026-11-18 09:13 UTC · incident revision 2 · fonte ↗
Severity used for sorting1Spike inference SpikeTrendWatch · incident revision 2

Independent reporting and observable signals: none attached to this incident. Only the provider's own statements are shown. Public attention (for example a search spike) shows interest only. It is not evidence of cause or impact.

Open questions

  • Cause: not stated by the provider in a structured field.
  • Customer impact: not established. The provider reports its own systems; impact on a specific business needs that business's own evidence.
  • Region: GitHub names no region in a structured field (the title names a place; Spike does not turn titles into regions).
Began (provider)2026-11-18 09:00 UTC
Published by GitHub2026-11-18 09:13 UTC
Observed and published by Spike2026-11-18 09:14 UTC
Deliveredper workspace, in its private view

3Which business service should I check?

That depends on what your business runs on. See the private view in a synthetic demo. In Spike Pro (free beta), list the providers and services you depend on; your private view of this brief then shows which business service each revision touches, whether it is a direct match or a possible exposure, and why. Customer impact always needs your own evidence.

4What did we know then?

Revision 2 uses only what Spike had recorded by 2026-11-18 09:14 UTC: incident revisions 1, 2. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint b938ee8ae306142c).

Known later, at brief revision 3 (2026-11-18 09:36 UTC): Resolved. Open revision 3

5Who received the correction?

No correction has been published for this incident.

Delivery outcomes are private to each workspace and appear in its own view of this brief.

Handoff summary

Plain text to paste into a ticket or shift handoff.

Schema spike.evidence-brief/1. A brief is built from Spike's append-only incident revisions; it adds no facts of its own beyond the labeled Spike inferences. Incident record · API contract · Open another brief