bgpreport

Network · data from 2026-11-12

AS59702 Junet AB

Registry name: JUNET Junet AB, SE · PeeringDB

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

Announced routes

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

81.25.144.0/21 Invalid: maxLength Nonecovered by 81.25.144.0/20 63 9%low visibility 30
81.25.152.0/24 Invalid: maxLength Nonecovered by 81.25.144.0/20 63 9%low visibility 30
81.25.154.0/24 Invalid: maxLength Nonecovered by 81.25.144.0/20 63 9%low visibility 30
81.25.155.0/24 Invalid: maxLength Nonecovered by 81.25.144.0/20 63 9%low visibility 30
81.25.153.0/24 Invalid: maxLength Nonecovered by 81.25.144.0/20 62 9%low visibility 30
172.103.92.0/24 Invalid: maxLength Nonecovered by 172.103.88.0/21 62 9%low visibility 30
172.103.93.0/24 Invalid: maxLength Nonecovered by 172.103.88.0/21 62 9%low visibility 30
185.47.195.0/24 Invalid: maxLength Nonecovered by 185.47.192.0/22 62 9%low visibility 30
195.42.104.0/24 Invalid: maxLength Nonecovered by 195.42.104.0/23 62 9%low visibility 30
207.189.201.0/24 Invalid: maxLength Nonecovered by 207.189.192.0/20 62 9%low visibility 30
216.158.105.0/24 Invalid: maxLength Nonecovered by 216.158.96.0/20 62 9%low visibility 30
216.158.106.0/24 Invalid: maxLength Nonecovered by 216.158.96.0/20 62 9%low visibility 30
216.158.107.0/24 Invalid: maxLength Nonecovered by 216.158.96.0/20 62 9%low visibility 30
216.158.108.0/24 Invalid: maxLength Nonecovered by 216.158.96.0/20 62 9%low visibility 30
81.25.144.0/20 Valid RIR databaseRIPE 673 100% 66
172.103.88.0/21 Valid RIR databaseRIPE 673 100% 66
31.31.160.0/21 Valid RIR databaseRIPE 672 100% 66
31.31.163.0/24 Valid RIR databaseRIPE 672 100% 67
31.31.165.0/24 Valid RIR databaseRIPE 672 100% 67
146.66.232.0/21 Valid RIR databaseRIPE 672 100% 66
185.16.200.0/22 Valid RIR databaseRIPE 672 100% 66
185.47.192.0/24 Valid RIR databaseRIPE 672 100% 67
185.47.194.0/24 Valid RIR databaseRIPE 672 100% 67
185.80.216.0/22 Valid RIR databaseRIPE 672 100% 66
195.42.104.0/23 Valid RIR databaseRIPE 672 100% 66
207.189.192.0/20 Valid RIR databaseRIPE 672 100% 66
213.244.240.0/21 Valid RIR databaseRIPE 672 100% 66
216.158.96.0/20 Valid RIR databaseRIPE 672 100% 66
185.47.192.0/22 Valid RIR databaseRIPE 671 100% 66
194.37.249.0/24 Valid RIR databaseRIPE 671 100% 66
2a03:780::/32 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS59702: AS-JUNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS59702 isn't in the set, or no route object for AS59702 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS59702 in itNot covered
AS-JUNET RIPE 1121 Yes 0

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

  • ROA: maxLength14
  • Route object: none14
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength81.25.144.0/21ROA 81.25.144.0/20 AS59702 has maxLength 20; the route is a /21. Raise the maxLength, or add a ROA for 81.25.144.0/21.63 of 673
Route object: none81.25.144.0/21No route object for it. A route object for 81.25.144.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.63 of 673
ROA: maxLength81.25.152.0/24ROA 81.25.144.0/20 AS59702 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 81.25.152.0/24.63 of 673
Route object: none81.25.152.0/24No route object for it. A route object for 81.25.144.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.63 of 673
ROA: maxLength81.25.154.0/24ROA 81.25.144.0/20 AS59702 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 81.25.154.0/24.63 of 673
Route object: none81.25.154.0/24No route object for it. A route object for 81.25.144.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.63 of 673
ROA: maxLength81.25.155.0/24ROA 81.25.144.0/20 AS59702 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 81.25.155.0/24.63 of 673
Route object: none81.25.155.0/24No route object for it. A route object for 81.25.144.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.63 of 673
ROA: maxLength81.25.153.0/24ROA 81.25.144.0/20 AS59702 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 81.25.153.0/24.62 of 673
Route object: none81.25.153.0/24No route object for it. A route object for 81.25.144.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673
ROA: maxLength172.103.92.0/24ROA 172.103.88.0/21 AS59702 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 172.103.92.0/24.62 of 673
Route object: none172.103.92.0/24No route object for it. A route object for 172.103.88.0/21 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673
ROA: maxLength172.103.93.0/24ROA 172.103.88.0/21 AS59702 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 172.103.93.0/24.62 of 673
Route object: none172.103.93.0/24No route object for it. A route object for 172.103.88.0/21 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673
ROA: maxLength185.47.195.0/24ROA 185.47.192.0/22 AS59702 has maxLength 22; the route is a /24. Raise the maxLength, or add a ROA for 185.47.195.0/24.62 of 673
Route object: none185.47.195.0/24No route object for it. A route object for 185.47.192.0/22 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673
ROA: maxLength195.42.104.0/24ROA 195.42.104.0/23 AS59702 has maxLength 23; the route is a /24. Raise the maxLength, or add a ROA for 195.42.104.0/24.62 of 673
Route object: none195.42.104.0/24No route object for it. A route object for 195.42.104.0/23 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673
ROA: maxLength207.189.201.0/24ROA 207.189.192.0/20 AS59702 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 207.189.201.0/24.62 of 673
Route object: none207.189.201.0/24No route object for it. A route object for 207.189.192.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673
ROA: maxLength216.158.105.0/24ROA 216.158.96.0/20 AS59702 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 216.158.105.0/24.62 of 673
Route object: none216.158.105.0/24No route object for it. A route object for 216.158.96.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673
ROA: maxLength216.158.106.0/24ROA 216.158.96.0/20 AS59702 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 216.158.106.0/24.62 of 673
Route object: none216.158.106.0/24No route object for it. A route object for 216.158.96.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673
ROA: maxLength216.158.107.0/24ROA 216.158.96.0/20 AS59702 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 216.158.107.0/24.62 of 673
Route object: none216.158.107.0/24No route object for it. A route object for 216.158.96.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673
ROA: maxLength216.158.108.0/24ROA 216.158.96.0/20 AS59702 has maxLength 20; the route is a /24. Raise the maxLength, or add a ROA for 216.158.108.0/24.62 of 673
Route object: none216.158.108.0/24No route object for it. A route object for 216.158.96.0/20 with origin AS59702 covers it (filters allowing more-specifics accept it). Add a route object with origin AS59702 in the RIR database for the space.62 of 673

Route objects not announced

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

31.31.161.0/24RIPEValid
31.31.166.0/24RIPEValid
31.31.167.0/24RIPEValid
185.47.193.0/24RIPEValid

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.