bgpreport

Network · data from 2026-11-12

AS13535 NING - Ning Interactive, Inc.

Registry name: NING - Ning Interactive, Inc., US · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13535, 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.
2605:f480:997::/64 No ROA None 2 0%low visibility 2
8.6.19.0/24 No ROA Other IRR onlyRADB 670 100% 67
208.82.16.0/22 No ROA Other IRR onlyRADB 670 100% 67
208.82.16.0/24 No ROA Other IRR onlyRADB 670 100% 67
208.82.17.0/24 No ROA Other IRR onlyRADB 670 100% 67
208.82.18.0/24 No ROA Other IRR onlyRADB 670 100% 67
208.82.19.0/24 No ROA Other IRR onlyRADB 670 100% 67
2620:46:2000::/48 No ROA Other IRR onlyRADB 636 100% 67

AS-SET

AS13535 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 17 are in fix.csv.

  • ROA: none8
  • Route object: none1
  • Route object: RIR7
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2605:f480:997::/64No ROA covers it. Add a ROA for AS13535, maxLength 64.2 of 636
Route object: none2605:f480:997::/64No route object for it. Add a route object with origin AS13535 in the RIR database for the space.2 of 636
ROA: none8.6.19.0/24No ROA covers it. Add a ROA for AS13535, maxLength 24.670 of 673
Route object: RIR8.6.19.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none208.82.16.0/22No ROA covers it. Add a ROA for AS13535, maxLength 22.670 of 673
Route object: RIR208.82.16.0/22Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none208.82.16.0/24No ROA covers it. Add a ROA for AS13535, maxLength 24.670 of 673
Route object: RIR208.82.16.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none208.82.17.0/24No ROA covers it. Add a ROA for AS13535, maxLength 24.670 of 673
Route object: RIR208.82.17.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none208.82.18.0/24No ROA covers it. Add a ROA for AS13535, maxLength 24.670 of 673
Route object: RIR208.82.18.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none208.82.19.0/24No ROA covers it. Add a ROA for AS13535, maxLength 24.670 of 673
Route object: RIR208.82.19.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none2620:46:2000::/48No ROA covers it. Add a ROA for AS13535, maxLength 48.636 of 636
Route object: RIR2620:46:2000::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

205.245.53.0/24ALTDBNo 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.