bgpreport

Network · data from 2026-11-12

AS394581 BLUESPAN

Registry name: BLUESPAN - Bluespan Wireless, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394581, 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.
172.110.168.0/24 Valid Other IRR onlyRADB 673 100% 67
172.110.169.0/24 Valid Other IRR onlyRADB 673 100% 67
172.110.170.0/24 Valid Other IRR onlyRADB 673 100% 67
172.110.171.0/24 Valid Other IRR onlyRADB 673 100% 67
74.122.160.0/24 Valid Other IRR onlyRADB 672 100% 67
74.122.161.0/24 Valid Other IRR onlyRADB 672 100% 67
74.122.162.0/24 Valid Other IRR onlyRADB 672 100% 67
74.122.163.0/24 Valid Other IRR onlyRADB 672 100% 67
2607:e80::/32 Valid RIR databaseARIN, RADB 635 100% 67

AS-SET

AS394581'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 38 are in fix.csv.

  • Route object: RIR8
  • Route object: not announced30
ChangePrefix or setDetailFull-table peers
Route object: RIR172.110.168.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR172.110.169.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR172.110.170.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR172.110.171.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR74.122.160.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.122.161.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.122.162.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR74.122.163.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

8.10.150.0/24RADBNo ROA
50.58.129.0/24RADBNo ROA
74.122.160.0/22ARIN, RADBValid
74.122.160.0/23RADBValid
172.110.168.0/22ARINValid
173.227.34.0/23RADBNo ROA
173.227.35.0/24RADBNo ROA
174.46.244.0/23RADBNo ROA
206.169.116.0/24RADBNo ROA
207.114.135.0/24RADBNo ROA
209.136.143.0/24RADBNo ROA
209.194.248.0/23RADBNo ROA
209.234.134.0/24RADBNo ROA
209.234.171.0/24RADBNo ROA
2607:e80::/36RADBValid
2607:e80:1000::/36RADBValid
2607:e80:2000::/36RADBValid
2607:e80:3000::/36RADBValid
2607:e80:4000::/36RADBValid
2607:e80:5000::/36RADBValid
2607:e80:6000::/36RADBValid
2607:e80:7000::/36RADBValid
2607:e80:8000::/36RADBValid
2607:e80:9000::/36RADBValid
2607:e80:a000::/36RADBValid
2607:e80:b000::/36RADBValid
2607:e80:c000::/36RADBValid
2607:e80:d000::/36RADBValid
2607:e80:e000::/36RADBValid
2607:e80:f000::/36RADBValid

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.