Odile Gate

Gate status

Operational. Last recorded HTTP 200: 2026-11-20T09:50:00.761Z. Last 30 days: 99.55% of expected 5-minute slots have one.

Our monitor, on a DigitalOcean server in New York (nyc1), is scheduled to send one GET through Gate to its built-in Demo Desk on a dedicated project every 5 minutes (from the slot at 2026-11-19T15:10:00.000Z). Gate records each call it answers, and this page counts the expected 5-minute slots (from the first 5-minute UTC slot after the status project was created to the newest slot whose check has had a minute to land) with a recorded HTTP 200. A slot without one means no HTTP 200 was recorded in it; it does not say why. This page is served by Gate itself, so it is down when Gate is: for an independent signal, point your own monitor at https://gate.odilelabs.com/health.

UTC daySlots with an HTTP 200Share
2026-11-20118 of 11999.15%
2026-11-19106 of 106100.00%

Measured latency

Measured 2026-11-19: the same call sent direct and through Gate, 300 pairs on kept-alive HTTPS connections in alternating order, to https://api.odilelabs.com/health (a Cloudflare Worker). From a DigitalOcean server in New York (nyc1), compared with direct calls, latency through Gate was 81.5 ms higher at p50, 102.7 ms higher at p95 and 122.9 ms higher at p99 (each figure is the difference between the two paths' percentiles: direct 13.7, 21.5 and 38.9 ms; through Gate 95.2, 124.2 and 161.8 ms). From a home connection in Florida, the median through Gate was 128.5 ms higher (191.3 against 62.8 ms). Also from New York, Gate's /health answered in 15.8 ms at p50 and a Demo Desk call, answered inside Gate, in 51.2 ms. A new project's first call took 0.75 s from New York and 2.52 s from Florida, end to end. Your numbers depend on where your API is and where your project's Durable Object runs (Cloudflare places it near where it is first used).

How Gate behaves when it cannot answer: fail mode. JSON: add ?format=json.