bgpreport

Network · data from 2026-11-12

AS52947 PARAOPEBANET

Registry name: AS52947 - PARAOPEBANET PROVEDOR LTDA, BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS52947, 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.197.16.0/22 Valid Other IRR onlyRADB, TC 672 100% 66
177.38.136.0/21 Valid Other IRR onlyRADB, TC 672 100% 66
177.38.136.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
177.38.137.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
177.38.138.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
177.38.139.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
177.38.140.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
177.38.141.0/24 Valid Other IRR onlyRADB, TC 670 100% 66
177.38.142.0/23 Valid Other IRR onlyRADB, TC 665 99% 66
177.38.142.0/24 Valid Other IRR onlyRADB, TC 664 99% 67
177.38.143.0/24 Valid Other IRR onlyRADB, TC 664 99% 67
2804:1df4::/32 Valid Other IRR onlyRADB, TC 635 100% 67
2804:1df4::/34 Valid Other IRR onlyRADB 635 100% 67
2804:1df4:c000::/34 Valid Other IRR onlyRADB 635 100% 67
168.197.16.0/24 Valid Other IRR onlyRADB, TC 198 29% 55
168.197.17.0/24 Valid Other IRR onlyRADB, TC 198 29% 55
168.197.18.0/24 Valid Other IRR onlyRADB, TC 198 29% 55
168.197.19.0/24 Valid Other IRR onlyRADB, TC 198 29% 55

AS-SET

PeeringDB's irr_as_set for AS52947: AS52947:AS-PARAOPEBANET. 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 (AS52947 isn't in the set, or no route object for AS52947 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 objectsAS52947 in itNot covered
AS52947:AS-PARAOPEBANET TC 2326 Yes 0

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

  • Route object: RIR18
ChangePrefix or setDetailFull-table peers
Route object: RIR168.197.16.0/22Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.136.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673
Route object: RIR177.38.136.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.38.137.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.38.138.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.38.139.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.38.140.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.38.141.0/24Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.38.142.0/23Route object only in RADB, TC. Add it in the RIR database for the space.665 of 673
Route object: RIR177.38.142.0/24Route object only in RADB, TC. Add it in the RIR database for the space.664 of 673
Route object: RIR177.38.143.0/24Route object only in RADB, TC. Add it in the RIR database for the space.664 of 673
Route object: RIR2804:1df4::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1df4::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1df4:c000::/34Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR168.197.16.0/24Route object only in RADB, TC. Add it in the RIR database for the space.198 of 673
Route object: RIR168.197.17.0/24Route object only in RADB, TC. Add it in the RIR database for the space.198 of 673
Route object: RIR168.197.18.0/24Route object only in RADB, TC. Add it in the RIR database for the space.198 of 673
Route object: RIR168.197.19.0/24Route object only in RADB, TC. Add it in the RIR database for the space.198 of 673

Route objects not announced

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