Network · data from 2026-11-12
AS62785 AMAZON-FC - Amazon.com Services, LLC
Registry name: AMAZON-FC - Amazon.com Services, LLC, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS62785, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 173.83.0.0/17 | Valid | None | 667 99% |
| 172.96.110.0/24 | Valid | Nonecovered by 172.96.96.0/20 | 2 0%low visibility |
| 172.96.97.0/24 | Valid | Other IRR onlyRADB | 15 2%low visibility |
AS-SET
AS62785 isn't in PeeringDB, where networks name their AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 9 are in fix.csv.
- Route object: none2
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 173.83.0.0/17 | No route object for it. Add a route object with origin AS62785 in the RIR database for the space. |
| Route object: none | 172.96.110.0/24 | No route object for it. A route object for 172.96.96.0/20 with origin AS62785 covers it (filters allowing more-specifics accept it). Add a route object with origin AS62785 in the RIR database for the space. |
| Route object: RIR | 172.96.97.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS62785 whose prefix no peer sees AS62785 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 172.96.96.0/20 | RADB | Valid |
| 172.96.98.0/24 | RADB | Valid |
| 172.96.99.0/24 | RADB | Valid |
| 172.96.100.0/24 | RADB | Valid |
| 172.96.101.0/24 | RADB | Valid |
| 193.57.182.0/23 | RADB | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.