bgpreport

Network · data from 2026-11-12

AS56479 HCT-AS Higher Colleges of Technology

Registry name: HCT-AS Higher Colleges of Technology, AE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS56479, 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.
31.29.71.0/24 No ROA Nonecovered by 31.29.64.0/19 46 7%low visibility 29
31.29.64.0/19 No ROA Other IRR onlyRADB 672 100% 67
194.170.32.0/19 Valid Other origin only 46 7%low visibility 29
195.229.176.0/24 Valid Other IRR onlyRADB 672 100% 67
195.229.177.0/24 Valid Other IRR onlyRADB 672 100% 67
195.229.175.0/24 Valid Other IRR onlyRADB 46 7%low visibility 29
195.229.178.0/24 Valid Other IRR onlyRADB 46 7%low visibility 29
195.229.179.0/24 Valid Other IRR onlyRADB 46 7%low visibility 29
195.229.180.0/24 Valid Other IRR onlyRADB 46 7%low visibility 29
195.229.181.0/24 Valid Other IRR onlyRADB 46 7%low visibility 29

AS-SET

AS56479 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 12 are in fix.csv.

  • ROA: none2
  • Route object: none2
  • Route object: RIR8
ChangePrefix or setDetailFull-table peers
ROA: none31.29.71.0/24No ROA covers it. Add a ROA for AS56479, maxLength 24.46 of 673
Route object: none31.29.71.0/24No route object for it. A route object for 31.29.64.0/19 with origin AS56479 covers it (filters allowing more-specifics accept it). Add a route object with origin AS56479 in the RIR database for the space.46 of 673
ROA: none31.29.64.0/19No ROA covers it. Add a ROA for AS56479, maxLength 19.672 of 673
Route object: RIR31.29.64.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: none194.170.32.0/19Route objects for it name AS5384. Add a route object with origin AS56479 in the RIR database for the space.46 of 673
Route object: RIR195.229.176.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR195.229.177.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR195.229.175.0/24Route object only in RADB. Add it in the RIR database for the space.46 of 673
Route object: RIR195.229.178.0/24Route object only in RADB. Add it in the RIR database for the space.46 of 673
Route object: RIR195.229.179.0/24Route object only in RADB. Add it in the RIR database for the space.46 of 673
Route object: RIR195.229.180.0/24Route object only in RADB. Add it in the RIR database for the space.46 of 673
Route object: RIR195.229.181.0/24Route object only in RADB. Add it in the RIR database for the space.46 of 673

Route objects not announced

Every route object with origin AS56479 is announced.

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.