bgpreport

Network · data from 2026-11-12

AS134324 GOLDY DIGINET

Registry name: GOLDY-AS-IN - GOLDY DIGINET PRIVATE LIMITED, IN · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS134324, 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.
103.194.120.0/24 Invalid: origin RIR databaseAPNIC 16 2%low visibility 9
103.70.58.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67

AS-SET

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

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

  • ROA: origin1
ChangePrefix or setDetailFull-table peers
ROA: origin103.194.120.0/24ROAs covering it name AS45433, not AS134324. If AS134324 should announce it, add a ROA for AS134324.16 of 673

Route objects not announced

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