Skip to main content

AS269473

ASN269473

i4 Telecom Eireli

Registry

Authoritative registration data

AS number
269473
Name
ASN269473
Organisation
i4 Telecom Eireli
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

3

Total announced

6

Announced prefixes

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

Prefixes announced by AS269473
45.187.168.0/23 IPv4 /23 not checked
45.187.170.0/24 IPv4 /24 not checked
45.187.171.0/24 IPv4 /24 not checked
2804:652c::/32 IPv6 /32 not checked
2804:652c:8000::/33 IPv6 /33 not checked
2804:652c::/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

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

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS269473 in AS paths

Observed upstreams
Families
AS265377 ASN265377 287 576
v4 v6
AS3356 LEVEL3 237 459
v4 v6
AS273441 ASN273441 287 370
v4
AS1031 PEER1-1031 2 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS269473 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS263152 ASN263152 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.