Skip to main content

AS264071

ASN264071

HOPNET TELECOM LTDA

Registry

Authoritative registration data

AS number
264071
Name
ASN264071
Organisation
HOPNET TELECOM LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

7

Total announced

12

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS264071
143.137.44.0/22 IPv4 /22 not checked
143.137.44.0/23 IPv4 /23 not checked
143.137.46.0/23 IPv4 /23 not checked
143.137.45.0/24 IPv4 /24 not checked
143.137.47.0/24 IPv4 /24 not checked
2804:2a5c::/32 IPv6 /32 RPKI valid
2804:2a5c:8000::/33 IPv6 /33 RPKI valid
2804:2a5c::/33 IPv6 /33 RPKI valid
2804:2a5c:4000::/34 IPv6 /34 RPKI valid
2804:2a5c:8000::/34 IPv6 /34 RPKI valid
2804:2a5c::/34 IPv6 /34 RPKI valid
2804:2a5c:c000::/34 IPv6 /34 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS264071
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 1,024 Mbps IPv4 · IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS264071 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS264071 in AS paths

Observed upstreams
Families
AS52468 52468 643 2,113
v4 v6
AS6939 HURRICANE 124 780
v4 v6
AS11432 ASN11432 199 288
v4 v6
AS35280 F5 6 33
v4 v6
AS137409 GSLNETWORKS-AS-AP 5 21
v4 v6
AS6057 6057 2 18
v4 v6
AS53013 ASN53013 2 4
v4
AS39120 CONVERGENZE-AS 1 4
v6
AS61626 ASN61626 1 4
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS264071 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

17 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.