stabletravel.dev/api/flightaware/airports/delays
1.Catalog declaration
| Resource URL | https://stabletravel.dev/api/flightaware/airports/delays |
| Source | cdp_bazaar |
| Declared method | GET |
| Network | eip155:8453 |
| Receiving address | 0xdd257723b86b4947483905cdacbbbc70facf2ec0 |
| Declared price (base units) | 100000 |
| Catalog status | active |
| First seen / last seen | 2026-08-23 01:18 UTC / 2026-09-29 01:03 UTC |
| Catalog-reported calls / payers (30d) | 1 / 1 |
2.Probe history
| Probed at | Method | Verdict | HTTP | Latency | Reason |
|---|---|---|---|---|---|
| 2026-09-29 04:40 UTC | GET | pass | 402 | 217 ms | — |
| 2026-09-28 13:40 UTC | GET | pass | 402 | 503 ms | — |
| 2026-09-27 16:40 UTC | GET | pass | 402 | 204 ms | — |
| 2026-09-26 22:40 UTC | GET | pass | 402 | 133 ms | — |
| 2026-09-26 04:40 UTC | GET | pass | 402 | 402 ms | — |
| 2026-09-25 13:40 UTC | GET | pass | 402 | 368 ms | — |
| 2026-09-24 16:40 UTC | GET | pass | 402 | 44 ms | — |
| 2026-09-23 22:40 UTC | GET | pass | 402 | 116 ms | — |
| 2026-09-23 04:40 UTC | GET | pass | 402 | 163 ms | — |
| 2026-09-22 13:40 UTC | GET | pass | 402 | 58 ms | — |
| 2026-09-21 22:40 UTC | GET | pass | 402 | 145 ms | — |
| 2026-09-21 04:40 UTC | GET | pass | 402 | 162 ms | — |
| 2026-09-20 13:40 UTC | GET | pass | 402 | 180 ms | — |
| 2026-09-19 16:40 UTC | GET | pass | 402 | 152 ms | — |
| 2026-09-18 22:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-18 04:40 UTC | GET | pass | 402 | 300 ms | — |
| 2026-09-17 16:40 UTC | GET | pass | 402 | 153 ms | — |
| 2026-09-16 22:40 UTC | GET | pass | 402 | 189 ms | — |
| 2026-09-15 22:40 UTC | GET | pass | 402 | 40 ms | — |
| 2026-09-15 13:40 UTC | GET | pass | 402 | 150 ms | — |
| 2026-09-14 16:40 UTC | GET | pass | 402 | 287 ms | — |
| 2026-09-14 04:40 UTC | GET | pass | 402 | 70 ms | — |
| 2026-09-13 13:40 UTC | GET | pass | 402 | 41 ms | — |
| 2026-09-12 22:40 UTC | GET | pass | 402 | 103 ms | — |
| 2026-09-12 04:40 UTC | GET | pass | 402 | 88 ms | — |
| 2026-09-11 16:40 UTC | GET | pass | 402 | 80 ms | — |
| 2026-09-11 04:40 UTC | GET | pass | 402 | 269 ms | — |
| 2026-09-10 14:40 UTC | GET | pass | 402 | 67 ms | — |
| 2026-09-09 23:40 UTC | GET | pass | 402 | 121 ms | — |
| 2026-09-09 14:40 UTC | GET | pass | 402 | 105 ms | — |
3.L1 — real purchases
1 of 1 paid attempts settled with a receipt, and 1 of those also returned a 2xx response (delivered). Each settled row carries its on-chain transaction hash — the receipt is the evidence. A settled row reads as nonce-bound when the on-chain re-read also matched the one-time signature nonce we generated for that purchase, and amount + payee when it matched amount, payee, asset and chain with no nonce on record — the binding shipped on 2026-09-04, so earlier rows carry the weaker evidence and keep their label rather than being demoted (methodology). settled is the transfer we confirmed on-chain; delivered is the response arriving. A settled row whose paid request answered 5xx counts as settled and not as delivered — definitions.
Terms in this table
settled (nonce-bound)- vet402 confirmed the USDC transfer on-chain, and the on-chain re-read also matched the one-time nonce vet402 signed for that purchase.
L2 match- the response had the fields the listing's output schema declares.
Whose side- the same words as the seller page: seller's side only after failures on two different days (UTC), marked “under re-check”; vet402's side; or not sorted (the rules).
| Attempted at | Result | HTTP | Receipt (tx) | Latency |
|---|---|---|---|---|
| 09-08 12:082026-09-08 12:08 UTC | settled (nonce-bound) | 200 | 0x22f19298…89c1 | 1792 ms |
| 100000 units (≈ $0.10 USDC) · L2 matchWhose side: no failure (delivered) | ||||
Embed this record
Run this endpoint? Show the settle-through record vet402 measured — the badge reads 1/1 settled · 1 delivered and updates as the record grows. It carries the host it is about and the date it was last measured, so a saved copy cannot pass itself off as current. It states a measurement, not a rating.
[](https://vet402.com/observatory/e/a9de403e-3bf4-4fdb-b2d0-b079af707c51)4.Catalog listing events
No listing changes observed.
unverified is not a failure; a fail is published only after two consecutive failing probes. Definitions: methodology.
5.Dispute this record
Think a measurement above is wrong? Say which probe or purchase and what you observed instead. One person reads it and replies. The record is never deleted on dispute: if it was wrong, the correction is published with the same weight; if it was right, it stands. Operators who control the receiving address can also sign a dispute via POST /api/v1/observatory/disputes (API reference), which re-measures through the normal publication gate.
About the purchase at 2026-09-08T12:08:30Z (UTC). The form starts with that time; add what you saw instead.