bgpreport

Network · data from 2026-11-12

AS30929 GOLEM TECH

Registry name: GOLEMTECH-AS GOLEM TECH s.r.o., SK · PeeringDB

3IPv4 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 AS30929, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS30929, 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.
185.98.208.0/22 Valid RIR databaseRIPE 670 100% 67
2a06:cc0::/29 Valid RIR databaseRIPE 634 100% 69
2a06:cc0::/30 Valid RIR databaseRIPE 631 99% 69
2a06:cc4::/30 Valid RIR databaseRIPE 631 99% 69
185.98.208.0/23 Valid RIR databaseRIPE 148 22% 44
185.98.210.0/23 Valid RIR databaseRIPE 148 22% 44

AS-SET

PeeringDB's irr_as_set for AS30929: AS30929. 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 (AS30929 isn't in the set, or no route object for AS30929 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 objectsAS30929 in itNot covered
AS30929 A single AS number, not a set: AS30929 (this network), 6 route objects.

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

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