bgpreport

Network · data from 2026-11-12

AS57049 Kvant-II

Registry name: KVANT-II-AS Small Private Enterprise Kvant-II, UA · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS57049, 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.230.25.0/24 No ROA RIR databaseRIPE 671 100% 68
92.118.76.0/24 No ROA RIR databaseRIPE 671 100% 68
92.118.77.0/24 No ROA RIR databaseRIPE 671 100% 68
92.118.78.0/24 No ROA RIR databaseRIPE 671 100% 68
188.191.148.0/22 No ROA RIR databaseRIPE 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS57049: RIPE::AS-KVANT-II. 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 (AS57049 isn't in the set, or no route object for AS57049 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 objectsAS57049 in itNot covered
RIPE::AS-KVANT-II RIPE1 member set in no database: AS-INFOBYTE-IFIX 359340 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 7 are in fix.csv.

  • ROA: none5
  • AS-SET: missing member1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none91.230.25.0/24No ROA covers it. Add a ROA for AS57049, maxLength 24.671 of 673
ROA: none92.118.76.0/24No ROA covers it. Add a ROA for AS57049, maxLength 24.671 of 673
ROA: none92.118.77.0/24No ROA covers it. Add a ROA for AS57049, maxLength 24.671 of 673
ROA: none92.118.78.0/24No ROA covers it. Add a ROA for AS57049, maxLength 24.671 of 673
ROA: none188.191.148.0/22No ROA covers it. Add a ROA for AS57049, maxLength 22.671 of 673
AS-SET: missing memberRIPE::AS-KVANT-IIAS-KVANT-II (RIPE) lists AS-INFOBYTE-IFIX; no IRR database read has it.

Route objects not announced

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

45.131.167.0/24RIPENo 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.