Status
TravelCore API status
The real state of each service, including the ones that do not exist yet.
What is the TravelCore service status?
The status page lists each service and its current state. It deliberately publishes no uptime percentage: TravelCore is pre-production, and an uptime figure measured against no real traffic is a decoration rather than a commitment. Real numbers get published when there is real production load to measure them against.
Platform
Authentication
OAuth 2.0 token issuance.
API gateway
Routing, rate limiting, request validation.
Webhooks
Delivery with retry and replay.
Hotels
Hotel search
Sandbox and design-partner traffic.
Hotel booking
Sandbox and design-partner traffic.
Hotel mapping pipeline
Batch mapping runs and review queue.
Flights
Flight search
Specified, not implemented.
Flight booking
Specified, not implemented.
Ground
Transfers
Specified, not implemented.
Experiences
Activities
Specified, not implemented.
Payments
Payments
No provider contracted yet.
Historical uptime
Not published yet, and here is why
An uptime chart is only worth something if it was measured against real production traffic. We have not carried enough of it to draw one honestly, and a fabricated 99.99% would tell you nothing except that we are willing to fabricate.
What we will publish
Monthly uptime per service, measured from the gateway, from the first month of production traffic.
What we will not publish
A number chosen because it looks like the number everybody else displays.
What you can ask for
A written service level in an enterprise agreement, with defined remedies rather than a badge.