Data as of Nov 11, 2026

202.78.112.0/20

1 residential-proxy exit · 30 days

Bayan Telecommunications, Inc. · space held by Sky Internet

Announcement
this exact prefix
RPKI valid
Announced by
Type
Residential

Residential-proxy exits

Proxy exits
1
0.02% of its addresses · 30 days
Spread
1 of 16
/24s with at least one exit
Providers
1
selling exits here
Oct 12, 2026 – Nov 10, 2026

Exits seen per day

2 observations

Proxy providers listing exits

  • FastProxy

Announcements

Less specific

Covering announcements

PrefixOriginTypeProxy exitsHolderRPKI
202.78.96.0/19
since Feb 2007
AS6648Residential1Sky Internet
202.78.64.0/18
since May 2005
AS6648Residential3Sky Internet
More specific

Announcements inside

PrefixOriginTypeProxy exitsHolderRPKI
202.78.113.0/24
since Nov 2005
AS6648ResidentialSky Internet
202.78.122.0/24
since Jan 2009
AS6648Residential1Sky Internet
202.78.123.0/24
since Jun 2011
AS6648ResidentialSky Internet
202.78.127.0/24
since Jun 2014
AS6648ResidentialSky Internet

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
202.78.64.0/1816,384BAYAN-PH-APSky Internet (ORG-SI1-AP) · PHALLOCATED PORTABLE—cybersecurity_abuse@globe.com.ph
└ 202.78.114.0/24256DATELCOM-APDATELCOMASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 202.78.115.0/24256DATELCOM-APDATELCOMASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 202.78.121.0/24256NIGX-PH-APBayanTel Peering ExchangeASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 202.78.124.0/24256GLOBALINK-APGlobalink Internet Inc.ASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 202.78.125.0/24256IAS-APBorder IAS ClientsASSIGNED NON-PORTABLE—cybersecurity_abuse@globe.com.ph
via BAYAN-PH-AP
└ 202.78.127.0/24256IAS-APBorder IAS ClientsASSIGNED 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

Covering aggregate above, the prefix's own history below

Summary

Routing history

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