Skip to main content

AS52376

52376

Autonomous System AS52376 from AR-CCAB-LACNIC

Registry

Authoritative registration data

AS number
52376
Name
52376
Organisation
Autonomous System AS52376 from AR-CCAB-LACNIC
Country
—
RIR
LACNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

3

Total announced

10

Announced prefixes

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

Prefixes announced by AS52376
2.20.46.0/24 IPv4 /24 not checked
200.115.94.0/24 IPv4 /24 not checked
200.115.95.0/24 IPv4 /24 not checked
200.9.157.0/24 IPv4 /24 not checked
201.182.134.0/24 IPv4 /24 not checked
201.182.140.0/24 IPv4 /24 not checked
23.204.102.0/24 IPv4 /24 not checked
2001:13c7:600a::/48 IPv6 /48 not checked
2600:1419:6000::/48 IPv6 /48 RPKI valid
2801:168:5::/48 IPv6 /48 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 AS52376
Address families
AR-IX Cabase - Argentina 1,740,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 10,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 AS52376 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS52376 in AS paths

Observed upstreams
Families
AS263194 263194 6,592 9,651
v4 v6
AS16814 16814 5,259 7,385
v4 v6
AS52324 52324 409 538
v4
AS6939 HURRICANE 110 350
v4 v6
AS27984 27984 17 19
v4
AS22356 ASN22356 6 18
v4 v6
AS6057 6057 4 18
v4 v6
AS137409 GSLNETWORKS-AS-AP 5 7
v4 v6
AS52468 52468 2 3
v6
AS61626 ASN61626 2 2
v6

No rows match “”.

Showing – of

Observed downstreams

24 networks seen after AS52376 in AS paths

Observed downstreams
Families
AS52294 52294 1,280 1,676
v4 v6
AS52374 52374 1,236 1,640
v4 v6
AS52500 52500 761 988
v4 v6
AS61553 61553 682 981
v4 v6
AS52404 52404 725 966
v4 v6
AS61521 61521 693 965
v4 v6
AS52509 52509 637 965
v4 v6
AS52360 52360 532 707
v4 v6
AS52375 52375 516 675
v4 v6
AS52324 52324 427 574
v4 v6
AS61504 61504 383 562
v4 v6
AS52508 52508 441 561
v4 v6
AS52332 52332 437 560
v4 v6
AS61495 61495 437 560
v4 v6
AS64106 64106 436 560
v4 v6
AS52403 52403 436 559
v4 v6
AS52370 52370 435 559
v4 v6
AS52359 52359 257 334
v4 v6
AS61441 61441 229 285
v4
AS7303 7303 159 206
v4
AS16814 16814 135 178
v4
AS11664 11664 129 170
v4
AS64104 64104 83 117
v6
AS7049 7049 3 3
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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