Vendor reports: operationalResolved · vendor status “resolved”Official status API

Usage quota issue on free tier

Reported by Prisma Data Platform · Databases · source last read just now

Vendor start
Jan 9, 2026, 13:43 UTC
Vendor's clock
Resolved
Jan 10, 2026, 00:30 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
10 h 47 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Prisma Data Platform reports operational: "Usage quota issue on free tier".[E1, E2]
  • The vendor marked it resolved at 2026-01-10 00:30 UTC.[E3, E7]

Affected products and regions

  • Components: Prisma Postgres, Prisma Console, Prisma Accelerate.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-01-10 00:30 UTC · summary s1, evidence 9fd680e038736e73

Evidence (7)
  1. E1Prisma Data Platform reports operational. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Usage quota issue on free tier". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-01-09 13:43 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Prisma Postgres, Prisma Console, Prisma Accelerate. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-01-10 00:30 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Prisma Postgres, Prisma Console, Prisma Accelerate

No region Statuswall recognises is stated for this incident (place names and provider-specific codes are not converted). It is not assumed to be global.

Potential relevance

Prisma Data Platform is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Jan 9, 2026, 13:43 UTCVendor-reported startVendor time
  2. Jan 10, 2026, 00:30 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.