Network · data from 2026-11-12
AS52583 Asstelecom telecomunicação
Registry name: AS52583 - Asstelecom telecomunicacao Ltda me, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS52583, 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.
| 2804:d00:c000::/35 | Valid | Nonecovered by 2804:d00:c000::/34 | 628 99% |
| 177.87.170.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 177.87.171.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 177.87.172.0/23 | Valid | Other IRR onlyTC | 668 99% |
| 177.87.172.0/24 | Valid | Other IRR onlyRADB, TC | 668 99% |
| 177.87.174.0/24 | Valid | Other IRR onlyRADB, TC | 667 99% |
| 177.87.168.0/23 | Valid | Other IRR onlyTC | 645 96% |
| 2804:d00::/34 | Valid | Other IRR onlyTC | 631 99% |
| 177.87.173.0/24 | Valid | Other IRR onlyRADB, TC | 1 0%low visibility |
AS-SET
AS52583's PeeringDB record names no AS-SET.
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 23 are in fix.csv.
- Route object: none1
- Route object: RIR8
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:d00:c000::/35 | No route object for it. A route object for 2804:d00:c000::/34 with origin AS52583 covers it (filters allowing more-specifics accept it). Add a route object with origin AS52583 in the RIR database for the space. |
| Route object: RIR | 177.87.170.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.87.171.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.87.172.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.87.172.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.87.174.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.87.168.0/23 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:d00::/34 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 177.87.173.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 AS52583 whose prefix no peer sees AS52583 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 177.87.168.0/21 | RADB, TC | Valid |
| 177.87.168.0/22 | TC | Valid |
| 177.87.168.0/24 | RADB, TC | Valid |
| 177.87.169.0/24 | RADB, TC | Valid |
| 177.87.170.0/23 | TC | Valid |
| 177.87.172.0/22 | TC | Valid |
| 177.87.174.0/23 | TC | Valid |
| 177.87.175.0/24 | RADB, TC | Valid |
| 2804:d00::/32 | RADB, TC | Valid |
| 2804:d00::/33 | TC | Valid |
| 2804:d00:4000::/34 | TC | Valid |
| 2804:d00:8000::/33 | TC | Valid |
| 2804:d00:8000::/34 | TC | Valid |
| 2804:d00:c000::/34 | 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.