Network · data from 2026-11-12
AS53123 Power Telecomunicações
Registry name: AS53123 - Power Telecomunicacoes Ltda. - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS53123, 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.
| 187.111.192.0/21 | Valid | Other IRR onlyTC | 672 100% |
| 187.111.197.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 187.111.199.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 187.111.206.0/24 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 187.111.192.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 187.111.193.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 187.111.194.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 187.111.204.0/24 | Valid | Other IRR onlyRADB, TC | 670 100% |
| 187.111.192.0/22 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 187.111.196.0/22 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 187.111.200.0/22 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 187.111.204.0/22 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 187.111.196.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 187.111.198.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 187.111.200.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 187.111.202.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 187.111.204.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 187.111.206.0/23 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 187.111.192.0/23 | Valid | Other IRR onlyRADB, TC | 666 99% |
| 187.111.194.0/23 | Valid | Other IRR onlyRADB, TC | 666 99% |
| 187.111.200.0/23 | Valid | Other IRR onlyRADB, TC | 666 99% |
| 2804:6478::/32 | Valid | Other IRR onlyRADB, TC | 636 100% |
| 2804:6478::/33 | Valid | Other IRR onlyTC | 636 100% |
| 187.111.202.0/24 | Valid | Other IRR onlyRADB, TC | 2 0%low visibility |
| 187.111.195.0/24 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
| 187.111.196.0/24 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
| 187.111.198.0/24 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
| 187.111.201.0/24 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
| 187.111.203.0/24 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
| 187.111.205.0/24 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
| 187.111.207.0/24 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS53123: AS53123:AS-POWET-TELECOM-ALL. 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 (AS53123 isn't in the set, or no route object for AS53123 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 | AS53123 in it | Not covered |
|---|---|---|---|---|---|
| AS53123:AS-POWET-TELECOM-ALL | TC | 2 | 3 | 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 53 are in fix.csv.
- Route object: RIR31
- Route object: not announced22
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 187.111.192.0/21 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.197.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.199.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.206.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.192.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.193.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.194.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.204.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.192.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.196.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.200.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.204.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.196.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.198.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.200.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.202.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.204.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.206.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.192.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.194.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.200.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6478::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6478::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.202.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.195.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.196.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.198.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.201.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.203.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.205.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 187.111.207.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS53123 whose prefix no peer sees AS53123 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 187.111.192.0/20 | RADB, TC | Valid |
| 187.111.200.0/21 | TC | Valid |
| 2804:6478::/34 | TC | Valid |
| 2804:6478:1000::/36 | TC | Valid |
| 2804:6478:2000::/36 | TC | Valid |
| 2804:6478:3000::/36 | TC | Valid |
| 2804:6478:4000::/34 | TC | Valid |
| 2804:6478:4000::/36 | TC | Valid |
| 2804:6478:5000::/36 | TC | Valid |
| 2804:6478:6000::/36 | TC | Valid |
| 2804:6478:7000::/36 | TC | Valid |
| 2804:6478:8000::/33 | TC | Valid |
| 2804:6478:8000::/34 | TC | Valid |
| 2804:6478:8000::/36 | TC | Valid |
| 2804:6478:9000::/36 | TC | Valid |
| 2804:6478:a000::/36 | TC | Valid |
| 2804:6478:b000::/36 | TC | Valid |
| 2804:6478:c000::/34 | TC | Valid |
| 2804:6478:c000::/36 | TC | Valid |
| 2804:6478:d000::/36 | TC | Valid |
| 2804:6478:e000::/36 | TC | Valid |
| 2804:6478:f000::/36 | TC | Valid |
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.