Network · data from 2026-11-12
AS46273 APOG-ALBANY - Apogee Telecom Inc.
Registry name: APOG-ALBANY - Apogee Telecom Inc., US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS46273, 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.
| 64.189.224.0/20 | No ROA | None | 673 100% |
| 69.80.160.0/20 | No ROA | None | 673 100% |
| 204.137.251.0/24 | No ROA | Other origin onlycovered by 204.137.248.0/21 | 673 100% |
| 204.137.248.0/21 | No ROA | Other IRR onlyRADB | 673 100% |
| 76.78.3.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 76.78.64.0/21 | No ROA | RIR databaseARIN, RADB | 673 100% |
| 76.78.200.0/24 | No ROA | RIR databaseARIN | 673 100% |
| 76.78.72.0/23 | Valid | RIR databaseARIN | 673 100% |
| 76.78.181.0/24 | Valid | RIR databaseARIN | 673 100% |
| 76.78.201.0/24 | Valid | RIR databaseARIN | 673 100% |
| 76.78.208.0/20 | Valid | RIR databaseARIN | 673 100% |
AS-SET
AS46273 isn't in PeeringDB, where networks name their AS-SET.
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 39 are in fix.csv.
- ROA: none7
- Route object: none3
- Route object: RIR1
- Route object: not announced28
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 64.189.224.0/20 | No ROA covers it. Add a ROA for AS46273, maxLength 20. |
| Route object: none | 64.189.224.0/20 | No route object for it. Add a route object with origin AS46273 in the RIR database for the space. |
| ROA: none | 69.80.160.0/20 | No ROA covers it. Add a ROA for AS46273, maxLength 20. |
| Route object: none | 69.80.160.0/20 | No route object for it. Add a route object with origin AS46273 in the RIR database for the space. |
| ROA: none | 204.137.251.0/24 | No ROA covers it. Add a ROA for AS46273, maxLength 24. |
| Route object: none | 204.137.251.0/24 | Route objects for it name AS399324. A route object for 204.137.248.0/21 with origin AS46273 covers it (filters allowing more-specifics accept it). Add a route object with origin AS46273 in the RIR database for the space. |
| ROA: none | 204.137.248.0/21 | No ROA covers it. Add a ROA for AS46273, maxLength 21. |
| Route object: RIR | 204.137.248.0/21 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 76.78.3.0/24 | No ROA covers it. Add a ROA for AS46273, maxLength 24. |
| ROA: none | 76.78.64.0/21 | No ROA covers it. Add a ROA for AS46273, maxLength 21. |
| ROA: none | 76.78.200.0/24 | No ROA covers it. Add a ROA for AS46273, maxLength 24. |
Route objects not announced
Route objects with origin AS46273 whose prefix no peer sees AS46273 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 64.189.80.0/21 | ARIN | No ROA |
| 64.189.96.0/24 | RADB | No ROA |
| 64.189.232.0/24 | ARIN | No ROA |
| 69.80.160.0/23 | ARIN | No ROA |
| 69.80.164.0/24 | ARIN | Invalid: origin |
| 69.80.165.0/24 | ARIN | No ROA |
| 69.80.166.0/23 | ARIN | No ROA |
| 69.80.169.0/24 | ARIN | No ROA |
| 69.80.171.0/24 | ARIN | No ROA |
| 69.80.172.0/24 | ARIN | No ROA |
| 69.80.173.0/24 | ARIN | No ROA |
| 69.80.175.0/24 | ARIN | No ROA |
| 76.78.2.0/23 | RADB | No ROA |
| 76.78.16.0/20 | RADB | No ROA |
| 76.78.32.0/20 | RADB | No ROA |
| 76.78.48.0/20 | RADB | No ROA |
| 76.78.60.0/23 | ARIN | No ROA |
| 76.78.63.0/24 | ARIN | No ROA |
| 76.78.72.0/21 | ARIN | No ROA |
| 76.78.228.0/23 | ARIN, RADB | No ROA |
| 147.129.0.0/16 | RADB | No ROA |
| 192.74.209.0/24 | RADB | No ROA |
| 192.231.234.0/24 | RADB | No ROA |
| 204.137.248.0/24 | ARIN | No ROA |
| 204.137.249.0/24 | ARIN | No ROA |
| 204.137.250.0/24 | ARIN | No ROA |
| 209.51.64.0/23 | RADB | No ROA |
| 209.51.65.128/26 | ARIN | 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.