Field notes / 01
How we report reliability.
A clear account of the checks behind this status page, the meaning of each condition, and the limits of the history we show.
Reporting principle
Only recorded evidence informs the public timeline.
A missing check remains unrecorded. It is never counted as successful uptime.
01 / Methodology
What we monitor
The status page follows the steps people take with VaahanSafe, so a service condition has a clear customer meaning.
Website & Documentation
Public safety portal, hardware specifications, and replacement ordering.
Customer App
Vehicle profile management, emergency contact setup, and digital identity access.
Purchase & Payments
Authoritative order processing, Razorpay gateway checkout, and fulfillment tracking.
Retail Activation
Secure retail sticker claim, scratch PIN verification, and vehicle binding.
Vehicle QR Access
Instant roadside bystander scan resolution, safety profile exposure, and relay dispatch.
Emergency Notifications
Multi-channel SMS, WhatsApp, and call relay alerts during roadside vehicle incidents.
02 / Methodology
How conditions are named
A condition describes the available evidence for a capability. Unknown is shown when that evidence is missing.
The configured public check is responding successfully.
A recorded check cannot confirm normal operation, such as overdue processing or delivery receipts.
Some of the capability is unavailable or failing.
A primary capability is unavailable.
A planned service window has been published.
A reliable check is unavailable; no healthy state is inferred.
03 / Methodology
How the 90-day history works
Each mark represents one calendar day in India Standard Time. The history uses recorded Cloudflare checks, not estimated uptime.
Green
Successful check recorded
Amber / red
Degraded or failed check recorded
Grey
No check recorded that day
Observed success is successful checks divided by completed recorded checks. It does not describe unobserved time, and it should not be read as a 90-day service-level guarantee.
04 / Methodology
Sources and timing
Payments and notifications use provider access and processing checks recorded every ten minutes. Samples older than 25 minutes become unknown. These checks do not certify an individual payment or message delivery. The infrastructure panel reports the database heartbeat separately.
Direct database read
A server-side request checks whether Supabase responds now. This is separate from the scheduled run history.
Cloudflare scheduled run
The Worker runs every 10 minutes. A successful database heartbeat is considered overdue after 25 minutes without a new record.
Public service checks are stored as separate records. Capabilities without a configured check show an unknown condition. Published incident updates are reported independently of these measurements.