The public BridgeDb identifier-mapping API at webservice.bridgedb.org, also reachable as swagger.bridgedb.org and bridgedb.cloud.vhp4safety.nl.
Last 90 days
No data yet.
What we check
The Swagger UI landing page of webservice.bridgedb.org loads within five seconds, through public DNS and on each node.
The same service answers under the swagger.bridgedb.org name.
The same service answers under the bridgedb.cloud.vhp4safety.nl name.
Both nodes serve a trusted certificate that covers all three BridgeDb host names, with time to spare.
Plain http on each of the three names redirects permanently to https on the same name.
webservice.bridgedb.org resolves to a cluster node (tgx1 normally) and two public resolvers agree.
swagger.bridgedb.org resolves to a cluster node (tgx1 normally).
bridgedb.cloud.vhp4safety.nl resolves to a cluster node (tgx1 normally).
The service runs the expected BridgeDb 3.0.31 and webservice 2.1.9, the same build behind all three names, and its API description reports the same version.
The service lists its loaded organisms (an empty list is the database-driver failure mode), including human, mouse, rat and potato.
An unknown path still answers with the documented 'Unrecognized query' page; the body checks of this target rely on that behaviour.
