UNIFIBIZ-CENTRAL-BRF
BGP inherited
Cluster stats
| Netblocks | 16 · 4,080 IPv4 addresses |
| All fragments | 32 blocks across 4 clusters |
| Cluster ID | 208802646 |
| 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
5 weekly snapshots · JSON
16
0 netblocks since 2026-07-05
2026-07-05
peak 16
2026-07-19
IP Ranges (16)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 175.136.192.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.193.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.194.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.195.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.196.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.197.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.202.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.203.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.208.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.209.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.210.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.211.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.212.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.213.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.214.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
| 175.136.215.0/24 | UNIFIBIZ-CENTRAL-BRF | APNIC | ASSIGNED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: A
how networks compare →
100.0%
of checked blocks have valid RPKI ROA coverage
(16 of 16)
RPKI-inferred operator
TM TECHNOLOGY SERVICES SDN BHD
Nearly all of this network's RPKI-covered space is cryptographically authorized for this
single operator — the registered netname is likely one of its internal infrastructure labels.
No discrepancies found among checked blocks.
NIC Handles
AM2355-AP
EAK2-AP
EAK2-AP
MAINT-MY-WEBE