CheckUpstream measured Prisma at 100.000% availability across 2023 independent checks (global · api). 10 incidents were recorded in the past 12 months; the most recent resolved 28 days ago after 49 minutes. Status signals are polled from Prisma's official Atlassian Statuspage status page, alongside independent probes and community reports.
180 days measured availability how this is computed
100.000%
global · api · n=2023 · p95 1077ms (30d)
Share of our own checks against Prisma endpoints that returned Prisma's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 10 incidents · 176 of 180 days with none posted · 9h 2m of declared impact
Fewer incidents in the last 30 days than 34% of 232 tracked services.
Share of each window with no impact declared by Prisma
7d
99.932%
30d
99.984%
90d
99.995%
180d
99.791%
1y
99.897%
Downtime like this can be refundable
If you're a paying Prisma customer, outages in these windows may count against Prisma's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
Track your Prisma entitlement →Does Prisma actually matter to you?
A Prisma outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Check a repository →Predicted resolution
n=9~132m (p25 49m – p75 232m)
Based on 9 historical Major incidents · currently 10m elapsed.
From 9 incidents Prisma published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Prisma takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Excluded: 1 still open.
Sep 1, 06:52 UTC · in progress · Identified
Aug 3, 10:01 UTC · resolved in 49m · Resolved
Jul 31, 12:27 UTC · resolved in 1h 7m · Resolved
12signals across 1 source
Synthetic probes 12
All of these are CheckUpstream's own probes. Nobody else has reported Prisma in this window, so nothing here is corroboration.
Live Prisma status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/prisma)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Prisma is currently Degraded. CheckUpstream tracks Prisma in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Prisma's last resolved incident started 28 days ago and lasted 49 minutes (degraded performance).
Looking for the live "is Prisma down" view? See the Prisma Live status page.
Jul 17, 13:03 UTC · resolved in 3h 52m · Resolved
Prisma's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Prisma endpoints. It is the share of checks that returned the expected response, not a figure taken from Prisma's status page.
Sign up to CheckUpstream and add Prisma to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
We poll Prisma's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.