bgpreport

Network · data from 2026-11-12

AS149978 SPNHOST-AS-AP - SPNHOST

Registry name: SPNHOST-AS-AP - SPNHOST, BD · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS149978, 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.
82.152.234.0/24 Invalid: origin Other origin only 2 0%low visibility 2
82.152.241.0/24 Invalid: origin Other origin only 2 0%low visibility 2
169.40.60.0/22 Invalid: origin Other origin only 2 0%low visibility 2
195.21.135.0/24 Invalid: origin Other origin only 2 0%low visibility 2
195.162.249.0/24 Invalid: origin Other origin only 2 0%low visibility 2
195.162.250.0/24 Invalid: origin None 2 0%low visibility 2
195.162.251.0/24 Invalid: origin None 2 0%low visibility 2
195.162.252.0/24 Invalid: origin Other origin only 2 0%low visibility 2
169.40.52.0/22 No ROA None 2 0%low visibility 2
72.244.168.0/22 Valid RIR databaseARIN, RADB 671 100% 66

AS-SET

AS149978 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 18 are in fix.csv.

  • ROA: origin8
  • ROA: none1
  • Route object: none9
ChangePrefix or setDetailFull-table peers
ROA: origin82.152.234.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS149978. If AS149978 should announce it, add a ROA for AS149978.2 of 673
Route object: none82.152.234.0/24Route objects for it name AS174, AS834. Add a route object with origin AS149978 in the RIR database for the space.2 of 673
ROA: origin82.152.241.0/24ROAs covering it name AS834, AS8851, AS19905, AS206509, not AS149978. If AS149978 should announce it, add a ROA for AS149978.2 of 673
Route object: none82.152.241.0/24Route objects for it name AS174, AS834. Add a route object with origin AS149978 in the RIR database for the space.2 of 673
ROA: origin169.40.60.0/22ROAs covering it name AS834, not AS149978. If AS149978 should announce it, add a ROA for AS149978.2 of 673
Route object: none169.40.60.0/22Route objects for it name AS834. Add a route object with origin AS149978 in the RIR database for the space.2 of 673
ROA: origin195.21.135.0/24ROAs covering it name AS834, not AS149978. If AS149978 should announce it, add a ROA for AS149978.2 of 673
Route object: none195.21.135.0/24Route objects for it name AS834. Add a route object with origin AS149978 in the RIR database for the space.2 of 673
ROA: origin195.162.249.0/24ROAs covering it name AS834, not AS149978. If AS149978 should announce it, add a ROA for AS149978.2 of 673
Route object: none195.162.249.0/24Route objects for it name AS834. Add a route object with origin AS149978 in the RIR database for the space.2 of 673
ROA: origin195.162.250.0/24ROAs covering it name AS834, not AS149978. If AS149978 should announce it, add a ROA for AS149978.2 of 673
Route object: none195.162.250.0/24No route object for it. Add a route object with origin AS149978 in the RIR database for the space.2 of 673
ROA: origin195.162.251.0/24ROAs covering it name AS834, not AS149978. If AS149978 should announce it, add a ROA for AS149978.2 of 673
Route object: none195.162.251.0/24No route object for it. Add a route object with origin AS149978 in the RIR database for the space.2 of 673
ROA: origin195.162.252.0/24ROAs covering it name AS834, not AS149978. If AS149978 should announce it, add a ROA for AS149978.2 of 673
Route object: none195.162.252.0/24Route objects for it name AS834. Add a route object with origin AS149978 in the RIR database for the space.2 of 673
ROA: none169.40.52.0/22No ROA covers it. Add a ROA for AS149978, maxLength 22.2 of 673
Route object: none169.40.52.0/22No route object for it. Add a route object with origin AS149978 in the RIR database for the space.2 of 673

Route objects not announced

Every route object with origin AS149978 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.