Network · data from 2026-11-12
AS52781 Pertec Servicos de Telecomunicacoes
Registry name: AS52781 - Pertec Servicos de Telecomunicacoes ltda, BR · PeeringDB
31IPv4 routes
100.0% RPKI valid · 22.6% with a route object
7IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
24 with no route object for this origin
26Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS52781, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS52781, 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.200.48.0/21 | Valid | Nonecovered by 177.200.48.0/20 | 61 9%low visibility |
| 177.200.48.0/24 | Valid | Nonecovered by 177.200.48.0/23 | 61 9%low visibility |
| 177.200.49.0/24 | Valid | Nonecovered by 177.200.48.0/23 | 61 9%low visibility |
| 177.200.50.0/24 | Valid | Nonecovered by 177.200.50.0/23 | 61 9%low visibility |
| 177.200.51.0/24 | Valid | Nonecovered by 177.200.50.0/23 | 61 9%low visibility |
| 177.200.52.0/23 | Valid | Nonecovered by 177.200.52.0/22 | 61 9%low visibility |
| 177.200.52.0/24 | Valid | Nonecovered by 177.200.52.0/22 | 61 9%low visibility |
| 177.200.53.0/24 | Valid | Nonecovered by 177.200.52.0/22 | 61 9%low visibility |
| 177.200.54.0/23 | Valid | Nonecovered by 177.200.52.0/22 | 61 9%low visibility |
| 177.200.54.0/24 | Valid | Nonecovered by 177.200.52.0/22 | 61 9%low visibility |
| 177.200.55.0/24 | Valid | Nonecovered by 177.200.52.0/22 | 61 9%low visibility |
| 177.200.56.0/21 | Valid | Nonecovered by 177.200.48.0/20 | 61 9%low visibility |
| 177.200.56.0/22 | Valid | Nonecovered by 177.200.48.0/20 | 61 9%low visibility |
| 177.200.56.0/23 | Valid | Nonecovered by 177.200.48.0/20 | 61 9%low visibility |
| 177.200.56.0/24 | Valid | Nonecovered by 177.200.48.0/20 | 61 9%low visibility |
| 177.200.57.0/24 | Valid | Nonecovered by 177.200.48.0/20 | 61 9%low visibility |
| 177.200.58.0/23 | Valid | Nonecovered by 177.200.48.0/20 | 61 9%low visibility |
| 177.200.58.0/24 | Valid | Nonecovered by 177.200.48.0/20 | 61 9%low visibility |
| 177.200.59.0/24 | Valid | Nonecovered by 177.200.48.0/20 | 61 9%low visibility |
| 177.200.60.0/24 | Valid | Nonecovered by 177.200.60.0/23 | 61 9%low visibility |
| 177.200.61.0/24 | Valid | Nonecovered by 177.200.60.0/23 | 61 9%low visibility |
| 177.200.62.0/23 | Valid | Nonecovered by 177.200.60.0/22 | 61 9%low visibility |
| 177.200.62.0/24 | Valid | Nonecovered by 177.200.60.0/22 | 61 9%low visibility |
| 177.200.63.0/24 | Valid | Nonecovered by 177.200.60.0/22 | 61 9%low visibility |
| 177.200.48.0/20 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 177.200.48.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 177.200.48.0/23 | Valid | Other IRR onlyRADB | 672 100% |
| 177.200.60.0/22 | Valid | Other IRR onlyRADB | 672 100% |
| 177.200.50.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 2804:24d4::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 2804:24d4::/33 | Valid | Other IRR onlyRADB | 68 11% |
| 2804:24d4::/34 | Valid | Other IRR onlyRADB | 68 11% |
| 2804:24d4:4000::/34 | Valid | Other IRR onlyRADB | 68 11% |
| 2804:24d4:8000::/33 | Valid | Other IRR onlyRADB | 68 11% |
| 2804:24d4:8000::/34 | Valid | Other IRR onlyRADB | 68 11% |
| 2804:24d4:c000::/34 | Valid | Other IRR onlyRADB | 68 11% |
| 177.200.52.0/22 | Valid | Other IRR onlyRADB | 61 9%low visibility |
| 177.200.60.0/23 | Valid | Other IRR onlyRADB | 61 9%low visibility |
AS-SET
PeeringDB's irr_as_set for AS52781: AS52781:AS-ANNOUNCEMENTS. 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 (AS52781 isn't in the set, or no route object for AS52781 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.
| Name | Database | ASNs | Sets | AS52781 in it | Not covered |
|---|---|---|---|---|---|
| AS52781:AS-ANNOUNCEMENTS | TC | 1 | 2 | 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 38 are in fix.csv.
- Route object: none24
- Route object: RIR14
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 177.200.48.0/21 | No route object for it. A route object for 177.200.48.0/20 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.48.0/24 | No route object for it. A route object for 177.200.48.0/23 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.49.0/24 | No route object for it. A route object for 177.200.48.0/23 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.50.0/24 | No route object for it. A route object for 177.200.50.0/23 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.51.0/24 | No route object for it. A route object for 177.200.50.0/23 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.52.0/23 | No route object for it. A route object for 177.200.52.0/22 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.52.0/24 | No route object for it. A route object for 177.200.52.0/22 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.53.0/24 | No route object for it. A route object for 177.200.52.0/22 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.54.0/23 | No route object for it. A route object for 177.200.52.0/22 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.54.0/24 | No route object for it. A route object for 177.200.52.0/22 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.55.0/24 | No route object for it. A route object for 177.200.52.0/22 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.56.0/21 | No route object for it. A route object for 177.200.48.0/20 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.56.0/22 | No route object for it. A route object for 177.200.48.0/20 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.56.0/23 | No route object for it. A route object for 177.200.48.0/20 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.56.0/24 | No route object for it. A route object for 177.200.48.0/20 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.57.0/24 | No route object for it. A route object for 177.200.48.0/20 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.58.0/23 | No route object for it. A route object for 177.200.48.0/20 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.58.0/24 | No route object for it. A route object for 177.200.48.0/20 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.59.0/24 | No route object for it. A route object for 177.200.48.0/20 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.60.0/24 | No route object for it. A route object for 177.200.60.0/23 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.61.0/24 | No route object for it. A route object for 177.200.60.0/23 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.62.0/23 | No route object for it. A route object for 177.200.60.0/22 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.62.0/24 | No route object for it. A route object for 177.200.60.0/22 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: none | 177.200.63.0/24 | No route object for it. A route object for 177.200.60.0/22 with origin AS52781 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52781 in the RIR database for the space. |
| Route object: RIR | 177.200.48.0/20 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.200.48.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.200.48.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.200.60.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.200.50.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:24d4::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:24d4::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:24d4::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:24d4:4000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:24d4:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:24d4:8000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:24d4:c000::/34 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.200.52.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 177.200.60.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Every route object with origin AS52781 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.