Network · data from 2026-11-12
AS61673 BR7 TELECOM
Registry name: AS61673 - BR7 TELECOM, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61673, 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.
| 170.245.192.0/22 | Valid | Other IRR onlyALTDB, RADB | 672 100% |
| 131.108.120.0/22 | Valid | Other IRR onlyALTDB | 671 100% |
| 2804:1cc0::/32 | Valid | Other IRR onlyALTDB | 635 100% |
| 2804:1cc0::/33 | Valid | Other IRR onlyALTDB | 16 3%low visibility |
| 2804:1cc0:8000::/33 | Valid | Other IRR onlyALTDB | 16 3%low visibility |
| 131.108.120.0/23 | Valid | Other IRR onlyALTDB | 12 2%low visibility |
| 131.108.122.0/23 | Valid | Other IRR onlyALTDB | 12 2%low visibility |
| 170.245.192.0/23 | Valid | Other IRR onlyALTDB | 12 2%low visibility |
| 170.245.194.0/23 | Valid | Other IRR onlyALTDB | 12 2%low visibility |
AS-SET
PeeringDB's irr_as_set for AS61673: AS61673:AS-CONE. 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 (AS61673 isn't in the set, or no route object for AS61673 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 | AS61673 in it | Not covered |
|---|---|---|---|---|---|
| AS61673:AS-CONE | ALTDB | 1 | 1 | 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 17 are in fix.csv.
- Route object: RIR9
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 170.245.192.0/22 | Route object only in ALTDB, RADB. Add it in the RIR database for the space. |
| Route object: RIR | 131.108.120.0/22 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1cc0::/32 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1cc0::/33 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1cc0:8000::/33 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 131.108.120.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 131.108.122.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.192.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| Route object: RIR | 170.245.194.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61673 whose prefix no peer sees AS61673 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 131.108.120.0/24 | ALTDB | Valid |
| 131.108.121.0/24 | ALTDB | Valid |
| 131.108.122.0/24 | ALTDB | Valid |
| 131.108.123.0/24 | ALTDB | Valid |
| 170.245.192.0/24 | ALTDB | Valid |
| 170.245.193.0/24 | ALTDB | Valid |
| 170.245.194.0/24 | ALTDB | Valid |
| 170.245.195.0/24 | ALTDB | 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.