Network · data from 2026-11-12
AS39153 Setel
Registry name: CO-TPTEL-AS1 JOINT-STOCK COMPANY "TELEPORT TELECOM", RU · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS39153, 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.
| 80.248.80.0/20 | No ROA | RIR databaseRIPE | 671 100% |
| 80.253.16.0/20 | No ROA | RIR databaseRIPE | 671 100% |
| 109.71.192.0/21 | No ROA | RIR databaseRIPE | 671 100% |
| 185.39.132.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 2a00:4500::/32 | No ROA | RIR databaseRIPE | 634 100% |
| 2a00:5d00::/32 | No ROA | RIR databaseRIPE | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS39153: AS-SETEL. 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 (AS39153 isn't in the set, or no route object for AS39153 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 | AS39153 in it | Not covered |
|---|---|---|---|---|---|
| AS-SETEL | RIPElists itself further down1 member set in no database: AS-PS-NET | 67 | 13 | 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 8 are in fix.csv.
- ROA: none6
- AS-SET: missing member1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 80.248.80.0/20 | No ROA covers it. Add a ROA for AS39153, maxLength 20. |
| ROA: none | 80.253.16.0/20 | No ROA covers it. Add a ROA for AS39153, maxLength 20. |
| ROA: none | 109.71.192.0/21 | No ROA covers it. Add a ROA for AS39153, maxLength 21. |
| ROA: none | 185.39.132.0/22 | No ROA covers it. Add a ROA for AS39153, maxLength 22. |
| ROA: none | 2a00:4500::/32 | No ROA covers it. Add a ROA for AS39153, maxLength 32. |
| ROA: none | 2a00:5d00::/32 | No ROA covers it. Add a ROA for AS39153, maxLength 32. |
| AS-SET: missing member | AS-SETEL | AS-SETEL (RIPE) lists AS-PS-NET; no IRR database read has it. |
Route objects not announced
Route objects with origin AS39153 whose prefix no peer sees AS39153 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 80.248.94.0/24 | RIPE | 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.