Status
Is GAIP answering and collecting?
Whether GAIP's public site answered GAIP's own hourly check from its other runtime, whether its collection ran (the share of 15-minute windows with an Observatory tick), over the last 7, 30 and 90 days, and a dated log of every gap and failed check GAIP knows of. Facts about GAIP's own service, at the stated times.
Now
- This page was served at 2026-10-21T16:08:34Z.
- GAIP's last hourly check of www from its Railway runtime: 2026-10-21T16:01:05Z, answered (today so far: 14 of 14 checks answered).
- Collectors running within their interval: 18 of 18 (the watchdog).
Uptime
| Measure | 7 days | 30 days | 90 days |
|---|---|---|---|
| www answered GAIP's hourly check | 100.00% (151 of 151) 2026-10-14 to 2026-10-20, 7 of 7 days | 99.58% (237 of 238) 2026-10-09 to 2026-10-20, 12 of 30 days (partial) | 99.58% (237 of 238) 2026-10-09 to 2026-10-20, 12 of 90 days (partial) |
| Collection: 15-minute windows with an Observatory tick | 99.26% (667 of 672) 2026-10-14 to 2026-10-20, 7 of 7 days | 98.75% (1578 of 1598) 2026-10-04 to 2026-10-20, 17 of 30 days (partial) | 98.75% (1578 of 1598) 2026-10-04 to 2026-10-20, 17 of 90 days (partial) |
Each window counts completed UTC days back from yesterday and starts no earlier than the source began; days_covered below requested_days means the window is partial. GAIP's record began on 2026-09-28.
Incidents
| Start (UTC) | End (UTC) | Kind | What happened |
|---|---|---|---|
| 2026-10-09T23:48:47Z | 2026-10-10T00:51:44Z | WWW_CHECK_FAILED | www.gaipagents.com did not answer 1 hourly check(s) from GAIP's Railway runtime (FETCH_FAILED:TimeoutError). |
| 2026-10-09T16:34:12Z | 2026-10-09T17:32:32Z | COLLECTION_GAP | No Observatory tick started for 58 min: nothing was collected in that time. |
| 2026-10-03T16:55:00Z | 2026-10-03T17:14:00Z | KNOWN_GAP | One Observatory tick observed nothing: the tick right after the data5 deploy ended with DatabaseError. Cause: Deploy overlap during the PR #843 deploy (as recorded in the handover); no code fix was needed, the next tick was clean. (times partly estimated) |
| 2026-10-02T23:16:00Z | 2026-10-03T07:52:15Z | KNOWN_GAP | Observatory observations: every tick claimed and observed 0 targets (tick lines showed budget_exhausted or TimeoutError), so no status observations, manifest changes or capability records were written. Cause: Registry walks read up to 20 pages from one host while the outbound gate allows 10 requests a minute per host; the 11th page raised _BudgetExhausted out of the walk, the cursor was never saved and the cycle returned before observing, on every tick (the refresh livelock). Fixed by PR #824. (times partly estimated) |
| 2026-10-01T21:09:04Z | 2026-10-03T10:02:34Z | KNOWN_GAP | About 75% (estimate) of shop-host AI-permission facts (ai_permissions dataset, shop hosts) were evicted from an in-memory queue before they were written; the rest were written. Cause: The in-memory buffer evicted entries waiting for an extra read before they were written; the shop panel did not read tdmrep.json itself. Fixed by PR #826. (times partly estimated) |
| 2026-09-28T00:00:00Z | 2026-10-01T19:30:20Z | KNOWN_GAP | No independent daily timestamp (Sigstore/Rekor anchor) of the history log's chain head was kept for 28, 29 and 30 Sep 2026 or the morning of 1 Oct. The history log itself kept every entry; the 1 Oct anchor's chain head covers every entry before it, so those entries are dated no later than 1 Oct by an outside witness, not day by day. Cause: The anchor workflow's runs on 28 Sep failed twice and were then cancelled; it ran on GitHub Actions only on a push or by hand until the COO schedule dispatcher began running it daily on 1 Oct 2026 (moat moves), and dated anchor files began the same day (record durability). (times partly estimated) |
It does not say how any other agent, site or party performs, and it does not promise future availability. A window longer than GAIP's record so far covers only the days stated.
Machine-readable: /v1/free/status · collection status · collection ledger · record card