bgpreport

Network · data from 2026-11-12

AS262851 Plim Telecom

Registry name: AS262851 - PLIM TELECOMUNICACOES LTDA-ME, BR · PeeringDB

9IPv4 routes 0.0% RPKI valid · 55.6% with a route object
2IPv6 routes 0.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
11No ROA 5 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS262851, seen from no peer

Announced routes

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

177.10.144.0/22 No ROA Nonecovered by 177.10.144.0/21 671 100% 66
177.10.148.0/22 No ROA Nonecovered by 177.10.144.0/21 671 100% 66
191.242.112.0/24 No ROA Nonecovered by 191.242.112.0/20 671 100% 66
38.225.43.0/24 No ROA None 670 100% 67
2804:452c::/32 No ROA Other origin only 584 92% 67
177.10.144.0/21 No ROA Other IRR onlyTC 672 100% 66
177.10.144.0/24 No ROA Other IRR onlyTC 672 100% 66
177.86.144.0/21 No ROA Other IRR onlyRADB, TC 672 100% 66
191.240.200.0/21 No ROA Other IRR onlyRADB, TC 672 100% 66
191.242.112.0/20 No ROA Other IRR onlyTC 672 100% 66
2804:1270::/32 No ROA Other IRR onlyRADB, TC 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS262851: AS262851:AS-PLIM. 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 (AS262851 isn't in the set, or no route object for AS262851 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 objectsAS262851 in itNot covered
AS262851:AS-PLIM TC 10188 Yes 2

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

  • ROA: none11
  • Route object: none5
  • Route object: RIR6
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none177.10.144.0/22No ROA covers it. Add a ROA for AS262851, maxLength 22.671 of 673
Route object: none177.10.144.0/22No route object for it. A route object for 177.10.144.0/21 with origin AS262851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262851 in the RIR database for the space.671 of 673
ROA: none177.10.148.0/22No ROA covers it. Add a ROA for AS262851, maxLength 22.671 of 673
Route object: none177.10.148.0/22No route object for it. A route object for 177.10.144.0/21 with origin AS262851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262851 in the RIR database for the space.671 of 673
ROA: none191.242.112.0/24No ROA covers it. Add a ROA for AS262851, maxLength 24.671 of 673
Route object: none191.242.112.0/24No route object for it. A route object for 191.242.112.0/20 with origin AS262851 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262851 in the RIR database for the space.671 of 673
ROA: none38.225.43.0/24No ROA covers it. Add a ROA for AS262851, maxLength 24.670 of 673
Route object: none38.225.43.0/24No route object for it. Add a route object with origin AS262851 in the RIR database for the space.670 of 673
ROA: none2804:452c::/32No ROA covers it. Add a ROA for AS262851, maxLength 32.584 of 636
Route object: none2804:452c::/32Route objects for it name AS262529. Add a route object with origin AS262851 in the RIR database for the space.584 of 636
ROA: none177.10.144.0/21No ROA covers it. Add a ROA for AS262851, maxLength 21.672 of 673
Route object: RIR177.10.144.0/21Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none177.10.144.0/24No ROA covers it. Add a ROA for AS262851, maxLength 24.672 of 673
Route object: RIR177.10.144.0/24Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none177.86.144.0/21No ROA covers it. Add a ROA for AS262851, maxLength 21.672 of 673
Route object: RIR177.86.144.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none191.240.200.0/21No ROA covers it. Add a ROA for AS262851, maxLength 21.672 of 673
Route object: RIR191.240.200.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
ROA: none191.242.112.0/20No ROA covers it. Add a ROA for AS262851, maxLength 20.672 of 673
Route object: RIR191.242.112.0/20Route object only in TC. Add it in the RIR database for the space.672 of 673
ROA: none2804:1270::/32No ROA covers it. Add a ROA for AS262851, maxLength 32.635 of 636
Route object: RIR2804:1270::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

177.10.148.0/24TCNo ROA
177.10.149.0/24TCNo 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.