Network · data from 2026-11-12
AS31972 Emagine Concept
Registry name: EMGINECONCEPT-01 - Emagine Concept, Inc., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31972, 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.
| 103.196.204.0/23 | Valid | None | 673 100% |
| 103.196.206.0/23 | Valid | None | 673 100% |
| 103.207.48.0/22 | Valid | Other origin only | 673 100% |
| 103.207.50.0/23 | Valid | None | 673 100% |
| 45.115.228.0/22 | Valid | Other origin only | 671 100% |
| 45.115.230.0/23 | Valid | None | 671 100% |
| 103.56.8.0/22 | Valid | Other origin only | 671 100% |
| 103.56.10.0/23 | Valid | None | 671 100% |
| 103.207.48.0/23 | Valid | None | 671 100% |
| 103.196.204.0/22 | Valid | Other origin only | 669 99% |
| 103.207.48.0/24 | Valid | None | 72 11% |
| 103.207.49.0/24 | Valid | None | 72 11% |
| 103.196.204.0/24 | Valid | None | 47 7%low visibility |
| 103.196.205.0/24 | Valid | None | 47 7%low visibility |
| 103.196.206.0/24 | Valid | None | 47 7%low visibility |
| 103.196.207.0/24 | Valid | None | 47 7%low visibility |
| 45.115.230.0/24 | Valid | Other IRR onlyNTTCOM | 672 100% |
| 103.56.8.0/24 | Valid | Other IRR onlyNTTCOM | 668 99% |
| 103.56.9.0/24 | Valid | Other IRR onlyNTTCOM | 668 99% |
| 45.115.228.0/24 | Valid | Other IRR onlyNTTCOM | 667 99% |
| 45.115.229.0/24 | Valid | Other IRR onlyNTTCOM | 667 99% |
| 45.115.231.0/24 | Valid | Other IRR onlyNTTCOM | 147 22% |
| 103.56.10.0/24 | Valid | Other IRR onlyNTTCOM | 147 22% |
| 103.56.11.0/24 | Valid | Other IRR onlyNTTCOM | 147 22% |
| 45.121.48.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 64.78.172.0/22 | Valid | RIR databaseAPNIC | 671 100% |
| 103.61.136.0/22 | Valid | RIR databaseAPNIC, NTTCOM | 671 100% |
| 103.159.88.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 103.159.206.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 162.222.164.0/23 | Valid | RIR databaseARIN | 671 100% |
| 199.101.116.0/23 | Valid | RIR databaseARIN | 671 100% |
| 202.148.212.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 211.73.102.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 211.79.108.0/23 | Valid | RIR databaseAPNIC | 671 100% |
| 64.78.172.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 64.78.173.0/24 | Valid | RIR databaseAPNIC, NTTCOM, RADB | 668 99% |
| 103.61.136.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.61.137.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.61.138.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.61.139.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.159.206.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 103.159.207.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 211.73.102.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 211.73.103.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 211.79.108.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 211.79.109.0/24 | Valid | RIR databaseAPNIC | 668 99% |
| 45.121.48.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 45.121.49.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 45.121.50.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 45.121.51.0/24 | Valid | RIR databaseAPNIC | 667 99% |
| 64.78.174.0/24 | Valid | RIR databaseAPNIC | 147 22% |
| 64.78.175.0/24 | Valid | RIR databaseAPNIC, NTTCOM | 147 22% |
| 103.159.88.0/24 | Valid | RIR databaseAPNIC | 147 22% |
| 103.159.89.0/24 | Valid | RIR databaseAPNIC | 147 22% |
| 162.222.164.0/24 | Valid | RIR databaseARIN, NTTCOM, RADB | 147 22% |
| 199.101.116.0/24 | Valid | RIR databaseARIN, NTTCOM | 147 22% |
| 199.101.117.0/24 | Valid | RIR databaseARIN, NTTCOM | 147 22% |
| 202.148.212.0/24 | Valid | RIR databaseAPNIC | 147 22% |
| 202.148.213.0/24 | Valid | RIR databaseAPNIC | 147 22% |
AS-SET
AS31972's PeeringDB record names no 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 76 are in fix.csv.
- Route object: none16
- Route object: RIR8
- Route object: not announced52
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 103.196.204.0/23 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.196.206.0/23 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.207.48.0/22 | Route objects for it name AS132369. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.207.50.0/23 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 45.115.228.0/22 | Route objects for it name AS132369. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 45.115.230.0/23 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.56.8.0/22 | Route objects for it name AS132369. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.56.10.0/23 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.207.48.0/23 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.196.204.0/22 | Route objects for it name AS132369. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.207.48.0/24 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.207.49.0/24 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.196.204.0/24 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.196.205.0/24 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.196.206.0/24 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: none | 103.196.207.0/24 | No route object for it. Add a route object with origin AS31972 in the RIR database for the space. |
| Route object: RIR | 45.115.230.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.8.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.9.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 45.115.228.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 45.115.229.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 45.115.231.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.10.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
| Route object: RIR | 103.56.11.0/24 | Route object only in NTTCOM. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS31972 whose prefix no peer sees AS31972 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.121.48.0/23 | APNIC | Valid |
| 45.121.50.0/23 | APNIC | Valid |
| 45.127.216.0/24 | NTTCOM | Valid |
| 45.127.217.0/24 | NTTCOM | Valid |
| 64.78.160.0/20 | APNIC | Valid |
| 64.78.160.0/21 | APNIC | Valid |
| 64.78.160.0/22 | APNIC | Valid |
| 64.78.160.0/23 | APNIC | Valid |
| 64.78.160.0/24 | APNIC | Valid |
| 64.78.161.0/24 | APNIC | Valid |
| 64.78.162.0/23 | APNIC | Valid |
| 64.78.162.0/24 | APNIC | Valid |
| 64.78.163.0/24 | APNIC | Valid |
| 64.78.164.0/22 | APNIC | Valid |
| 64.78.164.0/23 | APNIC | Valid |
| 64.78.164.0/24 | APNIC | Valid |
| 64.78.165.0/24 | APNIC | Valid |
| 64.78.166.0/23 | APNIC | Valid |
| 64.78.166.0/24 | APNIC | Valid |
| 64.78.167.0/24 | APNIC | Valid |
| 64.78.168.0/21 | APNIC | Valid |
| 64.78.168.0/22 | APNIC | Valid |
| 64.78.168.0/23 | APNIC | Valid |
| 64.78.168.0/24 | APNIC | Valid |
| 64.78.169.0/24 | APNIC | Valid |
| 64.78.170.0/23 | APNIC | Valid |
| 64.78.170.0/24 | APNIC | Valid |
| 64.78.171.0/24 | APNIC | Valid |
| 64.78.172.0/23 | APNIC | Valid |
| 64.78.174.0/23 | APNIC | Valid |
| 64.214.181.0/24 | NTTCOM | No ROA |
| 101.251.111.0/24 | NTTCOM | No ROA |
| 101.251.117.0/24 | NTTCOM | No ROA |
| 103.61.136.0/23 | APNIC | Valid |
| 103.61.138.0/23 | APNIC | Valid |
| 103.148.202.0/23 | APNIC, RADB | Valid |
| 103.148.202.0/24 | APNIC | Valid |
| 103.148.203.0/24 | APNIC | Valid |
| 162.222.164.0/22 | ARIN | Valid |
| 162.222.165.0/24 | ARIN, NTTCOM, RADB | Valid |
| 162.222.166.0/23 | ARIN | Valid |
| 162.222.166.0/24 | ARIN, NTTCOM | Valid |
| 162.222.167.0/24 | ARIN | Valid |
| 199.101.116.0/22 | ARIN, NTTCOM, RADB | Valid |
| 199.101.118.0/23 | ARIN | Valid |
| 199.101.118.0/24 | ARIN, NTTCOM | Valid |
| 199.101.119.0/24 | ARIN, NTTCOM | Valid |
| 200.77.172.0/24 | RADB | No ROA |
| 2405:d6c0::/32 | APNIC | Valid |
| 2405:d6c0::/33 | APNIC | Valid |
| 2405:d6c0:8000::/33 | APNIC | Valid |
| 2607:8680::/32 | 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.