Network · data from 2026-11-12
AS15267 702 Communications
Registry name: 702COM - 702 Communications, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS15267, 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.
| 65.183.224.0/19 | Valid | Other IRR onlyRADB | 670 100% |
| 65.183.224.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 65.183.240.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 68.69.224.0/19 | Valid | Other IRR onlyRADB | 670 100% |
| 68.69.224.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 68.69.240.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 72.18.112.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 72.18.112.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 72.18.114.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 72.18.116.0/23 | Valid | Other IRR onlyRADB | 670 100% |
| 72.18.116.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 72.18.117.0/24 | Valid | Other IRR onlyRADB | 670 100% |
| 72.18.120.0/21 | Valid | Other IRR onlyRADB | 670 100% |
| 72.18.120.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 72.18.124.0/22 | Valid | Other IRR onlyRADB | 670 100% |
| 206.188.160.0/19 | Valid | Other IRR onlyRADB | 670 100% |
| 206.188.160.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 206.188.176.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 216.239.0.0/19 | Valid | Other IRR onlyRADB | 670 100% |
| 216.239.0.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 216.239.16.0/20 | Valid | Other IRR onlyRADB | 670 100% |
| 2605:3400::/32 | Valid | Other IRR onlyRADB | 635 100% |
| 2605:3400::/33 | Valid | Other IRR onlyRADB | 635 100% |
| 2605:3400:8000::/33 | Valid | Other IRR onlyRADB | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS15267: RADB::AS15267:AS-ALL. 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 (AS15267 isn't in the set, or no route object for AS15267 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 | AS15267 in it | Not covered |
|---|---|---|---|---|---|
| RADB::AS15267:AS-ALL | RADB | 7 | 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 32 are in fix.csv.
- Route object: RIR24
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 65.183.224.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 65.183.224.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 65.183.240.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 68.69.224.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 68.69.224.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 68.69.240.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 72.18.112.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 72.18.112.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 72.18.114.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 72.18.116.0/23 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 72.18.116.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 72.18.117.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 72.18.120.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 72.18.120.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 72.18.124.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.188.160.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.188.160.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 206.188.176.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.239.0.0/19 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.239.0.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 216.239.16.0/20 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2605:3400::/32 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2605:3400::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2605:3400:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS15267 whose prefix no peer sees AS15267 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 72.18.112.0/20 | RADB | No ROA |
| 72.18.112.0/21 | RADB | No ROA |
| 72.18.116.0/22 | RADB | No ROA |
| 138.129.24.0/21 | ARIN, RADB | Valid |
| 138.129.30.0/24 | ARIN, RADB | Valid |
| 138.129.31.0/24 | ARIN, RADB | Valid |
| 138.129.48.0/20 | ARIN | Valid |
| 2001:470:345::/48 | ARIN | 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.