Skip to main content

AS268209

ASN268209

FENIX TELECOM

Registry

Authoritative registration data

AS number
268209
Name
ASN268209
Organisation
FENIX TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

2

Total announced

7

Announced prefixes

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

Prefixes announced by AS268209
45.235.68.0/23 IPv4 /23 RPKI valid
45.235.68.0/24 IPv4 /24 RPKI valid
45.235.69.0/24 IPv4 /24 not checked
45.235.70.0/24 IPv4 /24 not checked
45.235.71.0/24 IPv4 /24 RPKI valid
2804:4da0:fe00::/40 IPv6 /40 not checked
2804:4da0:ff00::/40 IPv6 /40 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 AS268209
Address families
IX.br (PTT.br) Rio de Janeiro: 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 AS268209 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS268209 in AS paths

Observed upstreams
Families
AS61832 ASN61832 384 668
v4 v6
AS266094 ASN266094 483 667
v4 v6
AS61731 ASN61731 202 243
v4
AS61582 ASN61582 65 89
v4
AS28368 ASN28368 20 31
v4 v6
AS35280 F5 8 24
v4
AS14840 ASN14840 2 10
v4
AS6057 6057 2 4
v4
AS61568 ASN61568 1 2
v4
AS268624 ASN268624 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS268209 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 2
v4
AS264479 ASN264479 1 2
v4
AS271253 ASN271253 1 2
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.