bgpreport

Network · data from 2026-11-12

AS22071 TRADINGSCREEN-INC - TS Imagine INC

Registry name: TRADINGSCREEN-INC - TS Imagine INC, US · not in PeeringDB

11IPv4 routes 0.0% RPKI valid · 90.9% with a route object
0IPv6 routes
1RPKI invalid 1 origin · 0 maxLength
10No ROA 1 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
15Route objects not announced registered with origin AS22071, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS22071, 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.
183.177.32.180/30 Invalid: origin None 1 0%low visibility 1
103.253.80.0/22 No ROA Other IRR onlyNTTCOM, RADB 672 100% 67
199.27.83.0/24 No ROA RIR databaseARIN 673 100% 66
199.27.84.0/24 No ROA RIR databaseARIN, NTTCOM, RADB 673 100% 67
199.27.86.0/24 No ROA RIR databaseARIN 673 100% 67
162.246.72.0/22 No ROA RIR databaseARIN, NTTCOM, RADB 672 100% 66
185.43.156.0/22 No ROA RIR databaseNTTCOM, RADB, RIPE 672 100% 66
199.27.80.0/21 No ROA RIR databaseARIN, NTTCOM, RADB 672 100% 67
199.27.85.0/24 No ROA RIR databaseARIN, RADB 672 100% 67
162.246.72.0/24 No ROA RIR databaseARIN 670 100% 67
199.27.81.0/24 No ROA RIR databaseARIN 670 100% 67

AS-SET

AS22071 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 28 are in fix.csv.

  • ROA: origin1
  • ROA: none10
  • Route object: none1
  • Route object: RIR1
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: origin183.177.32.180/30ROAs covering it name AS15830, not AS22071. If AS22071 should announce it, add a ROA for AS22071.1 of 673
Route object: none183.177.32.180/30No route object for it. Add a route object with origin AS22071 in the RIR database for the space.1 of 673
ROA: none103.253.80.0/22No ROA covers it. Add a ROA for AS22071, maxLength 22.672 of 673
Route object: RIR103.253.80.0/22Route object only in NTTCOM, RADB. Add it in the RIR database for the space.672 of 673
ROA: none199.27.83.0/24No ROA covers it. Add a ROA for AS22071, maxLength 24.673 of 673
ROA: none199.27.84.0/24No ROA covers it. Add a ROA for AS22071, maxLength 24.673 of 673
ROA: none199.27.86.0/24No ROA covers it. Add a ROA for AS22071, maxLength 24.673 of 673
ROA: none162.246.72.0/22No ROA covers it. Add a ROA for AS22071, maxLength 22.672 of 673
ROA: none185.43.156.0/22No ROA covers it. Add a ROA for AS22071, maxLength 22.672 of 673
ROA: none199.27.80.0/21No ROA covers it. Add a ROA for AS22071, maxLength 21.672 of 673
ROA: none199.27.85.0/24No ROA covers it. Add a ROA for AS22071, maxLength 24.672 of 673
ROA: none162.246.72.0/24No ROA covers it. Add a ROA for AS22071, maxLength 24.670 of 673
ROA: none199.27.81.0/24No ROA covers it. Add a ROA for AS22071, maxLength 24.670 of 673

Route objects not announced

Route objects with origin AS22071 whose prefix no peer sees AS22071 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.253.80.0/24NTTCOMNo ROA
103.253.81.0/24NTTCOMNo ROA
103.253.82.0/24NTTCOMNo ROA
103.253.83.0/24NTTCOMNo ROA
162.246.73.0/24ARINNo ROA
162.246.74.0/24ARINNo ROA
162.246.75.0/24ARINNo ROA
185.43.156.0/24RIPENo ROA
185.43.157.0/24RIPENo ROA
185.43.158.0/24RIPENo ROA
185.43.159.0/24RIPENo ROA
199.27.80.0/24ARINNo ROA
199.27.82.0/24ARINNo ROA
199.27.87.0/24ARINNo ROA
2620:108:3000::/44ARINNo 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.