Skip to main content

AS61610

ASN61610

ELEA DATA CENTERS

Registry

Authoritative registration data

AS number
61610
Name
ASN61610
Organisation
ELEA DATA CENTERS
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

12

IPv6 prefixes

8

Total announced

20

Announced prefixes

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

Prefixes announced by AS61610
200.225.48.0/21 IPv4 /21 not checked
187.87.28.0/22 IPv4 /22 not checked
187.87.28.0/23 IPv4 /23 not checked
187.87.28.0/24 IPv4 /24 not checked
200.225.48.0/24 IPv4 /24 not checked
200.225.49.0/24 IPv4 /24 not checked
200.225.50.0/24 IPv4 /24 not checked
200.225.51.0/24 IPv4 /24 not checked
200.225.52.0/24 IPv4 /24 not checked
200.225.53.0/24 IPv4 /24 not checked
200.225.54.0/24 IPv4 /24 not checked
200.225.55.0/24 IPv4 /24 not checked
2804:8ae0::/32 IPv6 /32 not checked
2804:8ae0:2000::/35 IPv6 /35 RPKI valid
2804:8ae0:4000::/35 IPv6 /35 RPKI valid
2804:8ae0:8000::/35 IPv6 /35 RPKI valid
2804:8ae0::/35 IPv6 /35 not checked
2804:8ae0:a000::/35 IPv6 /35 not checked
2804:8ae0:c000::/35 IPv6 /35 not checked
2804:8ae0:e000::/35 IPv6 /35 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 AS61610
Address families
IX.br (PTT.br) Brasília: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Curitiba: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Porto Alegre: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Rio de Janeiro: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 20,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 AS61610 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS61610 in AS paths

Observed upstreams
Families
AS12956 TELXIUS 405 1,613
v4 v6
AS52468 52468 600 1,534
v4 v6
AS3356 LEVEL3 414 1,272
v4 v6
AS53062 ASN53062 424 959
v4 v6
AS6057 6057 333 548
v4 v6
AS6939 HURRICANE 218 459
v4 v6
AS52863 ASN52863 176 325
v4
AS263558 ASN263558 124 208
v4 v6
AS7738 ASN7738 56 68
v4
AS14840 ASN14840 6 64
v4 v6
AS8167 ASN8167 22 26
v4
AS37468 ORG-AC4-AFRINIC 12 17
v4 v6
AS61626 ASN61626 2 4
v6
AS53013 ASN53013 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

12 networks seen after AS61610 in AS paths

Observed downstreams
Families
AS23074 ASN23074 272 1,440
v4 v6
AS28571 ASN28571 71 796
v4 v6
AS266997 ASN266997 153 534
v4
AS396986 BYTEDANCE 238 517
v4 v6
AS274518 ASN274518 291 338
v4 v6
AS263892 ASN263892 153 172
v4
AS53168 ASN53168 150 172
v4
AS53038 ASN53038 99 111
v4
AS265165 ASN265165 32 37
v4
AS263511 ASN263511 14 25
v6
AS275799 ASN275799 16 17
v6
AS270439 ASN270439 4 5
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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