bgpreport

Network · data from 2026-11-12

AS63479 HAMWAN - HamWAN

Registry name: HAMWAN - HamWAN, US · not in PeeringDB

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

Announced routes

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

44.12.7.0/24 No ROA None 673 100% 67
44.12.96.0/22 No ROA None 673 100% 67
44.24.200.0/22 No ROA Other origin only 190 28% 56
44.12.6.0/24 No ROA Other IRR onlyALTDB 671 100% 67
44.12.9.0/24 No ROA Other IRR onlyALTDB, RADB 671 100% 69
44.24.221.0/24 No ROA Other IRR onlyALTDB 671 100% 67
44.25.0.0/16 No ROA Other IRR onlyALTDB 670 100% 69
44.30.58.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
44.30.119.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
44.31.187.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67
44.135.180.0/24 No ROA Other IRR onlyALTDB 670 100% 67
44.135.219.0/24 No ROA Other IRR onlyALTDB, RADB 670 100% 67

AS-SET

AS63479 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 39 are in fix.csv.

  • ROA: none12
  • Route object: none3
  • Route object: RIR9
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none44.12.7.0/24No ROA covers it. Add a ROA for AS63479, maxLength 24.673 of 673
Route object: none44.12.7.0/24No route object for it. Add a route object with origin AS63479 in the RIR database for the space.673 of 673
ROA: none44.12.96.0/22No ROA covers it. Add a ROA for AS63479, maxLength 22.673 of 673
Route object: none44.12.96.0/22No route object for it. Add a route object with origin AS63479 in the RIR database for the space.673 of 673
ROA: none44.24.200.0/22No ROA covers it. Add a ROA for AS63479, maxLength 22.190 of 673
Route object: none44.24.200.0/22Route objects for it name AS26566. Add a route object with origin AS63479 in the RIR database for the space.190 of 673
ROA: none44.12.6.0/24No ROA covers it. Add a ROA for AS63479, maxLength 24.671 of 673
Route object: RIR44.12.6.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none44.12.9.0/24No ROA covers it. Add a ROA for AS63479, maxLength 24.671 of 673
Route object: RIR44.12.9.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.671 of 673
ROA: none44.24.221.0/24No ROA covers it. Add a ROA for AS63479, maxLength 24.671 of 673
Route object: RIR44.24.221.0/24Route object only in ALTDB. Add it in the RIR database for the space.671 of 673
ROA: none44.25.0.0/16No ROA covers it. Add a ROA for AS63479, maxLength 16.670 of 673
Route object: RIR44.25.0.0/16Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none44.30.58.0/24No ROA covers it. Add a ROA for AS63479, maxLength 24.670 of 673
Route object: RIR44.30.58.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none44.30.119.0/24No ROA covers it. Add a ROA for AS63479, maxLength 24.670 of 673
Route object: RIR44.30.119.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none44.31.187.0/24No ROA covers it. Add a ROA for AS63479, maxLength 24.670 of 673
Route object: RIR44.31.187.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673
ROA: none44.135.180.0/24No ROA covers it. Add a ROA for AS63479, maxLength 24.670 of 673
Route object: RIR44.135.180.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none44.135.219.0/24No ROA covers it. Add a ROA for AS63479, maxLength 24.670 of 673
Route object: RIR44.135.219.0/24Route object only in ALTDB, RADB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

44.4.64.0/22ALTDBNo ROA
44.12.64.0/22ALTDBNo ROA
44.24.125.0/24RADBNo ROA
44.24.131.0/24ALTDBNo ROA
44.24.240.0/20ALTDBNo ROA
44.25.255.0/24ALTDBNo ROA
44.26.108.0/24ALTDBNo ROA
44.26.168.0/24ALTDBNo ROA
44.30.240.0/20ALTDBNo ROA
44.31.137.0/24RADBNo ROA
44.32.59.0/24RADBNo ROA
44.32.60.0/24RADBNo ROA
44.34.128.0/21ALTDBNo ROA
44.129.64.0/22ALTDBNo ROA
2604:5000:20::/48ALTDBInvalid: origin

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.