Status

Operational · synthetic check

Gateway operational.

No customer traffic in the last 24 hours. A synthetic check calls the production Gateway every 10 minutes; the latest passed at 17:50 UTC.

Last checked 9 Nov 2026, 17:57 UTC

Services

What each service’s state rests on.

  • GatewayMeasured from real requests. None arrived in the last 24 hours. A synthetic check calls the production Gateway every 10 minutes; the latest passed at 17:50 UTC.Operational
  • ConsoleServed by the same deployment as this page. No independent check runs against it.Not monitored
  • DocumentationStatic pages from the same deployment. No independent check runs against it.Not monitored
  • Marketing siteYou are reading it. Its being up is not evidence about anything else here.Not monitored
Last 30 days

Day by day, from real requests.

A quiet day shows as no data, and a 401 from a bad key is never counted against us.

11 Oct3/3 served · 1 client error
12 Oct6/6 served · 1 client error
13 OctNo traffic
14 OctNo traffic
15 Oct42/44 served · 2 failed · 2 client errors
16 OctNo traffic
17 OctNo traffic
18 OctNo traffic
19 OctNo traffic
20 OctNo traffic
21 Oct60/70 served · 10 failed · 4 client errors
22 Oct12/12 served · 1 client error
23 Oct2/2 served
24 Oct13/13 served
25 OctNo traffic
26 OctNo traffic
27 OctNo traffic
28 OctNo traffic
29 OctNo traffic
30 OctNo traffic
31 Oct81/85 served · 4 failed · 1 client error
1 NovNo traffic
2 Nov1/2 served · 1 failed · 1 client error
3 NovNo traffic
4 NovNo traffic
5 NovNo traffic
6 Nov11/11 served · 5 client errors
7 Nov2/2 served · 2 client errors
8 NovNo traffic
9 NovNo traffic
11 OctAll servedSome failedMostly failedNo traffic9 Nov
250requests in the window
93.2%served, with 17 service-affecting failures
11 of 30days had traffic

A further 18 were rejected as a client error, which is not counted against uptime.

Measurements

Latency, synthetic checks and incidents, as measured.

Latencyp50 and p95, last 30 days
3,926 msp5021,162 msp95

Over 215 successful requests, end to end including the provider: what the caller waited, not what the Gateway added.

Synthetic checksLast 24 hours
  • GET /modelsPassed 9 Nov 2026, 17:50 UTC · 144/144 passed (100%) · p50 141 ms · no failures
  • POST /route-previewPassed 9 Nov 2026, 17:50 UTC · 144/144 passed (100%) · p50 144 ms · no failures
Incident historyLast 30 days
  1. Info

    Provider errors on search

    1 of 1 request failed · search · provider · single request

  2. Disruption

    Provider errors on search

    4 of 70 requests failed · search · provider · until 31 Oct 2026, 04:28 UTC

  3. Disruption

    Provider errors on search

    5 of 11 requests failed · search · provider · until 21 Oct 2026, 04:33 UTC

  4. Disruption

    Provider errors on search

    5 of 17 requests failed · search · provider · until 21 Oct 2026, 03:56 UTC

  5. Disruption

    Provider errors on search

    2 of 2 requests failed · search · provider · until 15 Oct 2026, 04:09 UTC

Measured, never written by hand.

Incidents are derived from clusters of failures in the request trace, and nothing here is retro-edited. The page is rebuilt at most once a minute.