bgpreport

Network · data from 2026-11-12

AS270766 UNE PROVEDOR DE INTERNET LGT61 EIRELI

Registry name: AS270766 - UNE PROVEDOR DE INTERNET LGT61 EIRELI, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270766, 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:5954:fb00::/40 No ROA Other origin only 103 16% 40
186.194.172.0/23 Valid Nonecovered by 186.194.172.0/22 136 20% 45
186.194.174.0/23 Valid Nonecovered by 186.194.172.0/22 136 20% 45
2804:7118::/33 Valid Nonecovered by 2804:7118::/32 121 19% 44
2804:7118:8000::/33 Valid Nonecovered by 2804:7118::/32 121 19% 44
186.194.172.0/22 Valid Other IRR onlyRADB, TC 671 100% 66
2804:7118::/32 Valid Other IRR onlyTC 634 100% 69

AS-SET

PeeringDB's irr_as_set for AS270766: AS270766:AS-UNETELECOM. 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 (AS270766 isn't in the set, or no route object for AS270766 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 objectsAS270766 in itNot covered
AS270766:AS-UNETELECOM TC 2140 Yes 1

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

  • ROA: none1
  • Route object: none5
  • Route object: RIR2
ChangePrefix or setDetailFull-table peers
ROA: none2804:5954:fb00::/40No ROA covers it. Add a ROA for AS270766, maxLength 40.103 of 636
Route object: none2804:5954:fb00::/40Route objects for it name AS268183. Add a route object with origin AS270766 in the RIR database for the space.103 of 636
Route object: none186.194.172.0/23No route object for it. A route object for 186.194.172.0/22 with origin AS270766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270766 in the RIR database for the space.136 of 673
Route object: none186.194.174.0/23No route object for it. A route object for 186.194.172.0/22 with origin AS270766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270766 in the RIR database for the space.136 of 673
Route object: none2804:7118::/33No route object for it. A route object for 2804:7118::/32 with origin AS270766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270766 in the RIR database for the space.121 of 636
Route object: none2804:7118:8000::/33No route object for it. A route object for 2804:7118::/32 with origin AS270766 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270766 in the RIR database for the space.121 of 636
Route object: RIR186.194.172.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:7118::/32Route object only in TC. Add it in the RIR database for the space.634 of 636

Route objects not announced

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