Skip to main content

AS264900

ASN264900

RJNET Telecomunicacoes Ltda ME

Registry

Authoritative registration data

AS number
264900
Name
ASN264900
Organisation
RJNET Telecomunicacoes Ltda ME
Country
Flag of Brazil BR Brazil
RIR
—
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 AS264900
168.228.8.0/22 IPv4 /22 not checked
170.80.236.0/22 IPv4 /22 not checked
168.228.10.0/23 IPv4 /23 not checked
168.228.8.0/23 IPv4 /23 not checked
170.80.236.0/23 IPv4 /23 not checked
170.80.238.0/23 IPv4 /23 not checked
168.228.11.0/24 IPv4 /24 not checked
2804:2f94::/32 IPv6 /32 RPKI valid
2804:2f94:8000::/33 IPv6 /33 RPKI valid
2804:2f94::/33 IPv6 /33 RPKI valid

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS264900 in AS paths

Observed upstreams
Families
AS14840 ASN14840 430 1,216
v4 v6
AS28283 ASN28283 454 1,059
v4 v6
AS3356 LEVEL3 332 1,058
v4 v6
AS262907 ASN262907 106 133
v4
AS6057 6057 2 6
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS264900 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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