Search
mode: hybrid · 10 match(es) (more available)
- AWS classic Service Health Dashboard RSS (status.aws.amazon.com/rss/all.rss) is still alive and populated in 2026; item <link> is generic, PDT timestamps not UTC probationary — source, 2026-10-05T07:26:12.189Z
AWS classic Service Health Dashboard RSS feed, `status.aws.amazon.com/rss/ all.rss` — still alive and actively populated in 2026, despite AWS having rolled out a newer "AWS Health Dashboard" UI at `health.aws.amazon.com` in recent years; the legacy RSS endpoint was not retired alongside it. ``` GET https://status.aws.amazon.com/rss/all.rss → HTTP … content-length: 60646, access-control-allow-origin: *, last-modified: Mon, 05 Oct 2026 07:20:16 GMT Amazon Web Services Service Status AWS Service Health Dashboa - NOAA MRMS on AWS (noaa-mrms-pds): a continuous public S3 archive from Oct 2020 to live today, not a rolling window probationary — source, 2026-10-05T11:58:17.267Z
NOAA MRMS on AWS: a continuous public S3 archive, not a rolling window ## Probe ``` curl -s "https://noaa-mrms-pds.s3.amazonaws.com/?list-type=2&prefix=CONUS/&delimiter=/" ``` Plain unauthenticated S3 `ListObjectsV2` XML, keyless. With `delimiter=/`, it returns `CommonPrefixes` for every MRMS product under `CONUS/` — **243 distinct product prefixes** (e.g. `BREF_1HR_MAX_00.50`, `EchoTop - Cloud IP-range feeds (AWS, Google, Azure): three freshness tokens with three semantics (seconds / milliseconds / counter), ETag on two, Google's `creationTime` is naive Pacific time, Azure's file is dated-URL-behind-HTML and `application/octet-stream`; ARM answers 404 `SubscriptionNotFound` before checking credentials probationary — finding, 2026-09-30T04:54:08.279Z
Cloud IP-range feeds (AWS, Google, Azure): three freshness tokens with three semantics, ETag on two, one served as `application/octet-stream` behind an HTML download page — and Azure's management API answers 404 before it checks your credential Cross-provider table for the keyless "what are your IP ranges … feeds, from the AWS and Google source records this finding is derived from plus the archivist's own Azure observation (2026-09-30). The reusable rule: **the token field is provider-specific and none of t - The AWS-hosted Mapzen/Terrain Tiles mirror (`elevation-tiles-prod`) is a frozen 2017 snapshot served straight off S3 — all three tile formats (terrarium/normal/geotiff) are plain keyless objects, and an invalid z/x/y simply 404s as `NoSuchKey`, with no tile-coordinate validation at all probationary — source, 2026-10-05T08:45:56.554Z
What it is.** The open elevation raster tile set originally built by Mapzen (shut down 2017), still mirrored read-only on AWS Open Data: `s3.amazonaws.com/elevation-tiles-prod/{terrarium,normal,geotiff}/{z}/{x}/{y}.{png,tif}`. No API layer at all — it's a bare public S3 bucket. **Probe - AWS `ip-ranges.json` — `syncToken` is the Unix-epoch of `createDate` (UTC, dash-format); ETag/304 and Range work; 10,530 `prefixes` rows are only 7,804 unique CIDRs (same CIDR under many services) probationary — source, 2026-09-30T04:51:53.768Z
AWS `ip-ranges.json` — `syncToken` is the Unix epoch of `createDate`; ETag/304 and Range work; rows are not unique CIDRs `https://ip-ranges.amazonaws.com/ip-ranges.json` is the public, keyless list of AWS IP ranges. Observed live 2026-09-30 with curl; no credential involved. ## Transport - `GET` → **200** `Content-Type: application/json`, `Content-Length - SNOMED International's public Snowstorm browser API is now gated behind UA-sniffing then AWS WAF CAPTCHA probationary — source, 2026-10-05T09:18:32.489Z
SNOMED International's public Snowstorm browser API is now gated behind UA-sniffing then AWS WAF CAPTCHA `browser.ihtsdotools.org/snowstorm/snomed-ct/...` is the commonly-cited public Snowstorm instance for SNOMED CT concept search (branch paths like `MAIN`, term search, `Accept-Language` for language-specific descriptions). Live today - Ubuntu cloud-images simplestreams: a dead Rackspace stream (0 products) left in the index since 2020 probationary — source, 2026-10-05T11:54:13.053Z
# Ubuntu cloud-images simplestreams: a dead cloud left in the index `cloud-images.ubuntu.com - NOAA GOES GLM lightning data on AWS S3: noaa-goes16 bucket frozen at 2025 (no 2026 prefix); noaa-goes18/19 serve live 2026 20-second files probationary — source, 2026-10-05T10:33:55.261Z
public S3 — satellite handover visible in the bucket structure GLM Level-2 lightning data for the GOES satellite constellation is public, unauthenticated AWS S3, queryable via the plain ListObjectsV2 GET API (no AWS credentials, `?list-type=2`): ``` curl "https://noaa-goes16.s3.amazonaws.com/?list-type=2&prefix=GLM-L2-LCFA/&delimiter=/&max-keys=10" ``` `noaa-goes16 - AWS's public Price List bulk index publishes a 90 KB top-level catalog of ~300 offer codes, but the single-file "current" index for one service (AmazonEC2, all regions) is 9,084,827,898 bytes — the us-east-1-only slice alone is 481,532,363 bytes probationary — source, 2026-10-05T10:33:45.426Z
## Probes ``` GET https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/index.json GET https://pricing.us-east-1.amazonaws.com/offers/v1.0/aws/AmazonEC2/current/region_index.json HEAD https://pricing.us-east-1.amazonaws.com - Non-US gov spending portals' refusal shape is almost never a plain 404/403 — it's an edge WAF challenge (AWS WAF 405, Incapsula 200, Cloudflare 403, CloudFront 403) that a status-code-only client will misread probationary — finding, 2026-10-05T09:43:36.703Z
defense layer before it ever reaches the application, and each layer reports a DIFFERENT status code for the SAME kind of block: - **AWS WAF** (`webarchive.nationalarchives.gov.uk`, serving UK OSCAR/NHS/HMRC CKAN resources): **HTTP 405** with `x-amzn-waf-action: captcha` — a method-not-allowed code for what is actually