bgpreport

Network · data from 2026-11-12

AS399631 STREAMICAN - StreamICan

Registry name: STREAMICAN - StreamICan, US · not in PeeringDB

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

Announced routes

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

51.241.92.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.153.97.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.153.102.0/24 Invalid: origin Other origin only 2 0%low visibility 2
185.49.125.0/24 Invalid: origin None 2 0%low visibility 2
82.153.109.0/24 Invalid: origin Other origin only 1 0%low visibility 1
217.25.8.0/24 Invalid: origin Other origin only 1 0%low visibility 1
2a13:9500:1b4::/48 Invalid: origin RIR databaseRIPE 3 0%low visibility 4
96.126.132.0/24 Valid RIR databaseARIN 2 0%low visibility 2
212.60.148.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
212.189.45.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2
217.79.99.0/24 Valid RIR databaseRADB, RIPE 2 0%low visibility 2

AS-SET

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

  • ROA: origin7
  • Route object: none6
ChangePrefix or setDetailFull-table peers
ROA: origin51.241.92.0/24ROAs covering it name AS834, not AS399631. If AS399631 should announce it, add a ROA for AS399631.2 of 673
Route object: none51.241.92.0/24Route objects for it name AS834. Add a route object with origin AS399631 in the RIR database for the space.2 of 673
ROA: origin82.153.97.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS399631. If AS399631 should announce it, add a ROA for AS399631.2 of 673
Route object: none82.153.97.0/24Route objects for it name AS834. Add a route object with origin AS399631 in the RIR database for the space.2 of 673
ROA: origin82.153.102.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS399631. If AS399631 should announce it, add a ROA for AS399631.2 of 673
Route object: none82.153.102.0/24Route objects for it name AS834. Add a route object with origin AS399631 in the RIR database for the space.2 of 673
ROA: origin185.49.125.0/24ROAs covering it name AS834, not AS399631. If AS399631 should announce it, add a ROA for AS399631.2 of 673
Route object: none185.49.125.0/24No route object for it. Add a route object with origin AS399631 in the RIR database for the space.2 of 673
ROA: origin82.153.109.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS399631. If AS399631 should announce it, add a ROA for AS399631.1 of 673
Route object: none82.153.109.0/24Route objects for it name AS834. Add a route object with origin AS399631 in the RIR database for the space.1 of 673
ROA: origin217.25.8.0/24ROAs covering it name AS137410, not AS399631. If AS399631 should announce it, add a ROA for AS399631.1 of 673
Route object: none217.25.8.0/24Route objects for it name AS137410. Add a route object with origin AS399631 in the RIR database for the space.1 of 673
ROA: origin2a13:9500:1b4::/48ROAs covering it name AS218269, not AS399631. If AS399631 should announce it, add a ROA for AS399631.3 of 636

Route objects not announced

Every route object with origin AS399631 is announced.

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.