Status and uptime
Last updated April 25, 2026
VeriRFP publishes service availability and incident communications through a dedicated status surface. Use this page to track the current source of truth and escalation channels.
The goal is to keep customers, procurement reviewers, and internal support aligned on the same incident signal. A single status page avoids scattered updates and gives buyers a stable reference point during review.
During diligence, uptime questions usually sit next to requests for the security overview, subprocessor inventory, and privacy workflow. Publishing those operating references as linked pages makes it easier for procurement teams to validate how service health, escalation, and contractual handling fit together.
Current status
Live probes run on each page load against the web app, MCP API, and worker health endpoints.
Overall system state: Operational · last checked May 29, 2026, 12:47 PM EDT.
No customer-impacting incidents reported in the last 90 days.
Status timestamps are shown in America/New_York and automatically display EDT or EST based on the date.
- Web app: operational — Healthy (200) · 32ms
- MCP API: operational — Healthy (200) · 35ms
- Worker: operational — Healthy (200) · 55ms
You are currently viewing the live status page.
Incident update cadence
- Initial notice within 30 minutes of confirmed customer impact.
- Progress updates at least every 60 minutes while impact remains active.
- Final summary with root-cause and corrective actions after resolution.
Maintenance windows
- Planned maintenance announcements are posted at least 24 hours in advance.
- Emergency maintenance notices are posted as soon as risk is confirmed.
- Customer escalation path during incidents: admin@verirfp.com.
Teams evaluating operational maturity usually pair planned-maintenance policy with the live status feed, support model, and security reporting commitments before they sign off on a vendor.
How this status surface fits the trust workflow
Status updates are one part of the broader buyer-trust package. Enterprise customers use this page to verify live availability expectations, then pair it with the security reporting policy, privacy workflow, and subprocessor inventory during diligence reviews. Keeping these operational references linked reduces back-and-forth when a procurement team wants the full picture in one pass.
- Incident notices explain active customer impact and update cadence.
- Security reporting explains how researchers and customers should submit new findings.
- Support and privacy pages document the operational escalation paths used once communication is required.