bgpreport

Network · data from 2026-11-12

AS197563 GNM UA

Registry name: GNMUA-AS "GLOBALNET UA" LLC, UA · PeeringDB

1IPv4 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 AS197563, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS197563, 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.
178.18.231.0/24 Valid RIR databaseRIPE 671 100% 67
2001:b28:4::/48 Valid RIR databaseRIPE 636 100% 67
2a03:5f80:8::/48 Valid RIR databaseRIPE 636 100% 67
2a03:5f80:a::/48 Valid RIR databaseRIPE 635 100% 67

AS-SET

PeeringDB's irr_as_set for AS197563: RIPE::AS197563:AS-GLOBALNET-UA. 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 (AS197563 isn't in the set, or no route object for AS197563 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 objectsAS197563 in itNot covered
RIPE::AS197563:AS-GLOBALNET-UA RIPElists itself further down6 member sets in no database: AS-AIREXPRESS, AS-HORS, AS-INFOBYTE-IFIX, AS-UNETCOM, AS-WINTELECOM … 1,10227614,414 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 6 are in fix.csv.

  • AS-SET: missing member6
ChangePrefix or setDetailFull-table peers
AS-SET: missing memberRIPE::AS197563:AS-GLOBALNET-UAAS197563:AS-GLOBALNET-UA (RIPE) lists AS-AIREXPRESS; no IRR database read has it.
AS-SET: missing memberRIPE::AS197563:AS-GLOBALNET-UAAS197563:AS-GLOBALNET-UA (RIPE) lists AS-HORS; no IRR database read has it.
AS-SET: missing memberRIPE::AS197563:AS-GLOBALNET-UAAS197563:AS-GLOBALNET-UA (RIPE) lists AS-INFOBYTE-IFIX; no IRR database read has it.
AS-SET: missing memberRIPE::AS197563:AS-GLOBALNET-UAAS197563:AS-GLOBALNET-UA (RIPE) lists AS-UNETCOM; no IRR database read has it.
AS-SET: missing memberRIPE::AS197563:AS-GLOBALNET-UAAS197563:AS-GLOBALNET-UA (RIPE) lists AS-WINTELECOM; no IRR database read has it.
AS-SET: missing memberRIPE::AS197563:AS-GLOBALNET-UAAS197563:AS-GLOBALNET-UA (RIPE) lists AS199986:AS-SET; no IRR database read has it.

Route objects not announced

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