bgpreport

Network · data from 2026-11-12

AS208946 Sirius-2014 LLC

Registry name: assirius2014 Sirius-2014 LLC, KZ · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS208946, 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.
45.13.16.0/23 No ROA RIR databaseRIPE 673 100% 67
45.13.18.0/24 No ROA RIR databaseRIPE 673 100% 67
45.13.19.0/24 No ROA RIR databaseRIPE 673 100% 67
93.171.158.0/24 Valid Nonecovered by 93.171.158.0/23 2 0%low visibility 2
93.171.159.0/24 Valid Nonecovered by 93.171.158.0/23 2 0%low visibility 2
93.171.158.0/23 Valid RIR databaseRIPE 673 100% 67
95.47.108.0/23 Valid RIR databaseRIPE 673 100% 67
95.47.144.0/23 Valid RIR databaseRIPE 673 100% 67

AS-SET

AS208946'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 5 are in fix.csv.

  • ROA: none3
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: none45.13.16.0/23No ROA covers it. Add a ROA for AS208946, maxLength 23.673 of 673
ROA: none45.13.18.0/24No ROA covers it. Add a ROA for AS208946, maxLength 24.673 of 673
ROA: none45.13.19.0/24No ROA covers it. Add a ROA for AS208946, maxLength 24.673 of 673
Route object: none93.171.158.0/24No route object for it. A route object for 93.171.158.0/23 with origin AS208946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208946 in the RIR database for the space.2 of 673
Route object: none93.171.159.0/24No route object for it. A route object for 93.171.158.0/23 with origin AS208946 covers it (filters allowing more-specifics accept it). Add a route object with origin AS208946 in the RIR database for the space.2 of 673

Route objects not announced

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