Skip to main content

AS265292

ASN265292

UFINET BRASIL S.A.

Registry

Authoritative registration data

AS number
265292
Name
ASN265292
Organisation
UFINET BRASIL S.A.
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS265292
168.121.0.0/22 IPv4 /22 not checked
168.121.0.0/24 IPv4 /24 not checked
168.121.1.0/24 IPv4 /24 not checked
168.121.3.0/24 IPv4 /24 not checked
2804:2d9c::/32 IPv6 /32 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS265292 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS265292 in AS paths

Observed upstreams
Families
AS52840 ASN52840 239 1,124
v4
AS6939 HURRICANE 106 130
v6
AS35280 F5 6 7
v6
AS137409 GSLNETWORKS-AS-AP 3 3
v6
AS6057 6057 2 2
v6
AS7195 7195 1 1
v6
AS39120 CONVERGENZE-AS 1 1
v6
AS52468 52468 1 1
v6
AS61626 ASN61626 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS265292 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

14 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.