Skip to main content

AS265113

ASN265113

SALES TELECOM LTDA

Registry

Authoritative registration data

AS number
265113
Name
ASN265113
Organisation
SALES TELECOM LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

5

Total announced

12

Announced prefixes

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

Prefixes announced by AS265113
170.254.108.0/22 IPv4 /22 not checked
170.254.108.0/23 IPv4 /23 not checked
170.254.110.0/23 IPv4 /23 RPKI valid
170.254.108.0/24 IPv4 /24 RPKI valid
170.254.109.0/24 IPv4 /24 RPKI valid
170.254.110.0/24 IPv4 /24 RPKI valid
170.254.111.0/24 IPv4 /24 RPKI valid
2804:330c::/32 IPv6 /32 not checked
2804:330c:4000::/34 IPv6 /34 RPKI valid
2804:330c:8000::/34 IPv6 /34 RPKI valid
2804:330c::/34 IPv6 /34 not checked
2804:330c:c000::/34 IPv6 /34 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 AS265113 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS265113 in AS paths

Observed upstreams
Families
AS13786 SEABORN 397 1,432
v4 v6
AS6939 HURRICANE 108 782
v4 v6
AS52468 52468 174 429
v4 v6
AS35280 F5 7 44
v4 v6
AS137409 GSLNETWORKS-AS-AP 6 28
v4 v6
AS6057 6057 2 24
v4 v6
AS10733 ASN10733 3 9
v4 v6
AS61626 ASN61626 1 9
v4 v6
AS7195 7195 1 4
v6
AS39120 CONVERGENZE-AS 1 4
v4
AS53013 ASN53013 1 3
v4

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS265113 in AS paths

Observed downstreams
Families
AS268710 ASN268710 174 487
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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