bgpreport

Network · data from 2026-11-12

AS20910 BALTCOM

Registry name: BALTKOM-AS SIA "BITE Latvija", LV · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS20910, 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.148.168.0/21 Valid RIR databaseRIPE 673 100% 66
62.84.0.0/20 Valid RIR databaseRIPE 673 100% 66
62.205.192.0/18 Valid RIR databaseRIPE 673 100% 66
77.38.128.0/17 Valid RIR databaseRIPE 673 100% 66
85.254.120.0/23 Valid RIR databaseRIPE 673 100% 66
87.226.0.0/17 Valid RIR databaseRIPE 673 100% 66
89.201.0.0/17 Valid RIR databaseRIPE 673 100% 66
91.142.0.0/20 Valid RIR databaseRIPE 673 100% 66
91.188.32.0/19 Valid RIR databaseRIPE 673 100% 66
93.177.192.0/18 Valid RIR databaseRIPE 673 100% 66
94.30.128.0/17 Valid RIR databaseRIPE 673 100% 66
109.110.0.0/19 Valid RIR databaseRIPE 673 100% 66
136.169.0.0/17 Valid RIR databaseRIPE 673 100% 66
185.144.184.0/22 Valid RIR databaseRIPE 673 100% 66
188.112.128.0/18 Valid RIR databaseRIPE 673 100% 66
195.62.128.0/19 Valid RIR databaseRIPE 673 100% 66
195.244.128.0/20 Valid RIR databaseRIPE 673 100% 66
213.180.96.0/19 Valid RIR databaseRIPE 673 100% 66
217.198.224.0/20 Valid RIR databaseRIPE 673 100% 66
217.199.96.0/19 Valid RIR databaseRIPE 673 100% 66
2a00:9000::/29 Valid RIR databaseRIPE 635 100% 69
2a00:f4a0::/29 Valid RIR databaseRIPE 635 100% 69
2a03:6740::/29 Valid RIR databaseRIPE 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS20910: AS-BALTKOM. 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 (AS20910 isn't in the set, or no route object for AS20910 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 objectsAS20910 in itNot covered
AS-BALTKOM RIPE 455161 Yes 0

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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