Network · data from 2026-11-12
AS20080 AMPATH
Registry name: AMPATH - Florida International University, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS20080, 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.
| 67.17.206.128/27 | No ROA | Nonecovered by 67.17.206.0/24 | 10 1%low visibility |
| 67.17.206.192/26 | No ROA | Nonecovered by 67.17.206.0/24 | 8 1%low visibility |
| 67.17.206.0/24 | No ROA | Other IRR onlyRADB | 665 99% |
| 198.32.252.0/24 | No ROA | Other IRR onlyRADB | 665 99% |
| 2001:468:700::/48 | No ROA | Other IRR onlyNTTCOM, RADB | 632 99% |
| 2800:bc0:8000::/33 | Valid | Nonecovered by 2800:bc0::/32 | 17 3%low visibility |
| 170.39.8.0/23 | Valid | Other IRR onlyRADB | 665 99% |
| 190.103.184.0/22 | Valid | Other IRR onlyRADB | 664 99% |
| 2800:bc0::/32 | Valid | Other IRR onlyNTTCOM, RADB | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS20080: RADB::AS-AS20080-TRANSIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS20080 isn't in the set, or no route object for AS20080 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS20080 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS-AS20080-TRANSIT | RADB4 member sets in no database: AS-TERTIARY, AS1251:AS-FAPESP, AS27750:AS-MEMBERS, AS61468:AS-CEDIATRANSITMIEMBROS | 13 | 1 | Yes | 2 |
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 38 are in fix.csv.
- ROA: none5
- Route object: none3
- Route object: RIR6
- AS-SET: missing member4
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 67.17.206.128/27 | No ROA covers it. Add a ROA for AS20080, maxLength 27. |
| Route object: none | 67.17.206.128/27 | No route object for it. A route object for 67.17.206.0/24 with origin AS20080 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS20080 in the RIR database for the space. |
| ROA: none | 67.17.206.192/26 | No ROA covers it. Add a ROA for AS20080, maxLength 26. |
| Route object: none | 67.17.206.192/26 | No route object for it. A route object for 67.17.206.0/24 with origin AS20080 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS20080 in the RIR database for the space. |
| ROA: none | 67.17.206.0/24 | No ROA covers it. Add a ROA for AS20080, maxLength 24. |
| Route object: RIR | 67.17.206.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 198.32.252.0/24 | No ROA covers it. Add a ROA for AS20080, maxLength 24. |
| Route object: RIR | 198.32.252.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2001:468:700::/48 | No ROA covers it. Add a ROA for AS20080, maxLength 48. |
| Route object: RIR | 2001:468:700::/48 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| Route object: none | 2800:bc0:8000::/33 | No route object for it. A route object for 2800:bc0::/32 with origin AS20080 covers it (filters allowing more-specifics accept it). Add a route object with origin AS20080 in the RIR database for the space. |
| Route object: RIR | 170.39.8.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.103.184.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2800:bc0::/32 | Route object only in NTTCOM, RADB. Add it in the RIR database for the space. |
| AS-SET: missing member | RADB::AS-AS20080-TRANSIT | AS-AS20080-TRANSIT (RADB) lists AS-TERTIARY; no IRR database read has it. |
| AS-SET: missing member | RADB::AS-AS20080-TRANSIT | AS-AS20080-TRANSIT (RADB) lists AS1251:AS-FAPESP; no IRR database read has it. |
| AS-SET: missing member | RADB::AS-AS20080-TRANSIT | AS-AS20080-TRANSIT (RADB) lists AS27750:AS-MEMBERS; no IRR database read has it. |
| AS-SET: missing member | RADB::AS-AS20080-TRANSIT | AS-AS20080-TRANSIT (RADB) lists AS61468:AS-CEDIATRANSITMIEMBROS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS20080 whose prefix no peer sees AS20080 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 143.255.248.0/22 | LACNIC | Valid |
| 187.251.160.0/19 | LACNIC | Valid |
| 190.15.128.0/20 | LACNIC | Valid |
| 201.159.220.0/22 | LACNIC | Valid |
| 2001:468:701::/48 | NTTCOM | No ROA |
| 2001:500:3::/48 | NTTCOM | No ROA |
| 2001:500:9e::/47 | NTTCOM | No ROA |
| 2001:500:9f::/48 | NTTCOM | No ROA |
| 2001:43f8:70::/45 | NTTCOM | No ROA |
| 2001:43f8:a0::/48 | NTTCOM | No ROA |
| 2001:43f8:700::/44 | NTTCOM | No ROA |
| 2001:43f8:770::/46 | NTTCOM | No ROA |
| 2620:11c:1000::/40 | NTTCOM | No ROA |
| 2800:68::/32 | LACNIC | Valid |
| 2800:a018::/32 | NTTCOM | No ROA |
| 2801:80:390::/48 | NTTCOM | No ROA |
| 2801:80:1350::/48 | NTTCOM | No ROA |
| 2804:18c::/32 | NTTCOM | No ROA |
| 2804:9b0::/32 | NTTCOM | No ROA |
| 2804:1f18::/32 | NTTCOM | No ROA |
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.