bgpreport

Network · data from 2026-11-12

AS266129 LOCALLINK TELECOMUNICAÇÕES LTDA - ME

Registry name: AS266129 - LOCALLINK TELECOMUNICACOES LTDA - ME, BR · PeeringDB

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

Announced routes

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

2804:3b18:c300::/40 Invalid: maxLength Nonecovered by 2804:3b18:c000::/34 70 11% 38
2804:76cc::/33 No ROA None 635 100% 67
2804:76cc::/34 No ROA None 635 100% 67
2804:76cc:4000::/34 No ROA None 635 100% 67
2804:76cc:c000::/34 No ROA None 635 100% 67
2804:76cc::/32 No ROA Other origin only 634 100% 67
2804:76cc:8000::/33 No ROA None 634 100% 67
2804:76cc:8000::/34 No ROA None 634 100% 67
45.6.92.0/23 Valid Other IRR onlyTC 673 100% 66
45.6.94.0/23 Valid Other IRR onlyTC 673 100% 66
177.36.22.0/24 Valid Other IRR onlyTC 672 100% 66
177.36.20.0/24 Valid Other IRR onlyTC 671 100% 66
177.36.23.0/24 Valid Other IRR onlyTC 671 100% 66
45.6.92.0/22 Valid Other IRR onlyRADB, TC 670 100% 66
45.165.54.0/23 Valid Other IRR onlyRADB, TC 670 100% 66
45.165.54.0/24 Valid Other IRR onlyTC 670 100% 66
45.165.55.0/24 Valid Other IRR onlyTC 669 99% 67
177.36.21.0/24 Valid Other IRR onlyTC 668 99% 66
2804:3b18::/32 Valid Other IRR onlyRADB, TC 634 100% 69
2804:3b18::/33 Valid Other IRR onlyTC 351 55% 65
2804:3b18::/34 Valid Other IRR onlyTC 351 55% 65
2804:3b18:4000::/34 Valid Other IRR onlyTC 351 55% 65
2804:3b18:8000::/33 Valid Other IRR onlyTC 351 55% 65
2804:3b18:8000::/34 Valid Other IRR onlyTC 351 55% 65
2804:3b18:c000::/34 Valid Other IRR onlyTC 351 55% 65
45.6.92.0/24 Valid Other IRR onlyTC 205 30% 56
45.6.95.0/24 Valid Other IRR onlyTC 205 30% 56
45.6.93.0/24 Valid Other IRR onlyTC 203 30% 56
45.6.94.0/24 Valid Other IRR onlyTC 203 30% 56

AS-SET

PeeringDB's irr_as_set for AS266129: AS266129:AS-LOCALLINK. 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 (AS266129 isn't in the set, or no route object for AS266129 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 objectsAS266129 in itNot covered
AS266129:AS-LOCALLINK In no IRR database read today.

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

  • ROA: maxLength1
  • ROA: none7
  • Route object: none8
  • Route object: RIR21
  • AS-SET: not found1
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: maxLength2804:3b18:c300::/40ROA 2804:3b18:8000::/33 AS266129 has maxLength 33; ROA 2804:3b18::/32 AS266129 has maxLength 32; ROA 2804:3b18:c000::/34 AS266129 has maxLength 34; the route is a /40. Raise the maxLength, or add a ROA for 2804:3b18:c300::/40.70 of 636
Route object: none2804:3b18:c300::/40No route object for it. A route object for 2804:3b18:c000::/34 with origin AS266129 covers it (filters allowing more-specifics accept it). Add a route object with origin AS266129 in the RIR database for the space.70 of 636
ROA: none2804:76cc::/33No ROA covers it. Add a ROA for AS266129, maxLength 33.635 of 636
Route object: none2804:76cc::/33No route object for it. Add a route object with origin AS266129 in the RIR database for the space.635 of 636
ROA: none2804:76cc::/34No ROA covers it. Add a ROA for AS266129, maxLength 34.635 of 636
Route object: none2804:76cc::/34No route object for it. Add a route object with origin AS266129 in the RIR database for the space.635 of 636
ROA: none2804:76cc:4000::/34No ROA covers it. Add a ROA for AS266129, maxLength 34.635 of 636
Route object: none2804:76cc:4000::/34No route object for it. Add a route object with origin AS266129 in the RIR database for the space.635 of 636
ROA: none2804:76cc:c000::/34No ROA covers it. Add a ROA for AS266129, maxLength 34.635 of 636
Route object: none2804:76cc:c000::/34No route object for it. Add a route object with origin AS266129 in the RIR database for the space.635 of 636
ROA: none2804:76cc::/32No ROA covers it. Add a ROA for AS266129, maxLength 32.634 of 636
Route object: none2804:76cc::/32Route objects for it name AS271135. Add a route object with origin AS266129 in the RIR database for the space.634 of 636
ROA: none2804:76cc:8000::/33No ROA covers it. Add a ROA for AS266129, maxLength 33.634 of 636
Route object: none2804:76cc:8000::/33No route object for it. Add a route object with origin AS266129 in the RIR database for the space.634 of 636
ROA: none2804:76cc:8000::/34No ROA covers it. Add a ROA for AS266129, maxLength 34.634 of 636
Route object: none2804:76cc:8000::/34No route object for it. Add a route object with origin AS266129 in the RIR database for the space.634 of 636
Route object: RIR45.6.92.0/23Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR45.6.94.0/23Route object only in TC. Add it in the RIR database for the space.673 of 673
Route object: RIR177.36.22.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.36.20.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR177.36.23.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR45.6.92.0/22Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.165.54.0/23Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.165.54.0/24Route object only in TC. Add it in the RIR database for the space.670 of 673
Route object: RIR45.165.55.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
Route object: RIR177.36.21.0/24Route object only in TC. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:3b18::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:3b18::/33Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:3b18::/34Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:3b18:4000::/34Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:3b18:8000::/33Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:3b18:8000::/34Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR2804:3b18:c000::/34Route object only in TC. Add it in the RIR database for the space.351 of 636
Route object: RIR45.6.92.0/24Route object only in TC. Add it in the RIR database for the space.205 of 673
Route object: RIR45.6.95.0/24Route object only in TC. Add it in the RIR database for the space.205 of 673
Route object: RIR45.6.93.0/24Route object only in TC. Add it in the RIR database for the space.203 of 673
Route object: RIR45.6.94.0/24Route object only in TC. Add it in the RIR database for the space.203 of 673
AS-SET: not foundAS266129:AS-LOCALLINKPeeringDB names AS266129:AS-LOCALLINK; no IRR database read has it.

Route objects not announced

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

177.36.20.0/22RADB, TCValid
177.36.20.0/23TCValid
177.36.22.0/23TCValid
2804:1550::/32RADBNo ROA

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.