bgpreport

Network · data from 2026-11-12

AS18244 STIDC - Stateline Internet Data Center Co., Ltd. Shanghai

Registry name: STIDC - Stateline Internet Data Center Co., Ltd. Shanghai, CN · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS18244, 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.253.204.0/22 Invalid: origin Other origin only 2 0%low visibility 2
2403:a200:a100::/48 Invalid: origin None 2 0%low visibility 2
120.132.224.0/24 Valid Other origin only 3 0%low visibility 4
120.132.231.0/24 Valid Other origin only 3 0%low visibility 4
120.133.240.0/22 Valid Other origin only 3 0%low visibility 4
120.133.252.0/22 Valid Other origin only 3 0%low visibility 4
211.148.17.0/24 Valid Other origin only 3 0%low visibility 4
211.148.18.0/23 Valid Other origin only 3 0%low visibility 4
211.148.20.0/23 Valid None 3 0%low visibility 4
211.148.22.0/24 Valid None 3 0%low visibility 4
211.148.24.0/23 Valid Other origin only 3 0%low visibility 4
211.148.30.0/23 Valid Nonecovered by 211.148.28.0/22 3 0%low visibility 4

AS-SET

AS18244 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 16 are in fix.csv.

  • ROA: origin2
  • Route object: none12
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin103.253.204.0/22ROAs covering it name AS4811, AS17428, AS17621, AS24400, not AS18244. If AS18244 should announce it, add a ROA for AS18244.2 of 673
Route object: none103.253.204.0/22Route objects for it name AS17428. Add a route object with origin AS18244 in the RIR database for the space.2 of 673
ROA: origin2403:a200:a100::/48ROAs covering it name AS4808, AS4847, AS9308, AS9802, AS17428, AS23724, AS56048, AS59020, AS133111, AS133119, not AS18244. If AS18244 should announce it, add a ROA for AS18244.2 of 636
Route object: none2403:a200:a100::/48No route object for it. Add a route object with origin AS18244 in the RIR database for the space.2 of 636
Route object: none120.132.224.0/24Route objects for it name AS17428. Add a route object with origin AS18244 in the RIR database for the space.3 of 673
Route object: none120.132.231.0/24Route objects for it name AS17428. Add a route object with origin AS18244 in the RIR database for the space.3 of 673
Route object: none120.133.240.0/22Route objects for it name AS17428. Add a route object with origin AS18244 in the RIR database for the space.3 of 673
Route object: none120.133.252.0/22Route objects for it name AS17428. Add a route object with origin AS18244 in the RIR database for the space.3 of 673
Route object: none211.148.17.0/24Route objects for it name AS17428. Add a route object with origin AS18244 in the RIR database for the space.3 of 673
Route object: none211.148.18.0/23Route objects for it name AS17428. Add a route object with origin AS18244 in the RIR database for the space.3 of 673
Route object: none211.148.20.0/23No route object for it. Add a route object with origin AS18244 in the RIR database for the space.3 of 673
Route object: none211.148.22.0/24No route object for it. Add a route object with origin AS18244 in the RIR database for the space.3 of 673
Route object: none211.148.24.0/23Route objects for it name AS17428. Add a route object with origin AS18244 in the RIR database for the space.3 of 673
Route object: none211.148.30.0/23No route object for it. A route object for 211.148.28.0/22 with origin AS18244 covers it (filters allowing more-specifics accept it). Add a route object with origin AS18244 in the RIR database for the space.3 of 673

Route objects not announced

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

211.148.12.0/24APNICNo ROA
211.148.28.0/22RADBValid

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.