Skip to main content

AS266400

ASN266400

Ferenz Networks

Registry

Authoritative registration data

AS number
266400
Name
ASN266400
Organisation
Ferenz Networks
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

31

IPv6 prefixes

13

Total announced

44

Announced prefixes

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

Prefixes announced by AS266400
170.81.40.0/22 IPv4 /22 not checked
45.224.128.0/22 IPv4 /22 not checked
170.81.40.0/23 IPv4 /23 not checked
170.81.42.0/23 IPv4 /23 not checked
181.214.128.0/23 IPv4 /23 not checked
31.57.174.0/23 IPv4 /23 not checked
45.224.128.0/23 IPv4 /23 not checked
45.224.130.0/23 IPv4 /23 not checked
74.1.74.0/23 IPv4 /23 not checked
74.1.84.0/23 IPv4 /23 not checked
102.165.25.0/24 IPv4 /24 not checked
170.81.40.0/24 IPv4 /24 not checked
170.81.41.0/24 IPv4 /24 not checked
170.81.42.0/24 IPv4 /24 not checked
170.81.43.0/24 IPv4 /24 not checked
181.214.128.0/24 IPv4 /24 not checked
181.214.129.0/24 IPv4 /24 not checked
181.214.230.0/24 IPv4 /24 not checked
181.215.211.0/24 IPv4 /24 not checked
181.215.215.0/24 IPv4 /24 not checked
31.57.174.0/24 IPv4 /24 not checked
31.57.175.0/24 IPv4 /24 not checked
45.224.128.0/24 IPv4 /24 not checked
45.224.129.0/24 IPv4 /24 not checked
45.224.130.0/24 IPv4 /24 not checked
45.224.131.0/24 IPv4 /24 not checked
74.1.74.0/24 IPv4 /24 not checked
74.1.75.0/24 IPv4 /24 not checked
74.1.84.0/24 IPv4 /24 not checked
74.1.85.0/24 IPv4 /24 not checked
96.43.96.0/24 IPv4 /24 not checked
2804:3744::/32 IPv6 /32 RPKI valid
2804:3744:8000::/33 IPv6 /33 RPKI valid
2804:3744::/33 IPv6 /33 RPKI valid
2804:3744:4000::/34 IPv6 /34 RPKI valid
2804:3744:8000::/34 IPv6 /34 RPKI valid
2804:3744::/34 IPv6 /34 RPKI valid
2804:3744:c000::/34 IPv6 /34 not checked
2804:3744:4000::/40 IPv6 /40 RPKI valid
2804:3744:4900::/40 IPv6 /40 RPKI valid
2804:3744:4000::/48 IPv6 /48 RPKI valid
2804:3744:4001::/48 IPv6 /48 RPKI valid
2804:3744:4900::/48 IPv6 /48 not checked
2804:3744:4901::/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

Internet Exchange memberships listed for AS266400
Address families
IX.br (PTT.br) Brasília: ATM/MPLA 100,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Curitiba: ATM/MPLA 200,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Florianópolis: ATM/MPLA 100,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Fortaleza: ATM/MPLA 100,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Porto Alegre: ATM/MPLA 100,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: ATM/MPLA 100,000 Mbps IPv4 · IPv6
PIT Paraguay 100,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 AS266400 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS266400 in AS paths

Observed upstreams
Families
AS3356 LEVEL3 1,133 15,524
v4 v6
AS61624 ASN61624 748 2,767
v4 v6
AS6939 HURRICANE 201 2,372
v4 v6
AS16735 ASN16735 215 1,633
v4 v6
AS52925 ASN52925 7 192
v4
AS53062 ASN53062 134 182
v4
AS137409 GSLNETWORKS-AS-AP 12 150
v4 v6
AS6057 6057 10 114
v4 v6
AS37468 ORG-AC4-AFRINIC 8 82
v4
AS7195 7195 2 4
v6

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS266400 in AS paths

Observed downstreams
Families
AS269412 ASN269412 459 4,886
v4 v6
AS275761 ASN275761 954 3,502
v4 v6
AS273508 ASN273508 176 483
v4 v6
AS275745 ASN275745 314 411
v4 v6
AS264254 ASN264254 258 334
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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