FeaturesWeb VitalsDevelopersPricingDocs
Sign inStart monitoring
System status

All systems
operational.

Real-time status for every PagePulse component, plus a 60-day incident history. Subscribe for email updates when a component changes state.

All systems operational

Updated just now · 7/4/2026, 5:37:02 AM

Components

RUM ingestion API
Beacon collection from browser SDK
Operational
Web Vitals pipeline
LCP, INP, CLS, FCP, TTFB processing
Operational
Dashboard & API
app.pagepulse.dev and REST API
Operational
Deployment diffing
Before/after release comparison engine
Operational
Webhooks delivery
Outbound event delivery and retries
Operational
Alert routing
Slack, email, Linear, Jira delivery
Operational
Report generation
Weekly PDF and CSV report builder
Operational
US East ingestion
Virginia, Oregon, Canada
Operational
EU ingestion
Frankfurt, London, Amsterdam
Operational
Asia Pacific ingestion
Tokyo, Singapore, Sydney
Operational

Incident history · last 60 days

Minor incident·Duration: 47 minutesResolved

Elevated webhook delivery latency in EU region

Webhook deliveries from the Frankfurt region experienced an additional 2-3 second latency between 14:12 and 14:59 UTC. No webhooks were dropped. Root cause was a Redis failover that triggered additional retry overhead.

14:12 UTCWe are investigating reports of elevated webhook delivery latency in the EU region.
14:38 UTCIdentified the cause as a Redis failover in the Frankfurt region. Implementing mitigation.
14:59 UTCWebhook delivery latency has returned to normal. We will monitor for the next hour.
16:00 UTCIncident resolved. No further action required.
Maintenance·Duration: 12 minutesResolved

Scheduled maintenance: dashboard database upgrade

We upgraded the dashboard database to a larger instance class to support the growing number of projects on Scale plans. The dashboard was briefly read-only during the upgrade window.

02:00 UTCScheduled maintenance window begins. Dashboard is now read-only.
02:12 UTCDatabase upgrade complete. Dashboard is back to full read/write.
Minor incident·Duration: 1 hour 14 minutesResolved

RUM ingestion delayed for Vercel deployments

RUM samples from Vercel-hosted customer sites were delayed by up to 90 seconds between 09:18 and 10:32 UTC due to a backpressure issue in our edge ingestion layer. No data was lost; all samples were eventually processed.

09:18 UTCWe are investigating delayed RUM ingestion from Vercel deployments.
09:45 UTCRoot cause identified as backpressure in the edge ingestion layer. Scaling capacity.
10:32 UTCIngestion backlog cleared. All RUM samples have been processed.

Subscribe to status updates

Get an email the moment a component changes state.