bgpreport

Network · data from 2026-11-12

AS34702 Aktsiaselts WaveCom

Registry name: WAVECOM-AS Aktsiaselts WaveCom, EE · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS34702, 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.
37.252.5.72/32 Invalid: maxLength Nonecovered by 37.252.4.0/23 2 0%low visibility 6
38.180.163.81/32 Invalid: maxLength Nonecovered by 38.180.163.0/24 2 0%low visibility 6
80.79.118.119/32 Invalid: maxLength Nonecovered by 80.79.112.0/20 2 0%low visibility 6
77.83.28.0/22 No ROA RIR databaseRIPE 673 100% 67
38.244.154.0/24 Valid Other IRR onlyRADB 672 100% 67
38.244.155.0/24 Valid Other IRR onlyRADB 672 100% 67
38.244.227.0/24 Valid Other IRR onlyRADB 672 100% 67
37.252.4.0/23 Valid RIR databaseRIPE 673 100% 67
38.180.44.0/23 Valid RIR databaseARIN, RADB 673 100% 67
46.22.208.0/20 Valid RIR databaseRIPE 673 100% 67
80.79.112.0/20 Valid RIR databaseRIPE 673 100% 67
114.129.9.0/24 Valid RIR databaseRIPE 673 100% 67
176.97.74.0/24 Valid RIR databaseRIPE 673 100% 67
185.114.116.0/24 Valid RIR databaseRIPE 673 100% 67
185.200.196.0/24 Valid RIR databaseRIPE 673 100% 67
38.180.10.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.180.163.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.180.164.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.180.216.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.180.230.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.180.248.0/24 Valid RIR databaseARIN, RADB 672 100% 67
38.244.216.0/24 Valid RIR databaseARIN, RADB 672 100% 67
185.46.20.0/22 Valid RIR databaseRIPE 671 100% 67
185.246.184.0/22 Valid RIR databaseRIPE 671 100% 67
2a01:97a0::/32 Valid RIR databaseRIPE 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS34702: AS34702:AS-ALL. 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 (AS34702 isn't in the set, or no route object for AS34702 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 objectsAS34702 in itNot covered
AS34702:AS-ALL RIPE 21265 Yes 3

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

  • ROA: maxLength3
  • ROA: none1
  • Route object: none3
  • Route object: RIR3
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: maxLength37.252.5.72/32ROA 37.252.4.0/23 AS34702 has maxLength 23; the route is a /32. Raise the maxLength, or add a ROA for 37.252.5.72/32.2 of 673
Route object: none37.252.5.72/32No route object for it. A route object for 37.252.4.0/23 with origin AS34702 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34702 in the RIR database for the space.2 of 673
ROA: maxLength38.180.163.81/32ROA 38.180.163.0/24 AS34702 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 38.180.163.81/32.2 of 673
Route object: none38.180.163.81/32No route object for it. A route object for 38.180.163.0/24 with origin AS34702 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34702 in the RIR database for the space.2 of 673
ROA: maxLength80.79.118.119/32ROA 80.79.112.0/20 AS34702 has maxLength 20; the route is a /32. Raise the maxLength, or add a ROA for 80.79.118.119/32.2 of 673
Route object: none80.79.118.119/32No route object for it. A route object for 80.79.112.0/20 with origin AS34702 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS34702 in the RIR database for the space.2 of 673
ROA: none77.83.28.0/22No ROA covers it. Add a ROA for AS34702, maxLength 22.673 of 673
Route object: RIR38.244.154.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.244.155.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR38.244.227.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

38.244.154.0/23ARINValid

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.