bgpreport

Network · data from 2026-11-12

AS53597 Hoyos Consulting

Registry name: HOYOS-CONSULTING-LLC - Hoyos Consulting LLC, US · PeeringDB

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

Announced routes

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

23.184.80.0/24 No ROA Other IRR onlyRADB 671 100% 68
2605:9180:4000::/36 Valid Nonecovered by 2605:9180::/32 634 100% 69
2605:9180:c000::/36 Valid Nonecovered by 2605:9180::/32 634 100% 69
141.193.124.0/22 Valid Other IRR onlyRADB 671 100% 68
162.248.232.0/22 Valid Other IRR onlyRADB 671 100% 68
162.248.232.0/23 Valid Other IRR onlyRADB 671 100% 68
162.248.235.0/24 Valid Other IRR onlyRADB 671 100% 68
172.102.4.0/22 Valid Other IRR onlyRADB 671 100% 68
172.102.7.0/24 Valid Other IRR onlyRADB 671 100% 68
2605:9180::/32 Valid Other IRR onlyRADB 634 100% 69
2605:9180:d000::/36 Valid Other IRR onlyRADB 634 100% 69
2605:9180:e100::/40 Valid Other IRR onlyRADB 634 100% 69
2605:9180:e200::/40 Valid Other IRR onlyRADB 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS53597: AS-HOYOS-NETWORK. 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 (AS53597 isn't in the set, or no route object for AS53597 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.

NameDatabaseASNsSets Route objectsAS53597 in itNot covered
AS-HOYOS-NETWORK RADB1 member set in no database: AS-2886-ALL 428356 Yes 0

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

  • ROA: none1
  • Route object: none2
  • Route object: RIR11
  • AS-SET: missing member1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none23.184.80.0/24No ROA covers it. Add a ROA for AS53597, maxLength 24.671 of 673
Route object: RIR23.184.80.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: none2605:9180:4000::/36No route object for it. A route object for 2605:9180::/32 with origin AS53597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53597 in the RIR database for the space.634 of 636
Route object: none2605:9180:c000::/36No route object for it. A route object for 2605:9180::/32 with origin AS53597 covers it (filters allowing more-specifics accept it). Add a route object with origin AS53597 in the RIR database for the space.634 of 636
Route object: RIR141.193.124.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR162.248.232.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR162.248.232.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR162.248.235.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.102.4.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR172.102.7.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR2605:9180::/32Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2605:9180:d000::/36Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2605:9180:e100::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2605:9180:e200::/40Route object only in RADB. Add it in the RIR database for the space.634 of 636
AS-SET: missing memberAS-HOYOS-NETWORKAS-HOYOS-NETWORK (RADB) lists AS-2886-ALL; no IRR database read has it.

Route objects not announced

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

198.200.146.0/24RADBNo ROA
199.45.8.0/22RADBNo ROA
204.11.135.0/24RADBValid
2001:470:85::/48ARINValid

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.