bgpreport

Network · data from 2026-11-12

AS52988 Plena Telecom

Registry name: AS52988 - PLENA TELECOM, BR · PeeringDB

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

Announced routes

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

168.227.189.0/24 No ROA Other origin only 668 99% 67
177.54.96.0/20 No ROA Other IRR onlyRADB 668 99% 67
179.109.48.0/21 No ROA Other IRR onlyRADB 668 99% 67
2804:498::/32 No ROA Other IRR onlyRADB 633 100% 67

AS-SET

PeeringDB's irr_as_set for AS52988: AS-PLENA. 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 (AS52988 isn't in the set, or no route object for AS52988 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 objectsAS52988 in itNot covered
AS-PLENA RADB 377317 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 11 are in fix.csv.

  • ROA: none4
  • Route object: none1
  • Route object: RIR3
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none168.227.189.0/24No ROA covers it. Add a ROA for AS52988, maxLength 24.668 of 673
Route object: none168.227.189.0/24Route objects for it name AS264893. Add a route object with origin AS52988 in the RIR database for the space.668 of 673
ROA: none177.54.96.0/20No ROA covers it. Add a ROA for AS52988, maxLength 20.668 of 673
Route object: RIR177.54.96.0/20Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none179.109.48.0/21No ROA covers it. Add a ROA for AS52988, maxLength 21.668 of 673
Route object: RIR179.109.48.0/21Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none2804:498::/32No ROA covers it. Add a ROA for AS52988, maxLength 32.633 of 636
Route object: RIR2804:498::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

177.54.97.0/24RADBNo ROA
177.54.97.49/32RADBNo ROA
177.54.101.0/24RADBNo 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.