bgpreport

Network · data from 2026-11-12

AS45061 SIN - Shanghai Information Network Co.,Ltd.

Registry name: SIN - Shanghai Information Network Co.,Ltd., CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS45061, 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.
114.141.128.0/19 Valid Nonecovered by 114.141.128.0/18 672 100% 67
114.141.148.0/22 Valid Nonecovered by 114.141.128.0/18 672 100% 67
114.141.160.0/19 Valid Nonecovered by 114.141.128.0/18 672 100% 67
45.116.52.0/22 Valid Other IRR onlyRADB 672 100% 67
103.13.244.0/22 Valid Other IRR onlyRADB 672 100% 67
103.251.84.0/22 Valid Other IRR onlyRADB 672 100% 67
114.28.160.0/19 Valid Other IRR onlyRADB 672 100% 67
114.141.128.0/18 Valid Other IRR onlyRADB 672 100% 67
118.126.32.0/19 Valid Other IRR onlyRADB 672 100% 67
121.55.0.0/18 Valid Other IRR onlyRADB 672 100% 67
202.122.112.0/21 Valid Other IRR onlyRADB 672 100% 67
2400:8200::/32 Valid Other IRR onlyRADB 636 100% 68

AS-SET

AS45061 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 38 are in fix.csv.

  • Route object: none3
  • Route object: RIR9
  • Route object: not announced26
ChangePrefix or setDetailFull-table peers
Route object: none114.141.128.0/19No route object for it. A route object for 114.141.128.0/18 with origin AS45061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45061 in the RIR database for the space.672 of 673
Route object: none114.141.148.0/22No route object for it. A route object for 114.141.128.0/18 with origin AS45061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45061 in the RIR database for the space.672 of 673
Route object: none114.141.160.0/19No route object for it. A route object for 114.141.128.0/18 with origin AS45061 covers it (filters allowing more-specifics accept it). Add a route object with origin AS45061 in the RIR database for the space.672 of 673
Route object: RIR45.116.52.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.13.244.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.251.84.0/22Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR114.28.160.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR114.141.128.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR118.126.32.0/19Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR121.55.0.0/18Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR202.122.112.0/21Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR2400:8200::/32Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

45.254.184.0/21RADBNo ROA
45.254.192.0/21RADBNo ROA
45.254.196.0/22RADBNo ROA
45.255.64.0/21RADBNo ROA
45.255.80.0/20RADBNo ROA
45.255.96.0/22RADBNo ROA
45.255.100.0/22RADBNo ROA
45.255.104.0/22RADBNo ROA
45.255.108.0/22RADBNo ROA
45.255.112.0/22RADBNo ROA
45.255.116.0/22RADBNo ROA
45.255.136.0/21RADBNo ROA
45.255.144.0/21RADBNo ROA
45.255.160.0/21RADBNo ROA
45.255.176.0/21RADBNo ROA
45.255.208.0/22RADBNo ROA
45.255.216.0/21RADBNo ROA
45.255.224.0/20RADBNo ROA
45.255.240.0/21RADBNo ROA
45.255.248.0/22RADBNo ROA
123.199.144.0/20RADBNo ROA
160.202.216.0/21RADBNo ROA
192.140.128.0/21RADBNo ROA
192.140.192.0/20RADBNo ROA
203.95.112.0/20RADBNo ROA
2400:8201::/48RADBValid

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.