Baycity Communications
Data as of 2026-08-16
BGP inherited
Limited data: only 3 ranges found registered
under this exact name. This may not reflect the organisation's full internet footprint — many companies'
web and cloud infrastructure is hosted under a third-party provider's own registration rather than their own.
Cluster stats
| Netblocks | 3 · 4,098 IPv4 addresses |
| Cluster ID | 222461547 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 5 shared RIR contact/maintainer handles |
| Registry names | 2 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works · report an issue | |
IP Ranges (3)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 118.82.144.0/20 | BAYCITY | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 192.203.154.167/32 | Baycity Communications | PEERINGDB | ASSIGNED | ● high |
| 192.203.154.168/32 | Baycity Communications | PEERINGDB | ASSIGNED | ● high |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
33.3%
of checked blocks have valid RPKI ROA coverage
(1 of 3)
Possible discrepancies (1)
These blocks are registered to Baycity Communications but cryptographically authorized for a different, unrelated network (1 distinct holder) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.
| 118.82.144.0/20 /20 | authorized for AS55872 — One New Zealand Group Limited |
NIC Handles
AO464-AP
AS55872
MAINT-NZ-BAYCITY
RB259-AP
RB259-AP