status.platformdtc.com publishes the live operational state of the surfaces we probe — storefronts, checkout, the merchant dashboard, the Core API, notifications and these docs — with response-time metrics, a rolling uptime record and the full incident history.
Not to be confused with Endpoint Status, which documents which individual API endpoints are verified, gated or known-broken. This page is about whether the platform is up right now.

​
What is monitored

Background Jobs & Fulfillment and Analytics & Reporting are not probed yet. They are listed because they are real surfaces, but no check runs against them, so they carry no response-time samples and no uptime figure. Do not read their state as evidence that they are healthy — an outage in either one would not show up here. Everything else in the table above is measured.
Each probed component reports one of four states — Operational, Degraded Performance, Partial Outage or Major Outage — plus its current p50 and p95 response time and the tail ratio between them.

​
Why response times are published, not just up/down

A service can be up and still be unusable. The number that matters is the tail: on 2026-07-30 an internal investigation found individual API requests taking up to 9.9 seconds while the median stayed at a perfectly healthy 0.31s. Every average-based dashboard was green for weeks. So the status page publishes p50, p95 and the p95/p50 ratio per component, and alerts on the tail rather than the average. If you think a surface is slow, you can cite the same figure we alert on instead of trading anecdotes.

​
Subscribe to updates

Subscribe a Slack channel
Subscribe your own endpoint
The secret is returned once, at creation. Store it — there is no endpoint that reads it back. You need it to verify signatures.
Feeds and webhooks emit one entry per incident update, not one per incident. A subscriber that only heard about an incident opening would never learn it had been resolved.

​
JSON API

The status API implements the Atlassian Statuspage v2 contract, so any existing Statuspage widget, uptime aggregator or integration works against it without an adapter. No authentication, CORS open to all origins, cached 30 seconds at the edge.
Is anything wrong right now?
Response
indicator is one of none, minor, major or critical.

​
Component metrics (extension)

Every component in summary.json and components.json carries a metrics object. This is an addition to the Statuspage schema — additive, so no standard consumer breaks.
p99_ms and max_ms are reported for completeness but no alert uses them — with nearest-rank percentiles p99 equals max at any sample count below 100, so a p99 rule is a worst-single-request rule in disguise.

​
Uptime history (extension)

days_measured is returned alongside uptime_pct on purpose, and it is the number to read first. window_days is the window you asked for; days_measured is how much of it we actually observed, and it is currently well short of 90. A window we have only partly observed reports the days it covers rather than implying 90 days of evidence we do not have. Components that are not probed appear in neither map.

​
Verifying webhook signatures

Every webhook delivery carries an HMAC-SHA256 of the raw request body, using the same scheme as PlatformDTC’s platform webhooks:
Compute the HMAC over the raw bytes, before any JSON parsing — re-serializing the payload changes the bytes and the signature will not match.

​
Incident lifecycle

An incident moves through investigating → identified → monitoring → resolved, and carries an independent impact of minor, major or critical. Status is how far along the response is; impact is how bad it is. Every update is retained, so the record shows what was known when.

​
How the page stays up during an outage

The status page runs on Cloudflare’s edge with no origin server. It shares no infrastructure with the systems it reports on, and its checks run from outside our network — so it keeps answering when the platform does not. That is verified deliberately, by cutting off every monitored service and confirming the page still loads and correctly reports a major outage.
Individual stores. Problems affecting a small number of specific stores may not appear here — the page reports platform-wide state, not per-store health. If your store is affected while this page shows all systems operational, contact support rather than assuming it is you.