Skip to main content

AS264355

ASN264355

Cais Network

Registry

Authoritative registration data

AS number
264355
Name
ASN264355
Organisation
Cais Network
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

0

Total announced

5

Announced prefixes

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

Prefixes announced by AS264355
131.108.240.0/22 IPv4 /22 not checked
131.108.240.0/24 IPv4 /24 not checked
131.108.241.0/24 IPv4 /24 not checked
131.108.242.0/24 IPv4 /24 not checked
131.108.243.0/24 IPv4 /24 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 AS264355 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS264355 in AS paths

Observed upstreams
Families
AS264293 ASN264293 155 1,003
v4
AS28598 ASN28598 116 575
v4
AS6939 HURRICANE 31 148
v4
AS6057 6057 2 8
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS264355 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS262427 ASN262427 1 4
v4
AS264479 ASN264479 1 4
v4
AS61573 ASN61573 1 3
v4

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.