Service status and incident communication
How WPCentrify reports service health and communicates during incidents. During early access this page sets the expectations we hold ourselves to, at a level you can actually act on.
Report health at the level customers can act on
Vague green dots do not help you decide what to do. Status is reported against the workflows you depend on.
Monitoring and alerting
Whether uptime checks and alerts are running normally across regions.
Update and rollback pipeline
Whether safe updates, verification and automatic rollback are operating.
Backups and restore
Whether scheduled backups are completing and restores are available.
Dashboard and reporting
Whether the portfolio dashboard and client reporting are responsive.
Investigating, identified, monitoring, resolved
Plain, consistent incident stages so you always know where things stand.
Investigating
We have seen a signal and are confirming scope and cause.
Identified
We know the cause and are applying a fix.
Monitoring
The fix is in place and we are watching to confirm recovery.
Resolved
Service is confirmed healthy, with a short note on what happened.
Frequently asked questions
During early access, incident communication runs through email and direct contact while the public status page is built. This page defines how that communication works.
Use the contact page for product or website issues, and the responsible disclosure route for anything security related. Both reach the team directly.