Breaking

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: identified → monitoring · incident revision 2
FieldBeforeNow
statusidentifiedmonitoringchanged
provider impactnonenonesame
servicesnone namednone namedsame
regionsnone namednone namedsame
mitigation or recoverythe provider has identified the issue and is working on a fixthe 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 Mailgun · published 2026-11-18 03:58 UTC · incident revision 2 · source ↗
Provider impact levelnoneProvider statement Mailgun · published 2026-11-17 20:31 UTC · incident revision 1 · source ↗
Services namednone namedProvider statement Mailgun · published 2026-11-17 20:31 UTC · incident revision 1 · source ↗
Regions namednone named in a structured fieldProvider statement Mailgun · published 2026-11-17 20:31 UTC · incident revision 1 · source ↗
Latest provider updateAddresses that were impacted are in the process of being removed from suppression lists.Provider statement Mailgun · published 2026-11-18 03:58 UTC · incident revision 2 · source ↗
Severity used for sorting0Spike 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: Mailgun names no region in a structured field.
Began (provider)2026-11-17 20:31 UTC
Published by Mailgun2026-11-18 03:58 UTC
Observed and published by Spike2026-11-18 04:01 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 04:01 UTC: incident revisions 1, 2. Later updates are excluded, so this view reads the same every time it is opened (content fingerprint c70c4e105be64117).

Known later, at brief revision 3 (2026-11-18 19:35 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