Ortel Communications
BGP inherited
Cluster stats
Netblocks9
All fragments 10 blocks across 2 clusters
Cluster ID193386911
RegistryAPNIC
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 8 shared RIR contact/maintainer handles
Registry names 3 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works

Footprint over time

2 weekly snapshots · JSON
9 0 netblocks since 2026-07-05
2026-07-05 peak 9 2026-07-06

IP Ranges (9)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.27.170.131/32 Ortel Communications PEERINGDB ASSIGNED ● high
2401:7500:fff6::131/128 Ortel Communications PEERINGDB ASSIGNED ● high
2a02:f561::/48 ORTEL-NET RIPE ASSIGNED ● high
46.254.240.0 – 46.254.245.255 ORTEL-NET RIPE ASSIGNED PA ● low
77.243.124.0/23 ORTEL-NET RIPE ASSIGNED PA ● low
77.243.127.0/24 ORTEL-NET RIPE ASSIGNED PA ● low
157.15.92.0/23 ORTEL APNIC ALLOCATED PORTABLE ● low
185.14.71.0/24 ORTEL-NET RIPE ASSIGNED PA ● low
2001:df4:5c40::/48 ORTEL APNIC ASSIGNED PORTABLE ● low

Network trust

what's this?
RPKI hygiene: C how networks compare →
55.6% of checked blocks have valid RPKI ROA coverage (5 of 9)
Possible discrepancies (5)

These blocks are registered to Ortel Communications but cryptographically authorized for a different, unrelated network (2 distinct holders) — often M&A history, multi-homing, or outsourced/managed hosting, occasionally worth a closer look.

2001:df4:5c40::/48 /48 authorized for AS151732 — ONREMOTE TELECOM PRIVATE LIMITED
77.243.124.0/23 /23 authorized for AS5547 — JSC Orient-Telecom
157.15.92.0/23 /23 authorized for AS151732 — ONREMOTE TELECOM PRIVATE LIMITED
77.243.127.0/24 /24 authorized for AS5547 — JSC Orient-Telecom
185.14.71.0/24 /24 authorized for AS5547 — JSC Orient-Telecom

NIC Handles

AS23772 AS5547-MNT DK1032-AP DO218-AP DUMY-RIPE DUMY-RIPE MAINT-IN-IRINN ORTEL-MNT