Skip to content
iplogs.com

AS4657 StarHub Ltd

Backbone / NSP · based in Singapore · IPLogs default verdict: Transit / backbone

Backbone / NSPlive registry data
ASN
AS4657
Name
StarHub Ltd
Category
Backbone / NSP
Country
Singapore
IPLogs verdict
Transit / backbone
Registry
APNIC
Allocated
1996-01-18
PeeringDB
Yes · 1 fac.
Proxy backbone
No

About StarHub Ltd

StarHub Ltd (AS4657) is registered with APNIC in Singapore and was allocated on 1996-01-18. Self-declared in PeeringDB as a Network Service Provider (transit / backbone). IPLogs treats PeeringDB NSPs as core infrastructure (asn_peeringdb_nsp, zero weight) rather than hosting — large carriers in this bucket also carry residential traffic, so per-IP checks decide the verdict. PeeringDB lists it in 1 facility.

How IPLogs classifies AS4657

When the detection engine sees an IP that routes through AS4657, it checks three lists: (1) the curated VPN-provider ASN list, (2) the datacenter / hosting ASN list, and (3) the trusted CDN allowlist. Matches produce one of vpn_asn, dc_ip, or no flag respectively. Keywords in the org name (e.g. "vpn", "proxy", "anonym") may also trigger vpn_org_keyword even for unknown ASNs.

Use the ASN as a shortcut when you want to block a whole hosting provider at the edge rather than maintaining a per-IP list.

Authoritative sources for AS4657

Third-party registries where you can verify the announcements, peer relationships, and WHOIS registration for this ASN.

Frequently asked questions about AS4657

+Is AS4657 (StarHub Ltd) a VPN, datacenter, or residential network?

IPLogs classifies StarHub Ltd (AS4657) as a backbone / nsp network based in Singapore. The default verdict for any IP that routes through this ASN is "Transit / backbone".

+Who operates AS4657 and where is it registered?

StarHub Ltd (AS4657) is registered with APNIC, operates in Singapore, was allocated on 1996-01-18. It is listed in PeeringDB across 1 facility.

+How do I check or block AS4657 traffic?

Send any suspect IP to the IPLogs API — POST https://iplogs.com/v1/check with body {"ip":"<ip>"} — and the response reports the originating ASN plus whether it matched the VPN, datacenter, or CDN lists. To block a whole hosting network at the edge, filter on AS4657 instead of maintaining a per-IP list. Copy-paste recipes for Cloudflare WAF, Nginx, and Stripe Radar are at /guides/block-vpn-traffic.

Related pages