bgpreport

Network · data from 2026-11-12

AS12178 INTERNAP-2BLK - Unitas Global

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS12178, 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.150.40.0/21 No ROA Other origin only 671 100% 67
74.217.112.0/20 No ROA None 5 1%low visibility 4
64.74.144.0/20 No ROA Other IRR onlyRADB 671 100% 66
64.94.196.0/22 No ROA Other IRR onlyRADB 671 100% 66
66.150.224.0/22 No ROA Other IRR onlyRADB 671 100% 66
216.52.64.0/22 No ROA Other IRR onlyRADB 671 100% 66
216.52.76.0/22 No ROA Other IRR onlyRADB 671 100% 66
2600:c09::/32 No ROA Other IRR onlyRADB 635 100% 68

AS-SET

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

  • ROA: none8
  • Route object: none2
  • Route object: RIR6
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: none66.150.40.0/21No ROA covers it. Add a ROA for AS12178, maxLength 21.671 of 673
Route object: none66.150.40.0/21Route objects for it name AS13789. Add a route object with origin AS12178 in the RIR database for the space.671 of 673
ROA: none74.217.112.0/20No ROA covers it. Add a ROA for AS12178, maxLength 20.5 of 673
Route object: none74.217.112.0/20No route object for it. Add a route object with origin AS12178 in the RIR database for the space.5 of 673
ROA: none64.74.144.0/20No ROA covers it. Add a ROA for AS12178, maxLength 20.671 of 673
Route object: RIR64.74.144.0/20Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none64.94.196.0/22No ROA covers it. Add a ROA for AS12178, maxLength 22.671 of 673
Route object: RIR64.94.196.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none66.150.224.0/22No ROA covers it. Add a ROA for AS12178, maxLength 22.671 of 673
Route object: RIR66.150.224.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none216.52.64.0/22No ROA covers it. Add a ROA for AS12178, maxLength 22.671 of 673
Route object: RIR216.52.64.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none216.52.76.0/22No ROA covers it. Add a ROA for AS12178, maxLength 22.671 of 673
Route object: RIR216.52.76.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none2600:c09::/32No ROA covers it. Add a ROA for AS12178, maxLength 32.635 of 636
Route object: RIR2600:c09::/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 AS12178 whose prefix no peer sees AS12178 announce. Many are kept on purpose (backup routes, space announced only in some places).

8.25.174.0/24RADBNo ROA
64.74.145.0/24RADBNo ROA
64.94.166.0/24RADBNo ROA
69.36.128.0/20RADBNo ROA
74.217.234.0/23RADBNo ROA
75.98.72.0/23RADBNo ROA
193.221.76.0/23RADBNo ROA
198.199.159.0/24RADBNo ROA
204.227.73.0/24RADBNo ROA
208.78.44.0/22RADBNo ROA
208.78.46.0/24RADBNo ROA
208.78.47.0/24RADBNo ROA
208.97.217.0/24RADBNo ROA
216.52.64.166/32RADBNo ROA
216.52.72.0/21RADBNo ROA
216.52.72.0/22RADBNo 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.