Data as of Nov 11, 2026

210.4.32.0/19

1 residential-proxy exit · 30 days

Bayan Telecommunications, Inc. · space held by Sky Internet

Announcement
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1
0.01% of its addresses · 30 days
Always-on exits
1
100% of its exits
Spread
1 of 32
/24s with at least one exit
Providers
20
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

318 observations

Proxy providers listing exits

  • 711Proxy
  • AnyIP
  • BirdProxies
  • BottingTools
  • Bright Data
  • ByteProxies
  • Byteful
  • Decodo
  • FloppyData
  • Geonode
  • GonzoProxy
  • Infatica
  • LemonBright
  • Oxylabs
  • Proxy-Seller
  • ProxyEmpire
  • ProxyRack
  • ProxyWing
  • Proxyma
  • Thordata

Announcements

More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
210.4.44.0/23
since Feb 2007
AS6648ResidentialSky Internet
210.4.50.0/24
since Jan 2025
AS6648ResidentialSky Internet
210.4.54.0/24
since Mar 2015
AS6648ResidentialSky Internet
210.4.58.0/24
since Mar 2007
AS6648ResidentialSky Internet
210.4.59.0/24
since Jan 2014
AS6648ResidentialSky Internet
210.4.60.0/23
since Aug 2013
AS6648Residential1
1 always on
Sky Internet
210.4.62.0/24
since Sep 2005
AS6648ResidentialSky Internet

Registrations in this block

The registry's network records over this block, widest first, each under its parent.

RangeAddressesNetnameHolderTypeCreatedAbuse contact
210.4.0.0/1816,384BAYAN-PH-APSky Internet (ORG-SI1-AP) · PHALLOCATED PORTABLE—cybersecurity_abuse@globe.com.ph
└ 210.4.3.0 - 210.4.39.2559,472BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.32.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYANTELDSL-AP
└ 210.4.33.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYANTELDSL-AP
└ 210.4.34.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYANTELDSL-AP
└ 210.4.35.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYANTELDSL-AP
└ 210.4.36.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYANTELDSL-AP
└ 210.4.37.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYANTELDSL-AP
└ 210.4.38.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYANTELDSL-AP
└ 210.4.40.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.41.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.42.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.43.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.44.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.45.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.46.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.47.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.48.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.49.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.50.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.51.0/24256BAYANTEL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.52.0/24256BAYANTEL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.53.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.54.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.55.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.56.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.57.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.59.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.60.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.61.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.62.0/24256PARASAT-APCable21 (Parasat) - ISPASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 210.4.63.0/24256BAYANTELDSL-APBayantel DSL InfrastructureASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP

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

Who has announced 210.4.0.0/18

210.4.0.0/18

Routing history

Pattern
Stable
First seen
May 2005
Current origin since
May 2005 · 22 yr
Origin networks
1