Rewindex

CompaniesLatticeIncidents

Lattice: Lattice notifications delayed

MinorStatus: resolvedStarted Resolved (41 min)2 updatesstspg.io (opens in new tab)
Part of an outage event

Cloudflare outage, Nov 18, 2025 · 77 vendors, 81 incidents

Lattice’s incident blames Cloudflare as the cause. (hop 1, posted +2 h 55 min vs the first vendor naming Cloudflare)

“…s affected. Our Engineering Team have identified that this was caused by the outages with Cloudflare and our email service provider. Notifications are now being re-sent for any notifications affected.…”

Swipe sideways to see the whole diagram.

Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamed CloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamed CloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, Maven Central +4Lattice (this incident)posted +2 h 55 min
Cloudflareown incident not archivedWithin an hour13 vendors, 13 blamedCloudflareStytch, Zed, NordLayer +101 to 4 hours later19 vendors, 19 blamedCloudflareGitLab, Gorgias, Cursor +16Later7 vendors, 7 blamed CloudflareRudderStack, Brex, MavenCentral +4Lattice (this incident)posted +2 h 55 min
Lattice is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Cloudflare<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed Cloudflare<br/>Stytch, Zed, NordLayer +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>19 vendors, 19 blamed Cloudflare<br/>GitLab, Gorgias, Cursor +16"]:::blames
  root --> h4
  later["Later<br/>7 vendors, 7 blamed Cloudflare<br/>RudderStack, Brex, Maven Central +4"]:::blames
  root --> later
  me["Lattice (this incident)<br/>posted +2 h 55 min"]:::me
  h4 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Affected components: Lattice Application

Timeline of updates

  1. investigating

    We're aware of delays in the sending of Lattice notifications via email, Teams, and Slack. Our Engineering Team are investigating the root cause behind these delays, and will be re-sending any delayed notifications.

  2. resolved

    Notifications are now being re-sent for any notifications affected. Our Engineering Team have identified that this was caused by the outages with Cloudflare and our email service provider.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Lattice profileRecent Lattice incidentsMarkdownJSON