Network · data from 2026-11-12

AS213772 BK Customers

Registry name: BK-CUST UAB "Baltnetos komunikacijos", LT · PeeringDB

8IPv4 routes 75.0% RPKI valid · 75.0% with a route object

0IPv6 routes

2RPKI invalid 2 origin · 0 maxLength

0No ROA 2 with no route object for this origin

2Low visibility seen by under 10% of full-table peers

2Route objects not announced registered with origin AS213772, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS213772, 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.188.254.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
181.214.147.0/24	Invalid: origin	Other origin only	2 0%low visibility	2
91.244.197.0/24	Valid	Other IRR onlyRADB	673 100%	66
88.223.100.0/24	Valid	RIR databaseRIPE	673 100%	66
146.103.38.0/24	Valid	RIR databaseRADB, RIPE	673 100%	66
193.187.112.0/22	Valid	RIR databaseRIPE	673 100%	66
45.82.42.0/24	Valid	RIR databaseRIPE	672 100%	66
45.153.237.0/24	Valid	RIR databaseRIPE	672 100%	66

91.188.254.0/24

Invalid: origin

Other origin only

2 0%low visibility

181.214.147.0/24

Invalid: origin

Other origin only

2 0%low visibility

91.244.197.0/24

Valid

Other IRR onlyRADB

673 100%

88.223.100.0/24

Valid

RIR databaseRIPE

673 100%

146.103.38.0/24

Valid

RIR databaseRADB, RIPE

673 100%

193.187.112.0/22

Valid

RIR databaseRIPE

673 100%

45.82.42.0/24

Valid

RIR databaseRIPE

672 100%

45.153.237.0/24

Valid

RIR databaseRIPE

672 100%

AS-SET

AS213772's PeeringDB record names no 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 7 are in fix.csv.

ROA: origin2
Route object: none2
Route object: RIR1
Route object: not announced2

Change	Prefix or set	Detail	Full-table peers
ROA: origin	91.188.254.0/24	ROAs covering it name AS834, not AS213772. If AS213772 should announce it, add a ROA for AS213772.	2 of 673
Route object: none	91.188.254.0/24	Route objects for it name AS834. Add a route object with origin AS213772 in the RIR database for the space.	2 of 673
ROA: origin	181.214.147.0/24	ROAs covering it name AS834, not AS213772. If AS213772 should announce it, add a ROA for AS213772.	2 of 673
Route object: none	181.214.147.0/24	Route objects for it name AS834. Add a route object with origin AS213772 in the RIR database for the space.	2 of 673
Route object: RIR	91.244.197.0/24	Route object only in RADB. Add it in the RIR database for the space.	673 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: origin

91.188.254.0/24

ROAs covering it name AS834, not AS213772. If AS213772 should announce it, add a ROA for AS213772.

2 of 673

Route object: none

91.188.254.0/24

Route objects for it name AS834. Add a route object with origin AS213772 in the RIR database for the space.

2 of 673

ROA: origin

181.214.147.0/24

ROAs covering it name AS834, not AS213772. If AS213772 should announce it, add a ROA for AS213772.

2 of 673

Route object: none

181.214.147.0/24

Route objects for it name AS834. Add a route object with origin AS213772 in the RIR database for the space.

2 of 673

Route object: RIR

91.244.197.0/24

Route object only in RADB. Add it in the RIR database for the space.

673 of 673

Route objects not announced

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


85.209.231.0/24	RADB, RIPE	Valid
222.167.199.0/24	RIPE	Invalid: origin

85.209.231.0/24

RADB, RIPE

Valid

222.167.199.0/24

RIPE

Invalid: origin

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.