bgpreport

Network · data from 2026-11-12

AS202116 SCANIA-AS Scania CV AB

Registry name: SCANIA-AS Scania CV AB, SE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS202116, 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.
138.106.0.0/16 No ROA Other origin only 673 100% 67
139.122.189.0/24 No ROA Other origin only 673 100% 67
139.122.191.0/24 No ROA None 673 100% 67
139.122.192.0/20 No ROA None 673 100% 67
139.122.240.0/22 No ROA None 673 100% 67
139.122.224.0/20 No ROA Other IRR onlyRADB 673 100% 66
157.10.210.0/23 No ROA RIR databaseAPNIC 671 100% 67

AS-SET

AS202116 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: none7
  • Route object: none5
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none138.106.0.0/16No ROA covers it. Add a ROA for AS202116, maxLength 16.673 of 673
Route object: none138.106.0.0/16Route objects for it name AS1257. Add a route object with origin AS202116 in the RIR database for the space.673 of 673
ROA: none139.122.189.0/24No ROA covers it. Add a ROA for AS202116, maxLength 24.673 of 673
Route object: none139.122.189.0/24Route objects for it name AS1257, AS3301. Add a route object with origin AS202116 in the RIR database for the space.673 of 673
ROA: none139.122.191.0/24No ROA covers it. Add a ROA for AS202116, maxLength 24.673 of 673
Route object: none139.122.191.0/24No route object for it. Add a route object with origin AS202116 in the RIR database for the space.673 of 673
ROA: none139.122.192.0/20No ROA covers it. Add a ROA for AS202116, maxLength 20.673 of 673
Route object: none139.122.192.0/20No route object for it. Add a route object with origin AS202116 in the RIR database for the space.673 of 673
ROA: none139.122.240.0/22No ROA covers it. Add a ROA for AS202116, maxLength 22.673 of 673
Route object: none139.122.240.0/22No route object for it. Add a route object with origin AS202116 in the RIR database for the space.673 of 673
ROA: none139.122.224.0/20No ROA covers it. Add a ROA for AS202116, maxLength 20.673 of 673
Route object: RIR139.122.224.0/20Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none157.10.210.0/23No ROA covers it. Add a ROA for AS202116, maxLength 23.671 of 673

Route objects not announced

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