MANGO NETWORK, C. A. MANGONET, C. A,

Data as of 2026-08-16
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.
Cluster stats
Netblocks3 · 1,025 IPv4 addresses
IPv6 1 prefix (largest 2801:18d:0:2000::17/128)
Cluster ID222470801
RegistryPEERINGDB
Customersfind customers using this network →
Evidence & provenance ?
Attribution BGP parent (inherited)
Shared handles clustered on 5 shared RIR contact/maintainer handles
Registry names 2 distinct registrant names across these blocks
full provenance (JSON) → · how attribution works · report an issue

Footprint over time

5 weekly snapshots · JSON
30 -1 netblocks since 2026-07-05
2026-07-05 peak 31 2026-07-19

IP Ranges (3)

⬇ export CSV
CIDR Org name Registry Status Confidence
45.68.89.17/32 MANGO NETWORK, C. A. MANGONET, C. A, PEERINGDB ASSIGNED ● high
2801:18d:0:2000::17/128 MANGO NETWORK, C. A. MANGONET, C. A, PEERINGDB ASSIGNED ● high
181.191.224.0/22 MANGO NETWORK, C. A. MANGONET, C. A, LACNIC ALLOCATED ● low

IPv6 ranges (1)

Network trust

what's this?
RPKI hygiene: A how networks compare →
100.0% of checked blocks have valid RPKI ROA coverage (3 of 3)
Possible discrepancies (1)

These blocks are registered to MANGO NETWORK, C. A. MANGONET, C. A, 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.

181.191.224.0/22 /22 authorized for AS271855 — AS271855

NIC Handles

AS271855 MNC13 MNC13 OSS57 VE-MACA9-LACNIC