Status
No published status page yet, and no uptime figure.
GetYourGuide is live through this service. A live status page is not yet published and no measured uptime figure is published. Until it is, this page states what will be watched and what it depends on.
Last updated 24 October 2026.
Current state
- GetYourGuideLive
Certified by GetYourGuide on 20 October 2026 (Supplier API live test passed); first supplier connected through self-mapping on 21 October 2026.
Live through the service. Last checked 2026-10-24
- ViatorPlanned
Not started. Viator requires five active engaged operators before development may begin.
Not live. Last checked 2026-08-28
Planned monitoring
What will be watched.
- 01
Each inbound channel endpoint
Availability, reservation, reservation cancellation, booking and booking cancellation, measured separately. Each carries its own response budget, so a single combined figure would hide the call that is failing.
- 02
The outbound availability notification
The call this service makes to GetYourGuide when availability changes. It is the one direction where a failure is invisible to the channel, which makes it the one most worth watching.
- 03
The routing decision itself
Whether a product identifier resolves to the marketplace that owns it. A wrong answer here would be worse than an outage, because it would be quiet.
- 04
Each marketplace backend
Reachability and response time from the front door to the system that holds the calendar, measured from where the calls are actually made rather than from a monitoring service elsewhere.
Live status is not yet published. These are the checks it will be built from.
Dependencies
What this service depends on.
| Dependency | What relies on it | Effect if it is unavailable |
|---|---|---|
| The Greek Local backend | Availability and bookings for every product in Greece | Calls for Greek products fail while it is unavailable. Cypriot products are unaffected, because the two are never answered by the same system. |
| Cyprus Bucket List backend | Availability and bookings for every product in Cyprus | Calls for Cypriot products fail while it is unavailable. Greek products are unaffected. |
| Hosting platform | Everything. The front door at api.rezroute.com runs on it | No channel call is answered. |
| DNS | Resolution of api.rezroute.com for both channels | Channels cannot reach the service at all. |
GetYourGuide and Viator are not listed as dependencies. They call this service rather than the other way round, apart from the outbound availability notification, and an incident inside a channel is reported by that channel. Restating a channel incident here would claim a visibility this service does not have.
When it is live
What will be published, and how it will be defined.
- Monthly availability per channel, measured against that channel definition. For GetYourGuide that means a call not answered within 15 seconds counts as unavailable.
- Monthly error rate per endpoint, set against the ceilings published on the reliability page, so the figure can be read as a pass or a fail rather than as a number.
- An incident log: start time, end time, which products and which marketplace were affected, and the cause once it is known rather than a placeholder for it.
- The measurement window and definition beside every figure, because an uptime percentage without its definition is decoration.
The targets those measurements will be read against are published on the reliability page, and changes that affect connectivity are announced on the changelog before they take effect.