bgpreport

Network · data from 2026-11-12

AS39816 Volta Communications

Registry name: VOLTA-AS Volta Communications Sp.z.o.o., PL · PeeringDB

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

Announced routes

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

91.221.214.0/23 No ROA RIR databaseRIPE 673 100% 67
95.142.242.0/24 No ROA RIR databaseRIPE 673 100% 67
194.116.130.0/24 No ROA RIR databaseRIPE 673 100% 67
81.95.204.0/22 No ROA RIR databaseRIPE 672 100% 67
95.142.241.0/24 No ROA RIR databaseRIPE 672 100% 67
95.142.244.0/22 No ROA RIR databaseRIPE 672 100% 67
95.142.248.0/21 No ROA RIR databaseRIPE 672 100% 67
185.122.88.0/22 No ROA RIR databaseRIPE 672 100% 67
193.26.131.0/24 No ROA RIR databaseRIPE 672 100% 67
84.38.16.0/20 Valid RIR databaseRIPE 672 100% 67

AS-SET

PeeringDB's irr_as_set for AS39816: AS-VOLTA. 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 (AS39816 isn't in the set, or no route object for AS39816 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 objectsAS39816 in itNot covered
AS-VOLTA RIPE 8132 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 22 are in fix.csv.

  • ROA: none9
  • Route object: not announced13
ChangePrefix or setDetailFull-table peers
ROA: none91.221.214.0/23No ROA covers it. Add a ROA for AS39816, maxLength 23.673 of 673
ROA: none95.142.242.0/24No ROA covers it. Add a ROA for AS39816, maxLength 24.673 of 673
ROA: none194.116.130.0/24No ROA covers it. Add a ROA for AS39816, maxLength 24.673 of 673
ROA: none81.95.204.0/22No ROA covers it. Add a ROA for AS39816, maxLength 22.672 of 673
ROA: none95.142.241.0/24No ROA covers it. Add a ROA for AS39816, maxLength 24.672 of 673
ROA: none95.142.244.0/22No ROA covers it. Add a ROA for AS39816, maxLength 22.672 of 673
ROA: none95.142.248.0/21No ROA covers it. Add a ROA for AS39816, maxLength 21.672 of 673
ROA: none185.122.88.0/22No ROA covers it. Add a ROA for AS39816, maxLength 22.672 of 673
ROA: none193.26.131.0/24No ROA covers it. Add a ROA for AS39816, maxLength 24.672 of 673

Route objects not announced

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

81.95.200.0/22RIPENo ROA
81.95.200.0/23RIPENo ROA
83.142.176.0/21RIPENo ROA
84.38.16.0/21RIPEInvalid: maxLength
84.38.24.0/21RIPEInvalid: maxLength
95.142.240.0/20RIPENo ROA
95.142.240.0/23RIPENo ROA
109.197.60.0/23RIPEInvalid: origin
109.197.63.0/24RIPEInvalid: origin
194.116.130.0/23RIPENo ROA
195.66.103.0/24RIPENo ROA
2a00:5b20::/32RIPENo ROA
2a13:2802:3000::/36RIPENo ROA

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.