Network · data from 2026-11-12
AS61573 IP Telecom (BR)
Registry name: AS61573 - IP TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61573, 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.
| 138.122.60.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 2804:25e4::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 2804:25e4:703::/48 | Valid | Other IRR onlyRADB, TC | 633 100% |
| 138.122.60.0/24 | Valid | Other IRR onlyRADB, TC | 17 3%low visibility |
| 138.122.61.0/24 | Valid | Other IRR onlyRADB, TC | 17 3%low visibility |
| 138.122.62.0/24 | Valid | Other IRR onlyRADB, TC | 17 3%low visibility |
| 138.122.63.0/24 | Valid | Other IRR onlyRADB, TC | 17 3%low visibility |
| 2804:25e4::/40 | Valid | Other IRR onlyRADB, TC | 8 1%low visibility |
| 2804:25e4:300::/48 | Valid | Other IRR onlyRADB, TC | 8 1%low visibility |
| 2804:25e4:500::/40 | Valid | Other IRR onlyRADB, TC | 8 1%low visibility |
| 2804:25e4:600::/48 | Valid | Other IRR onlyRADB, TC | 8 1%low visibility |
| 2804:25e4:700::/40 | Valid | Other IRR onlyRADB, TC | 8 1%low visibility |
| 2804:25e4:700::/48 | Valid | Other IRR onlyRADB, TC | 8 1%low visibility |
| 2804:25e4:706::/48 | Valid | Other IRR onlyRADB, TC | 8 1%low visibility |
| 2804:25e4:709::/48 | Valid | Other IRR onlyRADB | 8 1%low visibility |
| 2804:25e4:70a::/48 | Valid | Other IRR onlyRADB | 8 1%low visibility |
| 2804:25e4:70b::/48 | Valid | Other IRR onlyRADB | 8 1%low visibility |
| 2804:25e4:70d::/48 | Valid | Other IRR onlyRADB | 8 1%low visibility |
| 2804:25e4:800::/40 | Valid | Other IRR onlyRADB, TC | 8 1%low visibility |
| 2804:25e4:1000::/40 | Valid | Other IRR onlyRADB | 3 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS61573: AS61573:AS-CUSTOMERS. 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 (AS61573 isn't in the set, or no route object for AS61573 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 | AS61573 in it | Not covered |
|---|---|---|---|---|---|
| AS61573:AS-CUSTOMERS | RADB | 23 | 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 34 are in fix.csv.
- Route object: RIR20
- Route object: not announced14
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 138.122.60.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:703::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.122.60.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.122.61.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.122.62.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 138.122.63.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4::/40 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:300::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:500::/40 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:600::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:700::/40 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:700::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:706::/48 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:709::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:70a::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:70b::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:70d::/48 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:800::/40 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:25e4:1000::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61573 whose prefix no peer sees AS61573 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 138.122.60.0/23 | RADB, TC | Valid |
| 138.122.62.0/23 | RADB | Valid |
| 156.227.48.0/20 | RADB | No ROA |
| 2804:25e4:100::/40 | RADB, TC | Valid |
| 2804:25e4:200::/40 | RADB, TC | Valid |
| 2804:25e4:400::/40 | RADB, TC | Valid |
| 2804:25e4:701::/48 | RADB, TC | Valid |
| 2804:25e4:702::/48 | RADB, TC | Valid |
| 2804:25e4:704::/48 | RADB, TC | Valid |
| 2804:25e4:705::/48 | RADB | Valid |
| 2804:25e4:707::/48 | TC | Valid |
| 2804:25e4:70c::/48 | RADB | Valid |
| 2804:25e4:a00::/40 | RADB | Valid |
| 2804:2eb4::/32 | 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.