bgpreport

Network · data from 2026-11-12

AS266181 GOLDEN LINK

Registry name: AS266181 - GOLDEN LINK, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS266181, 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.

191.242.107.0/24 Valid Nonecovered by 191.242.104.0/21 668 99% 67
45.6.100.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
187.120.24.0/23 Valid Other IRR onlyRADB 672 100% 66
187.120.24.0/24 Valid Other IRR onlyRADB 672 100% 66
187.120.27.0/24 Valid Other IRR onlyRADB 672 100% 66
187.120.28.0/24 Valid Other IRR onlyRADB 672 100% 66
187.120.31.0/24 Valid Other IRR onlyRADB 672 100% 66
186.233.112.0/21 Valid Other IRR onlyRADB, TC 671 100% 66
187.120.16.0/21 Valid Other IRR onlyRADB 671 100% 66
187.120.26.0/24 Valid Other IRR onlyRADB 671 100% 66
187.120.29.0/24 Valid Other IRR onlyRADB 671 100% 66
187.120.30.0/24 Valid Other IRR onlyRADB 671 100% 66
191.242.104.0/21 Valid Other IRR onlyRADB 668 99% 67
2804:5b0::/32 Valid Other IRR onlyTC 634 100% 67
2804:3bf0::/32 Valid Other IRR onlyRADB, TC 634 100% 67

AS-SET

PeeringDB's irr_as_set for AS266181: AS-GOLDENLINK. 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 (AS266181 isn't in the set, or no route object for AS266181 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 objectsAS266181 in itNot covered
AS-GOLDENLINK RADBlists itself further down11 member sets in no database: AS-FIBERONE-ALL, AS-FJCEVOLUTION, AS-FNTTELECOM-ALL, AS-JMTELECOM, AS-M-I-MONTREAL-ALL … 3351506,463 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 31 are in fix.csv.

  • Route object: none1
  • Route object: RIR14
  • AS-SET: missing member11
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: none191.242.107.0/24No route object for it. A route object for 191.242.104.0/21 with origin AS266181 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266181 in the RIR database for the space.668 of 673
Route object: RIR45.6.100.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR187.120.24.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.120.24.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.120.27.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.120.28.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR187.120.31.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR186.233.112.0/21Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.120.16.0/21Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.120.26.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.120.29.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR187.120.30.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.242.104.0/21Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:5b0::/32Route object only in TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:3bf0::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS-FIBERONE-ALL; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS-FJCEVOLUTION; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS-FNTTELECOM-ALL; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS-JMTELECOM; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS-M-I-MONTREAL-ALL; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS-TRIBENET-ALL; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS264301:AS-LNP-TELECOM; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS264301:AS-LNP-TELECOM-ALL; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS265393:AS-ANNOUNCEMENTS; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS267942:AS-PRIMELINELATAM-ALL; no IRR database read has it.
AS-SET: missing memberAS-GOLDENLINKAS-GOLDENLINK (RADB) lists AS270728:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

45.6.100.0/23RADBValid
45.6.102.0/23RADBValid
64.224.16.0/22ARINNo ROA
187.120.16.0/20RADB, TCValid
187.120.16.0/22RADBValid

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.