IFIBER TELECOM
Cluster stats
| Netblocks | 23 |
| Cluster ID | 191601525 |
| Registry | APNIC |
| Customers | find customers using this network → |
Evidence & provenance ?
| Attribution | unresolved |
| Shared handles | clustered on 15 shared RIR contact/maintainer handles |
| Registry names | 5 distinct registrant names across these blocks |
| full provenance (JSON) → · how attribution works | |
IP Ranges (23)
⬇ export CSV| CIDR | Org name | Registry | Status | Confidence |
|---|---|---|---|---|
| 45.71.164.0/22 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 45.71.164.0/23 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 45.71.166.0/23 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 45.184.146.56/32 | IFIBER TELECOM | PEERINGDB | ASSIGNED | ● high |
| 103.100.46.0/23 | IFIBER SDN. BHD. | APNIC | ASSIGNED PORTABLE | ● high |
| 186.250.80.0/23 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 186.250.80.0/21 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 186.250.80.0/22 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 186.250.82.0/23 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 186.250.84.0/23 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 186.250.84.0/22 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 186.250.86.0/23 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 187.16.201.86/32 | IFIBER TELECOM | PEERINGDB | ASSIGNED | ● high |
| 187.16.211.221/32 | IFIBER TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:df3:2b00::/48 | IFIBER SDN. BHD. | APNIC | ASSIGNED PORTABLE | ● high |
| 2001:12f8::211:221/128 | IFIBER TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:4::56/128 | IFIBER TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2001:12f8:0:24::86/128 | IFIBER TELECOM | PEERINGDB | ASSIGNED | ● high |
| 2804:4444::/33 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 2804:4444::/32 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 2804:4444:8000::/33 | IFIBER TELECOM | BGP | ANNOUNCED | ● high |
| 103.209.154.0/23 | IFIBER | APNIC | ALLOCATED PORTABLE | ● low |
| 2a0a:4840::/29 | iFiber A/S | RIPE | ALLOCATED-BY-RIR | ● low |
Network trust
what's this?
RPKI hygiene: D
how networks compare →
43.5%
of checked blocks have valid RPKI ROA coverage
(10 of 23)
Possible discrepancies (1)
These blocks are registered to IFIBER TELECOM 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.
| 103.209.154.0/23 /23 | authorized for AS136302 — Airtech Internet Solutions Pvt. Ltd. |
NIC Handles
AI905-AP
APNIC-HM
AS267621
AS267621
DUMY-RIPE
DUMY-RIPE
JP1552-AP
JP1552-AP
MAINT-IN-IRINN
ORG-CASB1-AP
ORG-IA2148-RIPE
RIPE-NCC-HM-MNT
+3 more