PProdView
Sign in Start free trial
System status
RSS feed Subscribe by email Slack integration Webhook Status API
Dashboard app.prodview.app · UI
99.998%
REST API api.prodview.app/v1
99.995%
Ingestion pipeline agent event intake
99.999%
Webhooks outbound event delivery
99.974%
Agent updates dl.prodview.app
99.999%
SAML / SSO auth.prodview.app
99.991%
EU region eu-1 (Frankfurt)
99.997%
APAC region ap-1 (Singapore)
99.994%
99.992%
90-day uptime
all components, weighted by traffic
228ms
api p99 · global
↓ 12ms vs last quarter
99.99%
enterprise SLA
credits if missed
3
incidents · 90d
0 customer-impacting in 28d

Incident history

All times UTC · last 14 days shown
Today · May 16, 2026
No incidents reported.
May 14, 2026

Scheduled maintenance — eu-1 ingestion failover drill

maintenance
02:00 UTC — 02:14 UTC · 14m · no customer impact
Quarterly failover drill from eu-1a to eu-1b. Ingestion paused for 14 minutes; agent events buffered locally per design and replayed on resume. Zero data loss.
02:14 UTCresolvedDrill complete. Failback to primary at 02:14. All buffered events drained within 90 seconds.
02:00 UTCscheduledInitiating planned failover of eu-1 ingestion to standby region.
May 8, 2026

Webhook delivery latency · upstream provider

minor
11:43 UTC — 12:08 UTC · 25m · partial impact
A degradation at our outbound HTTP provider caused webhook delivery latency to rise from ~120ms p99 to ~4s p99 for a subset of tenants in us-east. Retries succeeded; no events lost. We've added a secondary egress provider as a follow-up.
12:08 UTCresolvedUpstream provider recovered. Backfilled deliveries complete.
11:55 UTCmonitoringLatency back to normal. Watching for re-occurrence.
11:48 UTCidentifiedRoot cause is an upstream HTTP egress provider. No data loss.
11:43 UTCinvestigatingAlerted on webhook p99 latency > 2s for >3 minutes.
May 1-7, 2026
No incidents reported.
Apr 26, 2026

ap-1 dashboard latency · regional

minor
09:22 UTC — 10:11 UTC · 49m · ap-1 only
Dashboard p95 load time rose to ~6s for ap-1 customers due to a deploy that didn't pre-warm the regional cache. Mitigated by manually warming cache; root cause fixed in 0.2.1 — pre-warm is now a release gate.
10:11 UTCresolvedCache warmed. Latency back to baseline (~280ms p95).
09:38 UTCidentifiedRecent deploy invalidated regional cache. Manually warming.
09:22 UTCinvestigatingap-1 dashboard p95 above threshold.