Network · data from 2026-11-12
AS393294 MEGATEL-NETCOM - Megatel Netcom Corporation
Registry name: MEGATEL-NETCOM - Megatel Netcom Corporation, US · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS393294, 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.
| 2602:2d8:2::/48 | No ROA | Nonecovered by 2602:2d8::/40 | 635 100% |
| 38.77.248.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 38.102.165.0/24 | No ROA | Other IRR onlyRADB | 672 100% |
| 2602:2d8::/40 | No ROA | Other IRR onlyRADB | 635 100% |
| 45.199.161.0/24 | No ROA | RIR databaseAFRINIC, RADB | 671 100% |
| 45.199.162.0/24 | No ROA | RIR databaseAFRINIC, RADB | 671 100% |
| 45.199.163.0/24 | No ROA | RIR databaseAFRINIC, RADB | 671 100% |
| 45.199.165.0/24 | No ROA | RIR databaseAFRINIC, RADB | 671 100% |
| 45.199.166.0/24 | No ROA | RIR databaseAFRINIC, RADB | 671 100% |
| 45.199.167.0/24 | No ROA | RIR databaseAFRINIC, RADB | 671 100% |
| 45.199.168.0/24 | No ROA | RIR databaseAFRINIC, RADB | 671 100% |
| 45.199.169.0/24 | Valid | RIR databaseAFRINIC, RADB | 671 100% |
AS-SET
AS393294 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 23 are in fix.csv.
- ROA: none11
- Route object: none1
- Route object: RIR3
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2602:2d8:2::/48 | No ROA covers it. Add a ROA for AS393294, maxLength 48. |
| Route object: none | 2602:2d8:2::/48 | No route object for it. A route object for 2602:2d8::/40 with origin AS393294 covers it (filters allowing more-specifics accept it). Add a route object with origin AS393294 in the RIR database for the space. |
| ROA: none | 38.77.248.0/24 | No ROA covers it. Add a ROA for AS393294, maxLength 24. |
| Route object: RIR | 38.77.248.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 38.102.165.0/24 | No ROA covers it. Add a ROA for AS393294, maxLength 24. |
| Route object: RIR | 38.102.165.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 2602:2d8::/40 | No ROA covers it. Add a ROA for AS393294, maxLength 40. |
| Route object: RIR | 2602:2d8::/40 | Route object only in RADB. Add it in the RIR database for the space. |
| ROA: none | 45.199.161.0/24 | No ROA covers it. Add a ROA for AS393294, maxLength 24. |
| ROA: none | 45.199.162.0/24 | No ROA covers it. Add a ROA for AS393294, maxLength 24. |
| ROA: none | 45.199.163.0/24 | No ROA covers it. Add a ROA for AS393294, maxLength 24. |
| ROA: none | 45.199.165.0/24 | No ROA covers it. Add a ROA for AS393294, maxLength 24. |
| ROA: none | 45.199.166.0/24 | No ROA covers it. Add a ROA for AS393294, maxLength 24. |
| ROA: none | 45.199.167.0/24 | No ROA covers it. Add a ROA for AS393294, maxLength 24. |
| ROA: none | 45.199.168.0/24 | No ROA covers it. Add a ROA for AS393294, maxLength 24. |
Route objects not announced
Route objects with origin AS393294 whose prefix no peer sees AS393294 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.199.160.0/20 | RADB | No ROA |
| 45.199.168.0/22 | RADB | No ROA |
| 45.199.170.0/24 | AFRINIC | Valid |
| 45.199.171.0/24 | AFRINIC | Valid |
| 45.199.172.0/22 | RADB | No ROA |
| 45.199.172.0/24 | AFRINIC | Valid |
| 45.199.173.0/24 | AFRINIC | Valid |
| 2602:2d8:1::/48 | RADB | 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.