TG_NETWORK
Data as of 2026-10-04
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.
This organisation
| Netblocks | 3 · 65,796 IPv4 addresses |
| Record ID | 247857350 |
| Registry | APNIC |
| Customers | see who runs inside this network → |
Evidence & provenance ?
| Attribution | BGP parent (inherited) |
| Shared handles | clustered on 9 shared RIR contact/maintainer handles |
| Registry names | 3 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 |
|---|---|---|---|---|
| 158.44.0.0/16 | TG-NETWORK | APNIC | ALLOCATED PORTABLE | ● low |
| 195.29.226.172/30 | TG_NETWORK | RIPE | ASSIGNED PA | ● low |
| 202.108.61.0/24 | TG-NETWORK-CO | APNIC | ASSIGNED NON-PORTABLE | ● low |
Network trust
what's this?
RPKI hygiene: C
how networks compare →
66.7%
of checked blocks have valid RPKI ROA coverage
(2 of 3)
Possible discrepancies (1)
These blocks are registered to TG_NETWORK 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.
| 202.108.61.0/24 /24 | authorized for AS4808 — China Unicom |
NIC Handles
CH455-AP
DUMY-RIPE
DUMY-RIPE
HPT-MNT
IM766-AP
IM766-AP
MAINT-CNCGROUP-BJ
MNT-KRNIC-AP
SY21-AP