Skip to main content

AS264982

ASN264982

Rio Telecom LTDA

Registry

Authoritative registration data

AS number
264982
Name
ASN264982
Organisation
Rio Telecom LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

5

Total announced

9

Announced prefixes

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

Prefixes announced by AS264982
170.0.132.0/24 IPv4 /24 not checked
170.0.133.0/24 IPv4 /24 not checked
170.0.134.0/24 IPv4 /24 not checked
170.0.135.0/24 IPv4 /24 not checked
2804:30f0:100::/40 IPv6 /40 not checked
2804:30f0:200::/40 IPv6 /40 not checked
2804:30f0::/40 IPv6 /40 not checked
2804:30f0:200::/41 IPv6 /41 not checked
2804:30f0:280::/41 IPv6 /41 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 AS264982 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

13 networks seen before AS264982 in AS paths

Observed upstreams
Families
AS265269 ASN265269 427 700
v4 v6
AS28165 ASN28165 395 671
v4 v6
AS14840 ASN14840 383 500
v4 v6
AS6939 HURRICANE 119 383
v4 v6
AS28260 ASN28260 264 332
v4
AS22381 ASN22381 42 73
v4 v6
AS35280 F5 6 16
v4 v6
AS137409 GSLNETWORKS-AS-AP 5 9
v4 v6
AS6057 6057 2 8
v4 v6
AS7195 7195 1 3
v6
AS37468 ORG-AC4-AFRINIC 1 2
v6
AS39120 CONVERGENZE-AS 1 2
v6
AS61626 ASN61626 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS264982 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.