bgpreport

Network · data from 2026-11-12

AS270901 Liker Telecomunicacoes

Registry name: AS270901 - Liker Telecomunicacoes Ltda, BR · PeeringDB

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

Announced routes

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

189.50.32.0/22 No ROA Other IRR onlyRADB, TC 672 100% 67
189.50.32.0/23 No ROA Other IRR onlyTC 670 100% 67
189.50.34.0/23 No ROA Other IRR onlyTC 670 100% 67
2804:7330::/32 No ROA Other IRR onlyRADB, TC 633 100% 67
189.50.32.0/24 No ROA Other IRR onlyTC 10 1%low visibility 5
189.50.34.0/24 No ROA Other IRR onlyRADB, TC 10 1%low visibility 5
2804:7330::/33 No ROA Other IRR onlyRADB, TC 9 1%low visibility 5
2804:7330::/34 No ROA Other IRR onlyRADB, TC 9 1%low visibility 5
2804:7330:4000::/34 No ROA Other IRR onlyRADB, TC 9 1%low visibility 5
2804:7330:8000::/33 No ROA Other IRR onlyTC 9 1%low visibility 5
2804:7330:8000::/34 No ROA Other IRR onlyRADB, TC 9 1%low visibility 5
2804:7330:c000::/34 No ROA Other IRR onlyTC 9 1%low visibility 5
189.50.33.0/24 No ROA Other IRR onlyTC 2 0%low visibility 2
189.50.35.0/24 No ROA Other IRR onlyTC 2 0%low visibility 2

AS-SET

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

  • ROA: none14
  • Route object: RIR14
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none189.50.32.0/22No ROA covers it. Add a ROA for AS270901, maxLength 22.672 of 673
Route object: RIR189.50.32.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none189.50.32.0/23No ROA covers it. Add a ROA for AS270901, maxLength 23.670 of 673
Route object: RIR189.50.32.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none189.50.34.0/23No ROA covers it. Add a ROA for AS270901, maxLength 23.670 of 673
Route object: RIR189.50.34.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none2804:7330::/32No ROA covers it. Add a ROA for AS270901, maxLength 32.633 of 636
Route object: RIR2804:7330::/32Route object only in RADB, TC. Add it in the RIR database for the space.633 of 636
ROA: none189.50.32.0/24No ROA covers it. Add a ROA for AS270901, maxLength 24.10 of 673
Route object: RIR189.50.32.0/24Route object only in TC. Add it in the RIR database for the space.10 of 673
ROA: none189.50.34.0/24No ROA covers it. Add a ROA for AS270901, maxLength 24.10 of 673
Route object: RIR189.50.34.0/24Route object only in RADB, TC. Add it in the RIR database for the space.10 of 673
ROA: none2804:7330::/33No ROA covers it. Add a ROA for AS270901, maxLength 33.9 of 636
Route object: RIR2804:7330::/33Route object only in RADB, TC. Add it in the RIR database for the space.9 of 636
ROA: none2804:7330::/34No ROA covers it. Add a ROA for AS270901, maxLength 34.9 of 636
Route object: RIR2804:7330::/34Route object only in RADB, TC. Add it in the RIR database for the space.9 of 636
ROA: none2804:7330:4000::/34No ROA covers it. Add a ROA for AS270901, maxLength 34.9 of 636
Route object: RIR2804:7330:4000::/34Route object only in RADB, TC. Add it in the RIR database for the space.9 of 636
ROA: none2804:7330:8000::/33No ROA covers it. Add a ROA for AS270901, maxLength 33.9 of 636
Route object: RIR2804:7330:8000::/33Route object only in TC. Add it in the RIR database for the space.9 of 636
ROA: none2804:7330:8000::/34No ROA covers it. Add a ROA for AS270901, maxLength 34.9 of 636
Route object: RIR2804:7330:8000::/34Route object only in RADB, TC. Add it in the RIR database for the space.9 of 636
ROA: none2804:7330:c000::/34No ROA covers it. Add a ROA for AS270901, maxLength 34.9 of 636
Route object: RIR2804:7330:c000::/34Route object only in TC. Add it in the RIR database for the space.9 of 636
ROA: none189.50.33.0/24No ROA covers it. Add a ROA for AS270901, maxLength 24.2 of 673
Route object: RIR189.50.33.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
ROA: none189.50.35.0/24No ROA covers it. Add a ROA for AS270901, maxLength 24.2 of 673
Route object: RIR189.50.35.0/24Route object only in TC. Add it in the RIR database for the space.2 of 673
AS-SET: not foundAS270901:AS-LIKERTELECOMPeeringDB names AS270901:AS-LIKERTELECOM; no IRR database read has it.

Route objects not announced

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