Data as of Nov 16, 2026

183.60.128.0/20

No anonymizer space · no proxy exits in 30 days

CHINANET Guangdong province network

Announcement
this exact prefix
RPKI valid
Announced by
Type
Hosting
Risk
50 / 100 · Medium

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
183.0.0.0/10
since Nov 2009
AS4134Residential39,645
222 always on
CHINANET Guangdong province network

Registrations in this block

The registry's network records over the announcement: those covering it, widest first, then every record inside it, under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
183.0.0.0/104,194,304CHINANET-GDCHINANET Guangdong province networkALLOCATED PORTABLE—anti-spam@chinatelecom.cn
└ 183.60.130.0/25128shenzhenshixinruanxinxiyouxiangunknownALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-GD
└ 183.60.130.128/2664shenzhenshiyixinkejiyouxiangongunknownALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-GD
└ 183.60.130.192/2732shenzhenshixinruanxinxiyouxiangunknownALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-GD
└ 183.60.131.0/24256baidugongsiunknownALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-GD
└ 183.60.132.0/24256dongguanshijuxunwangluojishuyouguangdongshengdongguanshiqifenglu??haoguotaidasha??306ALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-GD
└ 183.60.133.0/24256guangzhoutengmawangluojishuyouxunknownALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-GD
└ 183.60.139.0/24256guangdongyulinmufengkejiyouxianunknownALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-GD
└ 183.60.141.0/24256dongguanshiweiyiwangluokejiyouxunknownALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-GD
└ 183.60.143.0/24256dongguanshiweiyiwangluokejiyouxunknownALLOCATED NON-PORTABLE—anti-spam@chinatelecom.cn
via CHINANET-GD

A contact marked “via” is the registry's: the record names none of its own, so the registry hands down its parent's.

Network & registry

Routing timeline

Covering aggregate above, the prefix's own history below

Summary

Routing history

Pattern
Stable
First seen
Jan 2015
Current origin since
Nov 2025 · 12 mo
Origin networks
2
Last change of origin
Aug 2016
Recorded history

History

Handoffs
1