Network · data from 2026-11-12

AS48129 IRBIS Telecommunications

Registry name: IRBIS-TELECOMMUNICATIONS-AS IRBIS Telecommunications Ltd., RU · PeeringDB

13IPv4 routes 76.9% RPKI valid · 100.0% with a route object

0IPv6 routes

0RPKI invalid 0 origin · 0 maxLength

3No 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 AS48129, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS48129, 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.30.112.0/24	No ROA	RIR databaseRIPE	672 100%	67
81.30.114.0/24	No ROA	RIR databaseRIPE	672 100%	67
81.30.123.0/24	No ROA	RIR databaseRIPE	672 100%	67
81.30.113.0/24	Valid	RIR databaseRIPE	672 100%	67
81.30.115.0/24	Valid	RIR databaseRIPE	672 100%	67
81.30.116.0/24	Valid	RIR databaseRIPE	672 100%	67
81.30.117.0/24	Valid	RIR databaseRIPE	672 100%	67
81.30.118.0/24	Valid	RIR databaseRIPE	672 100%	67
81.30.119.0/24	Valid	RIR databaseRIPE	672 100%	67
81.30.124.0/24	Valid	RIR databaseRIPE	672 100%	67
81.30.125.0/24	Valid	RIR databaseRIPE	672 100%	67
81.30.126.0/24	Valid	RIR databaseRIPE	672 100%	67
91.210.44.0/22	Valid	RIR databaseRIPE	672 100%	67

AS-SET

PeeringDB's irr_as_set for AS48129: RIPE::AS-IRBISTELECOM. 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 (AS48129 isn't in the set, or no route object for AS48129 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.

Name	Database	ASNs	Sets	Route objects	AS48129 in it	Not covered
RIPE::AS-IRBISTELECOM	RIPE	4	1	34	Yes	0

Name

Database

ASNs

Sets

Route objects

AS48129 in it

Not covered

RIPE::AS-IRBISTELECOM

RIPE

Yes

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

ROA: none3

Change	Prefix or set	Detail	Full-table peers
ROA: none	81.30.112.0/24	No ROA covers it. Add a ROA for AS48129, maxLength 24.	672 of 673
ROA: none	81.30.114.0/24	No ROA covers it. Add a ROA for AS48129, maxLength 24.	672 of 673
ROA: none	81.30.123.0/24	No ROA covers it. Add a ROA for AS48129, maxLength 24.	672 of 673

Change

Prefix or set

Detail

Full-table peers

ROA: none

81.30.112.0/24

No ROA covers it. Add a ROA for AS48129, maxLength 24.

672 of 673

ROA: none

81.30.114.0/24

No ROA covers it. Add a ROA for AS48129, maxLength 24.

672 of 673

ROA: none

81.30.123.0/24

No ROA covers it. Add a ROA for AS48129, maxLength 24.

672 of 673

Route objects not announced

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