Vendor Status Watch

← all vendors

Prismic status history

Current state: operational — “All Systems Operational” per https://status.prismic.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

1incidents, last 30 days
2incidents, last 90 days
18incidents on record
Incidents per week, last 12 weeks:

How long do Prismic incidents last?

29 minmedian incident duration17 measured
2.4 h90th percentile1 in 10 ran longer
20 minmedian, major/critical only13 incidents

From 17 incidents with a vendor-posted start and resolve time. Longest on record: [Page Builder] Issue with oEmbed feature — 4.4 h (2026-01-07 10:17 UTC). Excluded, never estimated: 1 resolved before started (vendor data error). Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (18)

StartedIncidentStatusImpactDuration
2026-09-14 09:14 UTCElevated error rate on the API and Editorresolvedcritical8 min
2026-06-29 18:52 UTCError on new document publicationresolvedminor18 min
2026-05-19 09:14 UTCElevate errors on Writing Roomresolvedcritical13 min
2026-04-22 18:45 UTCPrismic.io is currently experiencing issues with authenticationresolvedcritical10 min
2026-04-13 17:00 UTCError accessing Prismicresolvedcritical13 min
2026-04-07 16:26 UTCIssue with Media Libraryresolvedmajor14 min
2026-04-03 10:47 UTCNew users are encountering issues when creating repositoriesresolvedmajor1 h 01 min
2026-03-20 15:37 UTCIssue with Media Libraryresolvedmajor43 min
2026-03-02 15:44 UTCIssue with Media Libraryresolvedmajor20 min
2026-02-18 14:51 UTCIssue with Media Libraryresolvedmajor16 min
2026-02-12 14:19 UTCUnable to sign upresolvednone29 min
2026-02-11 10:38 UTCService Disruptionresolvedcritical
2026-01-07 10:17 UTC[Page Builder] Issue with oEmbed feature resolvedminor4 h 23 min
2025-11-18 12:13 UTCReal Time Collaboration Unavailableresolvedminor1 h 04 min
2025-11-07 13:25 UTCAuthentication via SSO and Githubresolvedmajor1 h 00 min
2025-10-20 12:49 UTCIncreased Errors on Content APIresolvedmajor57 min
2025-10-20 11:26 UTCWebhook Triggers & Integration Fieldsresolvedcritical2 h 21 min
2025-10-20 07:30 UTCIncreased Error Rates and Latenciesresolvedcritical2 h 31 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Prismic with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "prismic"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}