bgpreport

Network · data from 2026-11-12

AS49368 DomoLAN

Registry name: DOMOLAN-AS DomoLAN Ltd., RU · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 0.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
2No 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 AS49368, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS49368, 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.
2a14:9c0::/48 No ROA RIR databaseRIPE 636 100% 69
2a14:9c7::/32 No ROA RIR databaseRIPE 636 100% 69
188.94.32.0/21 Valid RIR databaseRIPE 671 100% 68
188.126.32.0/20 Valid RIR databaseRIPE 671 100% 68
188.126.48.0/20 Valid RIR databaseRIPE 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS49368: AS-DOMOLAN. 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 (AS49368 isn't in the set, or no route object for AS49368 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 objectsAS49368 in itNot covered
AS-DOMOLAN RIPE 115 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 2 are in fix.csv.

  • ROA: none2
ChangePrefix or setDetailFull-table peers
ROA: none2a14:9c0::/48No ROA covers it. Add a ROA for AS49368, maxLength 48.636 of 636
ROA: none2a14:9c7::/32No ROA covers it. Add a ROA for AS49368, maxLength 32.636 of 636

Route objects not announced

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