Skip to main content

AS52721

ASN52721

TOLEDO FIBRA TELECOMUNICAÇAO LTDA

Registry

Authoritative registration data

AS number
52721
Name
ASN52721
Organisation
TOLEDO FIBRA TELECOMUNICAÇAO LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

21

IPv6 prefixes

5

Total announced

26

Announced prefixes

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

Prefixes announced by AS52721
138.185.108.0/22 IPv4 /22 not checked
170.246.96.0/22 IPv4 /22 not checked
177.84.108.0/22 IPv4 /22 not checked
138.185.108.0/23 IPv4 /23 not checked
138.185.110.0/23 IPv4 /23 not checked
170.246.96.0/23 IPv4 /23 not checked
170.246.98.0/23 IPv4 /23 not checked
177.84.108.0/23 IPv4 /23 not checked
177.84.110.0/23 IPv4 /23 not checked
138.185.108.0/24 IPv4 /24 not checked
138.185.109.0/24 IPv4 /24 RPKI not found
138.185.110.0/24 IPv4 /24 not checked
138.185.111.0/24 IPv4 /24 RPKI not found
170.246.96.0/24 IPv4 /24 RPKI not found
170.246.97.0/24 IPv4 /24 not checked
170.246.98.0/24 IPv4 /24 not checked
170.246.99.0/24 IPv4 /24 not checked
177.84.108.0/24 IPv4 /24 not checked
177.84.109.0/24 IPv4 /24 not checked
177.84.110.0/24 IPv4 /24 RPKI not found
177.84.111.0/24 IPv4 /24 RPKI not found
2804:2664::/32 IPv6 /32 RPKI not found
2804:2664:4000::/34 IPv6 /34 not checked
2804:2664:8000::/34 IPv6 /34 RPKI not found
2804:2664::/34 IPv6 /34 RPKI not found
2804:2664:c000::/34 IPv6 /34 RPKI not found

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 AS52721
Address families
IX.br (PTT.br) Fortaleza: ATM/MPLA 100,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 100,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 AS52721 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS52721 in AS paths

Observed upstreams
Families
AS7195 7195 2,023 7,935
v4 v6
AS267613 ASN267613 641 3,585
v4 v6
AS6939 HURRICANE 360 2,140
v4 v6
AS22356 ASN22356 286 1,131
v4 v6
AS14840 ASN14840 7 194
v4 v6
AS1031 PEER1-1031 50 151
v4 v6
AS6057 6057 16 108
v4 v6
AS3303 SWISSCOM 11 34
v4
AS137409 GSLNETWORKS-AS-AP 6 30
v4
AS33891 CORE-BACKBONE 4 10
v4

No rows match “”.

Showing – of

Observed downstreams

7 networks seen after AS52721 in AS paths

Observed downstreams
Families
AS61719 ASN61719 335 3,422
v6
AS264088 ASN264088 676 2,855
v4 v6
AS268737 ASN268737 822 2,140
v4 v6
AS266517 ASN266517 477 1,248
v4 v6
AS269038 ASN269038 253 323
v4
AS275615 ASN275615 232 316
v6
AS266613 ASN266613 41 57
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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