Omadata IX Route Servers

Data as of 2026-10-11
BGP inherited
This organisation
Netblocks8
IPv6 4 prefixes (largest 2403:1a00:55:659::3:1/128)
Record ID246758789
RegistryPEERINGDB
Customerssee who runs inside this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 1 shared RIR contact/maintainer handle
Registry names 1 distinct registrant name across these blocks
full provenance (JSON) → · how attribution works · report an issue

IP Ranges (8)

⬇ export CSV
CIDR Org name Registry Status Confidence
103.28.82.1/32 Omadata IX Route Servers PEERINGDB ASSIGNED ● high
103.28.83.1/32 Omadata IX Route Servers PEERINGDB ASSIGNED ● high
218.100.74.1/32 Omadata IX Route Servers PEERINGDB ASSIGNED ● high
218.100.74.200/32 Omadata IX Route Servers PEERINGDB ASSIGNED ● high
2403:1a00::1/128 Omadata IX Route Servers PEERINGDB ASSIGNED ● high
2403:1a00::99/128 Omadata IX Route Servers PEERINGDB ASSIGNED ● high
2403:1a00:55:659::3:1/128 Omadata IX Route Servers PEERINGDB ASSIGNED ● high
2403:1a00:55:659::4:1/128 Omadata IX Route Servers PEERINGDB ASSIGNED ● high

IPv6 ranges (4)

Footprint over time

3 weekly snapshots · JSON
8 0 netblocks since 2026-09-27
2026-09-27 peak 8 2026-10-11

Network trust

what's this?
RPKI hygiene: C how networks compare →
50.0% of checked blocks have valid RPKI ROA coverage (4 of 8)
No discrepancies found among checked blocks.

NIC Handles

AS55659