Skip to main content

AS269712

ASN269712

OCTA TELECOM

Registry

Authoritative registration data

AS number
269712
Name
ASN269712
Organisation
OCTA TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

3

Total announced

8

Announced prefixes

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

Prefixes announced by AS269712
190.112.156.0/22 IPv4 /22 not checked
190.112.156.0/23 IPv4 /23 not checked
190.112.158.0/23 IPv4 /23 not checked
190.112.156.0/24 IPv4 /24 not checked
190.112.158.0/24 IPv4 /24 not checked
2804:68bc::/32 IPv6 /32 not checked
2804:68bc:8000::/33 IPv6 /33 RPKI not found
2804:68bc::/33 IPv6 /33 not checked

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

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS269712 in AS paths

Observed upstreams
Families
AS271578 ASN271578 1,171 1,900
v4 v6
AS262503 ASN262503 138 476
v4
AS265269 ASN265269 314 408
v4
AS6939 HURRICANE 120 308
v6
AS14840 ASN14840 2 18
v4 v6
AS6057 6057 4 12
v4 v6
AS137409 GSLNETWORKS-AS-AP 2 3
v4
AS61626 ASN61626 2 2
v4
AS7195 7195 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

1 networks seen after AS269712 in AS paths

Observed downstreams
Families
AS272788 ASN272788 545 712
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

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