See how health will be reported.
This page is a product preview built with sample data. It is not connected to OnArrival production monitoring and must not be used to assess current availability.
- Example surfaces
- Sample 90-day figure
- Monitoring connection
By API surface.
Illustrative data model. Fixed sample snapshot .
Upstream dependencies.
An example of the supplier dimension that can sit behind each surface: bedbanks, GDS/NDC, PSPs and operators. Names and states below are illustrative, not current supplier health.
This sample shows how an affected operator could be isolated while healthy supply remains available. It demonstrates the intended reporting pattern, not a current Buses incident.
How targets can be explained.
This sample shows how tier targets, outage definitions, and credit rules can sit beside service health. It is explanatory website copy, not a service commitment; the signed MSA governs each customer.
Targets and credit schedules are set in your order form or MSA; the definitions above are the standard gloss and govern unless your contract says otherwise. The blended 99.95% figure on this page is the 90-day mean across all 8 surfaces. Your enforceable number is per product, measured only on the surfaces you actually call.
A postmortem model.
Illustrative incidents and maintenance windows show the level of detail intended for future reporting: blast radius, timeline, and the fix. These are sample records, not a production incident log.
Choose your channel.
Preview the notification routes intended for production. Email opens a draft, RSS is a sample feed, and webhook configuration lives in the developer documentation.
