ZAAPNET TELECOMUNICACOES LTDA

Data as of 2026-09-06

BGP inherited

This organisation

Netblocks	7 · 1,537 IPv4 addresses
IPv6	3 prefixes (largest 2804:2d60:8000::/33)
Record ID	236508332
Registry	BGP
Customers	see who runs inside this network →

Evidence & provenance ?

Attribution	BGP parent (inherited)
Shared handles	clustered on 6 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 (7)

⬇ export CSV

CIDR	Org name	Registry	Status	Confidence
200.219.144.26/32	ZaapNet Telecomunicacoes	PEERINGDB	ASSIGNED	● high
2001:12f8:0:7::26/128	ZaapNet Telecomunicacoes	PEERINGDB	ASSIGNED	● high
168.90.56.0/22	ZAAPNET TELECOMUNICACOES LTDA	ARIN	ALLOCATED	● low
170.231.149.0/24	ZAAPNET TELECOMUNICACOES LTDA	ARIN	ALLOCATED	● low
177.105.245.0/24	ZAAPNET TELECOMUNICACOES LTDA	ARIN	ALLOCATED	● low
2804:2d60::/33	ZAAPNET TELECOMUNICACOES LTDA	BGP	ANNOUNCED	● low
2804:2d60:8000::/33	ZAAPNET TELECOMUNICACOES LTDA	BGP	ANNOUNCED	● low

IPv6 ranges (3)

CIDR
2804:2d60:8000::/33
2804:2d60::/33
2001:12f8:0:7::26/128

Footprint over time

7 weekly snapshots · JSON

7 -11 netblocks since 2026-07-05

2026-07-05 peak 18 2026-09-06

Network trust

what's this?

RPKI hygiene: A how networks compare →

100.0% of checked blocks have valid RPKI ROA coverage (7 of 7)

Possible discrepancies (5)

These blocks are registered to ZAAPNET TELECOMUNICACOES LTDA 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.

2804:2d60::/33 /33	authorized for AS265278 — AS265278
2804:2d60:8000::/33 /33	authorized for AS265278 — AS265278
168.90.56.0/22 /22	authorized for AS265278 — AS265278
170.231.149.0/24 /24	authorized for AS265278 — AS265278
177.105.245.0/24 /24	authorized for AS265278 — AS265278

NIC Handles

23440765000148 AS265278 AS265278 LHVDS8 WDS21 WDS21