bgpreport

Network · data from 2026-11-12

AS20048 AMA-AS-0001 - American Medical Association

Registry name: AMA-AS-0001 - American Medical Association, US · not in PeeringDB

1IPv4 routes 0.0% RPKI valid · 0.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 1 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
1Route objects not announced registered with origin AS20048, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS20048, 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.

199.164.8.0/21 No ROA Other origin only 673 100% 67

AS-SET

AS20048 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 3 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none199.164.8.0/21No ROA covers it. Add a ROA for AS20048, maxLength 21.673 of 673
Route object: none199.164.8.0/21Route objects for it name AS63474. Add a route object with origin AS20048 in the RIR database for the space.673 of 673

Route objects not announced

Route objects with origin AS20048 whose prefix no peer sees AS20048 announce. Many are kept on purpose (backup routes, space announced only in some places).

204.29.0.0/21RADBNo 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.