Skip to main content

AS52840

ASN52840

UFINET BRASIL S.A.

Registry

Authoritative registration data

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

IPv4 prefixes

8

IPv6 prefixes

1

Total announced

9

Announced prefixes

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

Prefixes announced by AS52840
132.255.60.0/22 IPv4 /22 not checked
138.118.24.0/22 IPv4 /22 not checked
177.222.0.0/22 IPv4 /22 not checked
132.255.60.0/23 IPv4 /23 not checked
132.255.62.0/23 IPv4 /23 not checked
138.118.24.0/24 IPv4 /24 not checked
138.118.25.0/24 IPv4 /24 not checked
138.118.26.0/24 IPv4 /24 not checked
2804:be4::/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

Internet Exchange memberships listed for AS52840
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 300,000 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 AS52840 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS52840 in AS paths

Observed upstreams
Families
AS13786 SEABORN 3,308 10,750
v4 v6
AS52468 52468 1,160 3,178
v4 v6
AS6939 HURRICANE 570 1,669
v4 v6
AS6057 6057 39 113
v4 v6
AS35280 F5 27 87
v4 v6
AS53013 ASN53013 43 82
v4
AS61626 ASN61626 10 28
v4 v6
AS7195 7195 7 12
v6
AS273478 ASN273478 2 3
v4

No rows match “”.

Showing – of

Observed downstreams

36 networks seen after AS52840 in AS paths

Observed downstreams
Families
AS270819 ASN270819 263 1,344
v4 v6
AS263310 ASN263310 237 1,191
v4 v6
AS262861 ASN262861 214 1,086
v4 v6
AS262777 ASN262777 113 994
v4 v6
AS271110 ASN271110 220 884
v4 v6
AS268605 ASN268605 276 749
v4 v6
AS52800 ASN52800 178 709
v4
AS265292 ASN265292 156 696
v4
AS263672 ASN263672 171 658
v4 v6
AS263110 ASN263110 88 564
v4 v6
AS263855 ASN263855 155 521
v4 v6
AS272588 ASN272588 218 514
v4 v6
AS263421 ASN263421 150 483
v4 v6
AS61650 344 475
v4 v6
AS270648 ASN270648 260 438
v4 v6
AS263869 ASN263869 158 386
v4 v6
AS265114 ASN265114 170 375
v4 v6
AS267299 ASN267299 87 365
v4 v6
AS264890 ASN264890 189 348
v4 v6
AS267167 ASN267167 223 341
v4 v6
AS264346 ASN264346 41 315
v4
AS268876 ASN268876 89 309
v4 v6
AS269626 ASN269626 129 255
v4 v6
AS270279 ASN270279 153 218
v4
AS263847 ASN263847 148 210
v4 v6
AS52938 ASN52938 139 199
v4
AS263675 ASN263675 86 192
v4
AS266429 ASN266429 149 180
v4
AS262690 ASN262690 110 154
v4 v6
AS269517 ASN269517 77 115
v4 v6
AS265103 ASN265103 66 104
v4 v6
AS264189 ASN264189 16 72
v4
AS263508 ASN263508 39 46
v6
AS52468 52468 13 15
v4
AS61928 ASN61928 1 14
v4
AS273765 ASN273765 1 1
v6

No rows match “”.

Showing – of

Uncertain adjacencies

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