bgpreport

Network · data from 2026-11-12

AS45057 CTTSH - CHINA TIETONG SHANGHAI

Registry name: CTTSH - CHINA TIETONG SHANGHAI, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45057, 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.
222.44.35.0/24 Valid None 44 7%low visibility 30
222.44.91.0/24 Valid None 44 7%low visibility 30
222.44.111.0/24 Valid None 44 7%low visibility 30

AS-SET

AS45057 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 22 are in fix.csv.

  • Route object: none3
  • Route object: not announced19
ChangePrefix or setDetailFull-table peers
Route object: none222.44.35.0/24No route object for it. Add a route object with origin AS45057 in the RIR database for the space.44 of 673
Route object: none222.44.91.0/24No route object for it. Add a route object with origin AS45057 in the RIR database for the space.44 of 673
Route object: none222.44.111.0/24No route object for it. Add a route object with origin AS45057 in the RIR database for the space.44 of 673

Route objects not announced

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

120.90.0.0/19NTTCOM, RADBNo ROA
120.90.32.0/19NTTCOM, RADBNo ROA
120.90.64.0/19NTTCOM, RADBNo ROA
120.90.96.0/19NTTCOM, RADBNo ROA
120.90.128.0/19NTTCOM, RADBNo ROA
120.90.160.0/19NTTCOM, RADBNo ROA
120.90.192.0/19NTTCOM, RADBNo ROA
120.90.224.0/19NTTCOM, RADBNo ROA
120.90.240.0/20NTTCOM, RADBNo ROA
120.91.0.0/19NTTCOM, RADBNo ROA
120.91.32.0/19NTTCOM, RADBNo ROA
120.91.64.0/19NTTCOM, RADBNo ROA
120.91.96.0/19NTTCOM, RADBNo ROA
120.91.128.0/19NTTCOM, RADBNo ROA
120.91.160.0/19NTTCOM, RADBNo ROA
120.91.192.0/19NTTCOM, RADBNo ROA
120.91.224.0/19NTTCOM, RADBNo ROA
122.72.60.0/24NTTCOM, RADBNo ROA
122.72.61.0/24NTTCOM, RADBNo 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.