Rewindex

CompaniesPrismaIncidents

Prisma: Web interface service disruption

CriticalStatus: resolvedStarted Resolved (1.0 h)1 updatewww.prisma-status.com (opens in new tab)
Part of an outage event

AWS outage, Jun 13, 2023 · 56 vendors, 56 incidents

Prisma’s incident started in the same window without naming AWS (timing only, not evidence of a link). (timing only, posted +10 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, Temporal Cloud +101 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana +4Prisma (this incident)posted +10 min
same windowAWSown incident not archivedWithin an hour13 vendors, 13 blamed AWSPipedream, Wiz, TemporalCloud +101 to 4 hours later7 vendors, 6 blamed AWSCockroachDB, Vanta, Asana +4Prisma (this incident)posted +10 min
Prisma is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["AWS<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>13 vendors, 13 blamed AWS<br/>Pipedream, Wiz, Temporal Cloud +10"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>7 vendors, 6 blamed AWS<br/>CockroachDB, Vanta, Asana +4"]:::blames
  root --> h4
  me["Prisma (this incident)<br/>posted +10 min"]:::me
  root -.->|"same window"| 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.

Timeline of updates

  1. resolved

    This incident has been resolved.

From Prisma’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Impact, status and times are the vendor’s own, as last archived. View on www.prisma-status.com (opens in new tab).

Prisma profileRecent Prisma incidentsMarkdownJSON