Network · data from 2026-11-12
AS61716 Central Telecom
Registry name: AS61716 - Rede Tupiniquim de Comunicacao Ltda - ME, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61716, 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.
| 131.72.20.0/22 | No ROA | Other IRR onlyRADB, TC | 666 99% |
| 2804:1b38::/32 | No ROA | Other IRR onlyRADB, TC | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS61716: AS61716:AS-CENTRAL. 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 (AS61716 isn't in the set, or no route object for AS61716 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 | AS61716 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS61716:AS-CENTRAL | In no IRR database read today. | |||||
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 17 are in fix.csv.
- ROA: none2
- Route object: RIR2
- AS-SET: not found1
- Route object: not announced12
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 131.72.20.0/22 | No ROA covers it. Add a ROA for AS61716, maxLength 22. |
| Route object: RIR | 131.72.20.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| ROA: none | 2804:1b38::/32 | No ROA covers it. Add a ROA for AS61716, maxLength 32. |
| Route object: RIR | 2804:1b38::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS61716:AS-CENTRAL | PeeringDB names AS61716:AS-CENTRAL; no IRR database read has it. |
Route objects not announced
Route objects with origin AS61716 whose prefix no peer sees AS61716 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.72.20.0/23 | RADB | No ROA |
| 131.72.20.0/24 | RADB | No ROA |
| 131.72.21.0/24 | RADB | No ROA |
| 131.72.22.0/23 | RADB | No ROA |
| 131.72.22.0/24 | RADB | No ROA |
| 131.72.23.0/24 | RADB | No ROA |
| 2804:1b38::/33 | RADB | No ROA |
| 2804:1b38::/34 | RADB | No ROA |
| 2804:1b38:4000::/34 | RADB | No ROA |
| 2804:1b38:8000::/33 | RADB | No ROA |
| 2804:1b38:8000::/34 | RADB | No ROA |
| 2804:1b38:c000::/34 | RADB | No 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.