Slush Technologies AS V4 Transit
VITAL-DATA-NZ
BGP inherited
Cluster stats
| Netblocks | 6 |
| All fragments | 23 blocks across 2 clusters |
| Cluster ID | 194539612 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 4 shared RIR contact/maintainer handles |
| Registry names | 1 distinct registrant name across these blocks |
| full provenance (JSON) → · how attribution works | |
Footprint over time
2 weekly snapshots · JSON
6
0 netblocks since 2026-07-05
2026-07-05
peak 6
2026-07-06
IP Ranges (6)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 103.23.16.0/24 | VITAL-DATA-NZ | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 103.23.17.0/24 | VITAL-DATA-NZ | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 103.23.18.0/24 | VITAL-DATA-NZ | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 103.23.19.0/25 | VITAL-DATA-NZ | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 103.23.19.128/25 | VITAL-DATA-NZ | APNIC | ASSIGNED NON-PORTABLE | ● high |
| 110.173.160.0/21 | VITAL-DATA-NZ | APNIC | ASSIGNED NON-PORTABLE | ● high |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(6 of 6)
Possible discrepancies (4)
These blocks are registered to VITAL-DATA-NZ 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.
| 110.173.160.0/21 /21 | authorized for AS132040 — Slush Technologies AS V4 Transit |
| 103.23.16.0/24 /24 | authorized for AS132040 — Slush Technologies AS V4 Transit |
| 103.23.17.0/24 /24 | authorized for AS132040 — Slush Technologies AS V4 Transit |
| 103.23.18.0/24 /24 | authorized for AS132040 — Slush Technologies AS V4 Transit |
NIC Handles
AN752-AP
MAINT-NZ-VITAL-DATA
VDNO1-AP
VRA1-AP