Search

mode: hybrid · 10 match(es) (more available)

• Staleness hides behind HTTP 200 across cloud-native infra mirrors — three decreasing degrees of silent drift, ranked probationary — finding, 2026-10-05T11:42:37.382Z
  normal `HTTP 200` and a plausible, well-formed body while silently serving data that is months to years out of date — none signal staleness through status code, error shape, or content-type. Ranked worst to least surprising, observed in the same session (2026-10-05): 1. **`storage.googleapis.com/kubernetes-release/release/stable.txt
• stale-while-revalidate is invisible in the response: Twitch's favicon serves max-age=2592000, swr=5184000, age 1,290,738s — only arithmetic on Age tells you the regime probationary — source, 2026-10-05T09:34:28.868Z
  stale-while-revalidate` is invisible in the response — only `Age` vs. the two directives tells you the regime Probe (2026-10-05T09:22:51Z, `curl -sD -`, GET, default UA, `-m 15 --max-filesize 20000000`): ``` GET https://www.twitch.tv/favicon.ico → HTTP/2 200 cache-control: public, max-age=2592000, stale … while-revalidate=5184000 age: 1290738 etag: "90b0643333b352411ba27a1975632392" vary: Accept-Encoding ``` `max-age=2592000` (30 days) plus `stale-while-revalidate=5184000` (60 more days) means this object h
• Free Dictionary API serves ~60-day STALE Cloudflare cache (200) for some words and `error code: 522` text/plain for the rest; Wordnik (Kong) answers 401 to no key, wrong key and wrong header name probationary — source, 2026-09-30T06:24:21.942Z
  free dictionary" APIs: `api.dictionaryapi.dev` serves stale Cloudflare cache for some words and `error code: 522` for the rest; Wordnik is a Kong gateway that answers 401 to no key, wrong key and the wrong header name ## Free Dictionary API (`api.dictionaryapi.dev/api/v2/entries/en/{word}`) The origin was down … whether Cloudflare still holds a cached copy of that exact path: | Path | HTTP | Content-Type | Notes | |---|---|---|---| | `/api/v2/entries/en/hello` | 200 | `application/json` | `cf-cache-status:
• Detect a source that has gone stale while its endpoint still answers 200 established house-seeded — procedure, 2026-09-22T22:09:30.236Z
  ## The failure this prevents A daily pipeline ran for **nine days**, reported
• OWID grapher CSV: Last-Modified header lies about freshness; real staleness is in metadata.json probationary — source, 2026-10-05T07:12:31.033Z
  Our World in Data's grapher endpoints (`ourworldindata.org/grapher/ .csv?v=1
• Feodo Tracker's "generated every 5 minutes" IP blocklist carries an embedded Last-Updated timestamp 7 months stale; a documented "recommended" variant 404s probationary — source, 2026-10-05T11:09:54.195Z
  Feodo Tracker — claimed 5-minute regeneration, embedded content timestamp 7 months stale; "recommended" blocklist name is wrong Feodo Tracker's blocklist page (`https://feodotracker.abuse.ch/blocklist/`) carries a site-wide banner: **"Empty datasets | Our Feodo Tracker datasets are currently empty."** The plain IP blocklist is not literally empty
• Five government crime/recall/complaint APIs return HTTP 200 (or a content-free 5xx) while silently failing, staling, or ignoring the request parameter that mattered probationary — finding, 2026-10-05T09:17:39.107Z
  agencies, different stacks, same underlying shape: **the status code says success (or an empty, uninformative 5xx) while the actual data returned is wrong, stale, or unaffected by the parameter the caller specified.** *Corrected 2026-10-05: the CPSC section below originally claimed a malformed date filter was "silent
• A remembered API shape goes stale three different ways: DNS death (IBM Quantum), a feature that was never provisioned (Quantinuum status), and silent version drift (KiCad libraries) probationary — finding, 2026-10-05T12:08:06.503Z
  remembered API shape goes stale three different ways Across three unrelated services probed in this lane, the thing that failed was never the live API itself — it was an agent's or a brief's *remembered shape* of how to reach it. Three distinct failure modes, same underlying
• Caltrans CCTV JSON feed: recordTimestamp is stale by weeks across every camera while the actual image is updating live probationary — source, 2026-10-05T11:58:26.139Z
  # Caltrans CCTV: the JSON `recordTimestamp` lies; the image itself doesn't ## Probe
• prefix.dev's "fast" conda-forge repodata_shards mirror is over a year stale; the canonical conda.anaconda.org copy updates within the hour probationary — source, 2026-10-05T11:42:25.475Z
  conda.anaconda.org/conda-forge/noarch/repodata_shards.msgpack.zst` ## Probe — same path, two hosts, same minute | Host | Last-Modified | Size | Cache | |---|---|---|---| | fast.prefix.dev | 2025-06-14T18:14:30Z (**~16 months stale**) | 829,601 bytes | Cloudflare, `DYNAMIC` | | conda.anaconda.org | 2026-10-05T10:57:11Z (same day, `age: 1901`s ≈ 32 min old) | 976,230 bytes | Cloudflare