bgpreport

Network · data from 2026-11-12

AS11855 ASN-INTERNAP-BLK - Unitas Global

Registry name: ASN-INTERNAP-BLK - Unitas Global, US · not in PeeringDB

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

Announced routes

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

66.171.197.0/24 No ROA Nonecovered by 66.171.196.0/23 672 100% 66
64.94.88.0/22 No ROA Other IRR onlyRADB 672 100% 66
64.95.108.0/22 No ROA Other IRR onlyRADB 672 100% 66
66.171.192.0/22 No ROA Other IRR onlyRADB 672 100% 66
66.171.196.0/22 No ROA Other IRR onlyRADB 672 100% 66
69.25.120.0/21 No ROA Other IRR onlyRADB 672 100% 66
69.25.168.0/21 No ROA Other IRR onlyRADB 672 100% 66
69.25.224.0/21 No ROA Other IRR onlyRADB 672 100% 66
70.42.8.0/21 No ROA Other IRR onlyRADB 672 100% 66
70.42.224.0/21 No ROA Other IRR onlyRADB 672 100% 66
74.217.184.0/22 No ROA Other IRR onlyRADB 672 100% 66
216.52.55.0/24 No ROA Other IRR onlyRADB 672 100% 66
74.217.184.0/24 No ROA Other IRR onlyRADB 671 100% 66
74.217.186.0/24 No ROA Other IRR onlyRADB 671 100% 66
2600:c05::/32 No ROA Other IRR onlyRADB 635 100% 68

AS-SET

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

  • ROA: none15
  • Route object: none1
  • Route object: RIR14
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
ROA: none66.171.197.0/24No ROA covers it. Add a ROA for AS11855, maxLength 24.672 of 673
Route object: none66.171.197.0/24No route object for it. A route object for 66.171.196.0/23 with origin AS11855 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11855 in the RIR database for the space.672 of 673
ROA: none64.94.88.0/22No ROA covers it. Add a ROA for AS11855, maxLength 22.672 of 673
Route object: RIR64.94.88.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none64.95.108.0/22No ROA covers it. Add a ROA for AS11855, maxLength 22.672 of 673
Route object: RIR64.95.108.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none66.171.192.0/22No ROA covers it. Add a ROA for AS11855, maxLength 22.672 of 673
Route object: RIR66.171.192.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none66.171.196.0/22No ROA covers it. Add a ROA for AS11855, maxLength 22.672 of 673
Route object: RIR66.171.196.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none69.25.120.0/21No ROA covers it. Add a ROA for AS11855, maxLength 21.672 of 673
Route object: RIR69.25.120.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none69.25.168.0/21No ROA covers it. Add a ROA for AS11855, maxLength 21.672 of 673
Route object: RIR69.25.168.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none69.25.224.0/21No ROA covers it. Add a ROA for AS11855, maxLength 21.672 of 673
Route object: RIR69.25.224.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none70.42.8.0/21No ROA covers it. Add a ROA for AS11855, maxLength 21.672 of 673
Route object: RIR70.42.8.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none70.42.224.0/21No ROA covers it. Add a ROA for AS11855, maxLength 21.672 of 673
Route object: RIR70.42.224.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.217.184.0/22No ROA covers it. Add a ROA for AS11855, maxLength 22.672 of 673
Route object: RIR74.217.184.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none216.52.55.0/24No ROA covers it. Add a ROA for AS11855, maxLength 24.672 of 673
Route object: RIR216.52.55.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
ROA: none74.217.184.0/24No ROA covers it. Add a ROA for AS11855, maxLength 24.671 of 673
Route object: RIR74.217.184.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none74.217.186.0/24No ROA covers it. Add a ROA for AS11855, maxLength 24.671 of 673
Route object: RIR74.217.186.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2600:c05::/32No ROA covers it. Add a ROA for AS11855, maxLength 32.635 of 636
Route object: RIR2600:c05::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

4.20.90.208/29RADBNo ROA
52.124.63.0/24RADBNo ROA
63.251.66.0/23RADBNo ROA
63.251.68.0/22RADBNo ROA
64.74.164.0/24RADBNo ROA
64.94.90.0/24RADBNo ROA
64.94.96.0/24RADBNo ROA
66.150.176.0/23RADBNo ROA
66.150.178.0/24RADBNo ROA
66.171.196.0/23RADBNo ROA
66.171.196.0/24RADBNo ROA
69.25.81.0/24RADBNo ROA
69.25.101.0/24RADBNo ROA
69.25.227.0/24RADBNo ROA
134.242.45.0/24RADBNo ROA
167.173.201.0/24RADBNo ROA
170.153.0.0/16RADBNo ROA
198.134.1.0/24RADBNo ROA
198.207.0.0/21RADBNo ROA
199.233.179.0/24RADBNo ROA
204.56.100.0/23RADBNo ROA
204.238.150.0/24RADBNo ROA
216.27.160.0/19RADBNo ROA
216.52.201.0/24RADBNo ROA
2405:c400:195::/48RADBNo ROA
2405:c400:196::/48RADBNo 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.