Network · data from 2026-11-12
AS15165 Mutual Telephone Company
Registry name: MTC-LRCOMMUNICATIONS - Mutual Telephone Company, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15165, 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.
| 50.115.144.0/23 | No ROA | Other IRR onlyALTDB | 670 100% |
| 50.115.146.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 50.115.156.0/24 | No ROA | RIR databaseARIN | 670 100% |
| 63.245.137.0/24 | Valid | RIR databaseARIN | 670 100% |
| 63.245.140.0/23 | Valid | RIR databaseARIN | 670 100% |
| 63.245.153.0/24 | Valid | RIR databaseARIN | 670 100% |
| 63.245.156.0/22 | Valid | RIR databaseARIN | 670 100% |
| 63.245.160.0/22 | Valid | RIR databaseARIN | 670 100% |
| 63.245.169.0/24 | Valid | RIR databaseARIN | 670 100% |
| 63.245.175.0/24 | Valid | RIR databaseARIN | 670 100% |
| 63.245.184.0/24 | Valid | RIR databaseARIN | 670 100% |
| 63.245.187.0/24 | Valid | RIR databaseARIN | 670 100% |
| 2607:4e80::/32 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS15165: AS-MTC. 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 (AS15165 isn't in the set, or no route object for AS15165 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 | AS15165 in it | Not covered |
|---|---|---|---|---|---|
| AS-MTC | ARIN | 4 | 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 10 are in fix.csv.
- ROA: none3
- Route object: RIR1
- Route object: not announced6
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 50.115.144.0/23 | No ROA covers it. Add a ROA for AS15165, maxLength 23. |
| Route object: RIR | 50.115.144.0/23 | Route object only in ALTDB. Add it in the RIR database for the space. |
| ROA: none | 50.115.146.0/24 | No ROA covers it. Add a ROA for AS15165, maxLength 24. |
| ROA: none | 50.115.156.0/24 | No ROA covers it. Add a ROA for AS15165, maxLength 24. |
Route objects not announced
Route objects with origin AS15165 whose prefix no peer sees AS15165 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 50.115.144.0/24 | ARIN | No ROA |
| 50.115.145.0/24 | ARIN | No ROA |
| 63.245.156.0/24 | ARIN | Invalid: maxLength |
| 63.245.157.0/24 | ARIN | Invalid: maxLength |
| 63.245.158.0/24 | ARIN | Invalid: maxLength |
| 63.245.159.0/24 | ARIN | Invalid: maxLength |
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.