bgpreport

Network · data from 2026-11-12

AS271337 LIKENET

Registry name: AS271337 - LIKENET TELECOM LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271337, 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.
200.106.222.0/24 Valid Nonecovered by 200.106.222.0/23 671 100% 66
2804:79f0::/33 Valid Nonecovered by 2804:79f0::/32 636 100% 67
2804:79f0:8000::/33 Valid Nonecovered by 2804:79f0::/32 636 100% 67
200.106.223.0/24 Valid Other IRR onlyRADB 670 100% 66
200.106.222.0/23 Valid Other IRR onlyRADB, TC 669 99% 67
2804:79f0::/32 Valid Other IRR onlyRADB, TC 636 100% 67

AS-SET

PeeringDB's irr_as_set for AS271337: AS271337:AS-LIKENET. 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 (AS271337 isn't in the set, or no route object for AS271337 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 objectsAS271337 in itNot covered
AS271337:AS-LIKENET 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 7 are in fix.csv.

  • Route object: none3
  • Route object: RIR3
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
Route object: none200.106.222.0/24No route object for it. A route object for 200.106.222.0/23 with origin AS271337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271337 in the RIR database for the space.671 of 673
Route object: none2804:79f0::/33No route object for it. A route object for 2804:79f0::/32 with origin AS271337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271337 in the RIR database for the space.636 of 636
Route object: none2804:79f0:8000::/33No route object for it. A route object for 2804:79f0::/32 with origin AS271337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271337 in the RIR database for the space.636 of 636
Route object: RIR200.106.223.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR200.106.222.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:79f0::/32Route object only in RADB, TC. Add it in the RIR database for the space.636 of 636
AS-SET: not foundAS271337:AS-LIKENETPeeringDB names AS271337:AS-LIKENET; no IRR database read has it.

Route objects not announced

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