Tripdesk

Status

Our own desks and every catalogued server, from the scheduled probe. A probe connects, lists tools, and runs one real call whose answer we check, because reachable and working are not the same thing.

Last run 2026-09-29 06:00 UTC.

Our desks

DeskStatusProtocolLatencyDetail
catalogue up — — ok
directory up — — ok
egf up 2025-06-18 399 ms ok
egf-desk up — — ok
router up — — ok
sos up — — ok
utility up — — ok

Catalogued servers

ServerStatusScoreToolsGolden callDetail
amadeus-community unknown 0/5 — — not probeable: no public endpoint
apaleo unknown 0/5 — — not probeable: no public endpoint
booking-com unknown 0/5 — — not probeable: no public endpoint
deutsche-bahn-rail unknown 0/5 — — not probeable: no public endpoint
duffel-flights unknown 0/5 — — not probeable: no public endpoint
expedia-b2b unknown 0/5 — — not probeable: no public endpoint
flightradar24 unknown 0/5 — — not probeable: no public endpoint
google-maps-grounding unknown 0/5 — — not probeable: no public endpoint
ivisa unknown 0/5 — — not probeable: no public endpoint
kiwi-com up 5/5 2 pass ok
peek-activities unknown 0/5 — — not probeable: no public endpoint
sabre-agentic unknown 0/5 — — not probeable: no public endpoint
tourradar unknown 0/5 — — not probeable: no public endpoint
travelport-tripservices unknown 0/5 — — not probeable: no public endpoint
treppy-insurance unknown 0/5 — — not probeable: no public endpoint

How the score is read

0Unreachable, or refused the connection.
1Connected, but the tool list failed or was empty.
2Tool list fine, the golden call errored.
3The call returned, but the answer was not what it should be.
4Correct, but slow or with undocumented tools.
5Correct, prompt, documented.

One failed check is usually the network, so status stays up. Two consecutive is degraded. Four, about a day, is down and drops out of catalogue search. unknown means partner-gated with no public endpoint: we cannot check it, which is a different claim from saying it is broken.