bgpreport

Network · data from 2026-11-12

AS31972 Emagine Concept

Registry name: EMGINECONCEPT-01 - Emagine Concept, Inc., US · PeeringDB

59IPv4 routes 100.0% RPKI valid · 72.9% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 16 with no route object for this origin
4Low visibility seen by under 10% of full-table peers
52Route objects not announced registered with origin AS31972, seen from no peer

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% 70
103.196.206.0/23 Valid None 673 100% 70
103.207.48.0/22 Valid Other origin only 673 100% 67
103.207.50.0/23 Valid None 673 100% 67
45.115.228.0/22 Valid Other origin only 671 100% 67
45.115.230.0/23 Valid None 671 100% 67
103.56.8.0/22 Valid Other origin only 671 100% 67
103.56.10.0/23 Valid None 671 100% 67
103.207.48.0/23 Valid None 671 100% 67
103.196.204.0/22 Valid Other origin only 669 99% 67
103.207.48.0/24 Valid None 72 11% 39
103.207.49.0/24 Valid None 72 11% 39
103.196.204.0/24 Valid None 47 7%low visibility 29
103.196.205.0/24 Valid None 47 7%low visibility 29
103.196.206.0/24 Valid None 47 7%low visibility 29
103.196.207.0/24 Valid None 47 7%low visibility 29
45.115.230.0/24 Valid Other IRR onlyNTTCOM 672 100% 70
103.56.8.0/24 Valid Other IRR onlyNTTCOM 668 99% 67
103.56.9.0/24 Valid Other IRR onlyNTTCOM 668 99% 67
45.115.228.0/24 Valid Other IRR onlyNTTCOM 667 99% 67
45.115.229.0/24 Valid Other IRR onlyNTTCOM 667 99% 67
45.115.231.0/24 Valid Other IRR onlyNTTCOM 147 22% 52
103.56.10.0/24 Valid Other IRR onlyNTTCOM 147 22% 52
103.56.11.0/24 Valid Other IRR onlyNTTCOM 147 22% 52
45.121.48.0/22 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
64.78.172.0/22 Valid RIR databaseAPNIC 671 100% 67
103.61.136.0/22 Valid RIR databaseAPNIC, NTTCOM 671 100% 67
103.159.88.0/23 Valid RIR databaseAPNIC 671 100% 67
103.159.206.0/23 Valid RIR databaseAPNIC 671 100% 67
162.222.164.0/23 Valid RIR databaseARIN 671 100% 67
199.101.116.0/23 Valid RIR databaseARIN 671 100% 67
202.148.212.0/23 Valid RIR databaseAPNIC 671 100% 67
211.73.102.0/23 Valid RIR databaseAPNIC 671 100% 67
211.79.108.0/23 Valid RIR databaseAPNIC 671 100% 67
64.78.172.0/24 Valid RIR databaseAPNIC 668 99% 67
64.78.173.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
103.61.136.0/24 Valid RIR databaseAPNIC 668 99% 67
103.61.137.0/24 Valid RIR databaseAPNIC 668 99% 67
103.61.138.0/24 Valid RIR databaseAPNIC 668 99% 67
103.61.139.0/24 Valid RIR databaseAPNIC 668 99% 67
103.159.206.0/24 Valid RIR databaseAPNIC 668 99% 67
103.159.207.0/24 Valid RIR databaseAPNIC 668 99% 67
211.73.102.0/24 Valid RIR databaseAPNIC 668 99% 67
211.73.103.0/24 Valid RIR databaseAPNIC 668 99% 67
211.79.108.0/24 Valid RIR databaseAPNIC 668 99% 67
211.79.109.0/24 Valid RIR databaseAPNIC 668 99% 67
45.121.48.0/24 Valid RIR databaseAPNIC 667 99% 67
45.121.49.0/24 Valid RIR databaseAPNIC 667 99% 67
45.121.50.0/24 Valid RIR databaseAPNIC 667 99% 67
45.121.51.0/24 Valid RIR databaseAPNIC 667 99% 67
64.78.174.0/24 Valid RIR databaseAPNIC 147 22% 52
64.78.175.0/24 Valid RIR databaseAPNIC, NTTCOM 147 22% 52
103.159.88.0/24 Valid RIR databaseAPNIC 147 22% 52
103.159.89.0/24 Valid RIR databaseAPNIC 147 22% 52
162.222.164.0/24 Valid RIR databaseARIN, NTTCOM, RADB 147 22% 52
199.101.116.0/24 Valid RIR databaseARIN, NTTCOM 147 22% 52
199.101.117.0/24 Valid RIR databaseARIN, NTTCOM 147 22% 52
202.148.212.0/24 Valid RIR databaseAPNIC 147 22% 52
202.148.213.0/24 Valid RIR databaseAPNIC 147 22% 52

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
ChangePrefix or setDetailFull-table peers
Route object: none103.196.204.0/23No route object for it. Add a route object with origin AS31972 in the RIR database for the space.673 of 673
Route object: none103.196.206.0/23No route object for it. Add a route object with origin AS31972 in the RIR database for the space.673 of 673
Route object: none103.207.48.0/22Route objects for it name AS132369. Add a route object with origin AS31972 in the RIR database for the space.673 of 673
Route object: none103.207.50.0/23No route object for it. Add a route object with origin AS31972 in the RIR database for the space.673 of 673
Route object: none45.115.228.0/22Route objects for it name AS132369. Add a route object with origin AS31972 in the RIR database for the space.671 of 673
Route object: none45.115.230.0/23No route object for it. Add a route object with origin AS31972 in the RIR database for the space.671 of 673
Route object: none103.56.8.0/22Route objects for it name AS132369. Add a route object with origin AS31972 in the RIR database for the space.671 of 673
Route object: none103.56.10.0/23No route object for it. Add a route object with origin AS31972 in the RIR database for the space.671 of 673
Route object: none103.207.48.0/23No route object for it. Add a route object with origin AS31972 in the RIR database for the space.671 of 673
Route object: none103.196.204.0/22Route objects for it name AS132369. Add a route object with origin AS31972 in the RIR database for the space.669 of 673
Route object: none103.207.48.0/24No route object for it. Add a route object with origin AS31972 in the RIR database for the space.72 of 673
Route object: none103.207.49.0/24No route object for it. Add a route object with origin AS31972 in the RIR database for the space.72 of 673
Route object: none103.196.204.0/24No route object for it. Add a route object with origin AS31972 in the RIR database for the space.47 of 673
Route object: none103.196.205.0/24No route object for it. Add a route object with origin AS31972 in the RIR database for the space.47 of 673
Route object: none103.196.206.0/24No route object for it. Add a route object with origin AS31972 in the RIR database for the space.47 of 673
Route object: none103.196.207.0/24No route object for it. Add a route object with origin AS31972 in the RIR database for the space.47 of 673
Route object: RIR45.115.230.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
Route object: RIR103.56.8.0/24Route object only in NTTCOM. Add it in the RIR database for the space.668 of 673
Route object: RIR103.56.9.0/24Route object only in NTTCOM. Add it in the RIR database for the space.668 of 673
Route object: RIR45.115.228.0/24Route object only in NTTCOM. Add it in the RIR database for the space.667 of 673
Route object: RIR45.115.229.0/24Route object only in NTTCOM. Add it in the RIR database for the space.667 of 673
Route object: RIR45.115.231.0/24Route object only in NTTCOM. Add it in the RIR database for the space.147 of 673
Route object: RIR103.56.10.0/24Route object only in NTTCOM. Add it in the RIR database for the space.147 of 673
Route object: RIR103.56.11.0/24Route object only in NTTCOM. Add it in the RIR database for the space.147 of 673

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/23APNICValid
45.121.50.0/23APNICValid
45.127.216.0/24NTTCOMValid
45.127.217.0/24NTTCOMValid
64.78.160.0/20APNICValid
64.78.160.0/21APNICValid
64.78.160.0/22APNICValid
64.78.160.0/23APNICValid
64.78.160.0/24APNICValid
64.78.161.0/24APNICValid
64.78.162.0/23APNICValid
64.78.162.0/24APNICValid
64.78.163.0/24APNICValid
64.78.164.0/22APNICValid
64.78.164.0/23APNICValid
64.78.164.0/24APNICValid
64.78.165.0/24APNICValid
64.78.166.0/23APNICValid
64.78.166.0/24APNICValid
64.78.167.0/24APNICValid
64.78.168.0/21APNICValid
64.78.168.0/22APNICValid
64.78.168.0/23APNICValid
64.78.168.0/24APNICValid
64.78.169.0/24APNICValid
64.78.170.0/23APNICValid
64.78.170.0/24APNICValid
64.78.171.0/24APNICValid
64.78.172.0/23APNICValid
64.78.174.0/23APNICValid
64.214.181.0/24NTTCOMNo ROA
101.251.111.0/24NTTCOMNo ROA
101.251.117.0/24NTTCOMNo ROA
103.61.136.0/23APNICValid
103.61.138.0/23APNICValid
103.148.202.0/23APNIC, RADBValid
103.148.202.0/24APNICValid
103.148.203.0/24APNICValid
162.222.164.0/22ARINValid
162.222.165.0/24ARIN, NTTCOM, RADBValid
162.222.166.0/23ARINValid
162.222.166.0/24ARIN, NTTCOMValid
162.222.167.0/24ARINValid
199.101.116.0/22ARIN, NTTCOM, RADBValid
199.101.118.0/23ARINValid
199.101.118.0/24ARIN, NTTCOMValid
199.101.119.0/24ARIN, NTTCOMValid
200.77.172.0/24RADBNo ROA
2405:d6c0::/32APNICValid
2405:d6c0::/33APNICValid
2405:d6c0:8000::/33APNICValid
2607:8680::/32ARINValid

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.