Skip to main content

AS268335

ASN268335

ORACLON TELECOM

Registry

Authoritative registration data

AS number
268335
Name
ASN268335
Organisation
ORACLON TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

8

Total announced

16

Announced prefixes

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

Prefixes announced by AS268335
45.238.100.0/22 IPv4 /22 not checked
45.238.100.0/23 IPv4 /23 not checked
45.238.102.0/23 IPv4 /23 not checked
38.211.113.0/24 IPv4 /24 not checked
45.238.100.0/24 IPv4 /24 not checked
45.238.101.0/24 IPv4 /24 not checked
45.238.102.0/24 IPv4 /24 not checked
45.238.103.0/24 IPv4 /24 not checked
2804:4f90::/32 IPv6 /32 RPKI valid
2804:4f90:4000::/34 IPv6 /34 RPKI valid
2804:4f90:8000::/34 IPv6 /34 RPKI valid
2804:4f90::/34 IPv6 /34 RPKI valid
2804:4f90:c000::/34 IPv6 /34 not checked
2804:4f90:200::/40 IPv6 /40 not checked
2804:4f90:200::/41 IPv6 /41 not checked
2804:4f90:4001::/48 IPv6 /48 RPKI valid

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 AS268335 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS268335 in AS paths

Observed upstreams
Families
AS262476 ASN262476 384 1,895
v4 v6
AS6939 HURRICANE 59 360
v4 v6
AS28326 ASN28326 28 31
v4
AS6057 6057 3 21
v4 v6
AS35280 F5 2 16
v4 v6
AS7195 7195 1 4
v6
AS61626 ASN61626 1 4
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS268335 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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