PingMyBrand · status
Is PingMyBrand up?
Live status straight from the same health check (/api/health) and external uptime monitor our own deploy pipeline uses — not a marketing page, the real signal. Deploys are hourly, zero-downtime, and auto-rollback on a failed post-deploy health check.
All systems operational
Status
Operational
checked just now
Uptime · 24h
no data yet
Uptime · 30d
no data yet
Last deploy
#83da7f4
13d 2h ago
Last incident
no monitoring data recorded yet
This page reads live, server-side, on every request (no cache) — the deployed commit (83da7f4) and process uptime are the actual running process, not a build-time snapshot.
Questions, answered
What does an 'Operational' vs. non-operational status mean here?
Operational means this same process answered the request AND its data store responded correctly, checked just now — never a fabricated 'all systems go.' Any other status means the process is up but the store was unreachable at check time.
How is PingMyBrand's uptime percentage calculated?
From the same external uptime monitor our own deploy pipeline uses, over rolling 24-hour and 30-day windows — the ratio of checks that returned healthy to total checks in that window, shown as 'no data yet' rather than a placeholder if no history exists yet. If the box itself is ever fully unreachable (the monitor can't even record a failed check), we conservatively reconstruct that gap as down time once it recovers, and the 'Last incident' line says so explicitly, rather than letting a total outage silently vanish from the history.
How often does PingMyBrand deploy, and how would I know if a deploy caused an incident?
Deploys are hourly, zero-downtime, and auto-rollback on a failed post-deploy health check. 'Last deploy' on this page is derived from the running process's own uptime, since a real deploy always kills and restarts the single Node process.
Does the PingMyBrand status page show business or customer data?
No — this public page exposes only up/down status, uptime percentage, last-deploy identity, and last-incident time. No account counts or per-account numbers are ever shown here; that stays behind the internal, secret-gated ops dashboard.