Network · data from 2026-11-12
AS7441 OMEGADC - Omega Datacenters, LLC
Registry name: OMEGADC - Omega Datacenters, LLC, US · not in PeeringDB
15IPv4 routes
100.0% RPKI valid · 6.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
14 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
4Route objects not announced
registered with origin AS7441, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS7441, 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.
| 207.189.128.0/24 | Valid | Nonecovered by 207.189.128.0/21 | 673 100% |
| 207.189.129.0/24 | Valid | Nonecovered by 207.189.128.0/21 | 673 100% |
| 207.189.130.0/24 | Valid | Nonecovered by 207.189.128.0/21 | 673 100% |
| 207.189.131.0/24 | Valid | Nonecovered by 207.189.128.0/21 | 673 100% |
| 207.189.132.0/24 | Valid | Nonecovered by 207.189.128.0/21 | 673 100% |
| 207.189.133.0/24 | Valid | Nonecovered by 207.189.128.0/21 | 673 100% |
| 207.189.134.0/24 | Valid | Nonecovered by 207.189.128.0/21 | 673 100% |
| 207.189.135.0/24 | Valid | Nonecovered by 207.189.128.0/21 | 673 100% |
| 207.189.136.0/24 | Valid | Nonecovered by 207.189.136.0/22 | 673 100% |
| 207.189.137.0/24 | Valid | Nonecovered by 207.189.136.0/22 | 673 100% |
| 207.189.138.0/24 | Valid | Nonecovered by 207.189.136.0/22 | 673 100% |
| 207.189.139.0/24 | Valid | Nonecovered by 207.189.136.0/22 | 673 100% |
| 207.189.140.0/24 | Valid | Nonecovered by 207.189.140.0/23 | 673 100% |
| 207.189.141.0/24 | Valid | Nonecovered by 207.189.140.0/23 | 673 100% |
| 50.220.20.0/24 | Valid | RIR databaseARIN | 663 99% |
AS-SET
AS7441 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 18 are in fix.csv.
- Route object: none14
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 207.189.128.0/24 | No route object for it. A route object for 207.189.128.0/21 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.129.0/24 | No route object for it. A route object for 207.189.128.0/21 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.130.0/24 | No route object for it. A route object for 207.189.128.0/21 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.131.0/24 | No route object for it. A route object for 207.189.128.0/21 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.132.0/24 | No route object for it. A route object for 207.189.128.0/21 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.133.0/24 | No route object for it. A route object for 207.189.128.0/21 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.134.0/24 | No route object for it. A route object for 207.189.128.0/21 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.135.0/24 | No route object for it. A route object for 207.189.128.0/21 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.136.0/24 | No route object for it. A route object for 207.189.136.0/22 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.137.0/24 | No route object for it. A route object for 207.189.136.0/22 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.138.0/24 | No route object for it. A route object for 207.189.136.0/22 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.139.0/24 | No route object for it. A route object for 207.189.136.0/22 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.140.0/24 | No route object for it. A route object for 207.189.140.0/23 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
| Route object: none | 207.189.141.0/24 | No route object for it. A route object for 207.189.140.0/23 with origin AS7441 covers it (filters allowing more-specifics accept it). Add a route object with origin AS7441 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS7441 whose prefix no peer sees AS7441 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 207.189.128.0/21 | ARIN | Valid |
| 207.189.136.0/22 | ARIN | Valid |
| 207.189.140.0/23 | ARIN | Valid |
| 207.189.165.0/24 | 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.