bgpreport

Network · data from 2026-11-12

AS11738 BLIP Networks

Registry name: BLIP-NETWORKS - BLIP Networks, US · PeeringDB

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

Announced routes

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

38.129.94.0/23 No ROA None 672 100% 67
38.21.129.0/24 No ROA Nonecovered by 38.21.128.0/21 670 100% 68
38.21.132.0/24 No ROA Nonecovered by 38.21.128.0/21 670 100% 68
38.21.134.0/24 No ROA Nonecovered by 38.21.128.0/21 670 100% 68
38.21.135.0/24 No ROA Nonecovered by 38.21.128.0/21 670 100% 68
38.21.128.0/21 No ROA Other IRR onlyRADB 670 100% 68
163.123.254.0/24 Valid Nonecovered by 163.123.252.0/22 672 100% 67
66.97.116.0/22 Valid RIR databaseARIN 670 100% 68
163.123.252.0/22 Valid RIR databaseARIN 670 100% 68
2605:a1c0::/32 Valid RIR databaseARIN 635 100% 69

AS-SET

AS11738's PeeringDB record names no 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 14 are in fix.csv.

  • ROA: none6
  • Route object: none6
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none38.129.94.0/23No ROA covers it. Add a ROA for AS11738, maxLength 23.672 of 673
Route object: none38.129.94.0/23No route object for it. Add a route object with origin AS11738 in the RIR database for the space.672 of 673
ROA: none38.21.129.0/24No ROA covers it. Add a ROA for AS11738, maxLength 24.670 of 673
Route object: none38.21.129.0/24No route object for it. A route object for 38.21.128.0/21 with origin AS11738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11738 in the RIR database for the space.670 of 673
ROA: none38.21.132.0/24No ROA covers it. Add a ROA for AS11738, maxLength 24.670 of 673
Route object: none38.21.132.0/24No route object for it. A route object for 38.21.128.0/21 with origin AS11738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11738 in the RIR database for the space.670 of 673
ROA: none38.21.134.0/24No ROA covers it. Add a ROA for AS11738, maxLength 24.670 of 673
Route object: none38.21.134.0/24No route object for it. A route object for 38.21.128.0/21 with origin AS11738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11738 in the RIR database for the space.670 of 673
ROA: none38.21.135.0/24No ROA covers it. Add a ROA for AS11738, maxLength 24.670 of 673
Route object: none38.21.135.0/24No route object for it. A route object for 38.21.128.0/21 with origin AS11738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11738 in the RIR database for the space.670 of 673
ROA: none38.21.128.0/21No ROA covers it. Add a ROA for AS11738, maxLength 21.670 of 673
Route object: RIR38.21.128.0/21Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: none163.123.254.0/24No route object for it. A route object for 163.123.252.0/22 with origin AS11738 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11738 in the RIR database for the space.672 of 673

Route objects not announced

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

2001:470:1e9::/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.