Skip to main content

AS267160

ASN267160

JARDIMNET SERVICOS DE INFORMATICA E REDES

Registry

Authoritative registration data

AS number
267160
Name
ASN267160
Organisation
JARDIMNET SERVICOS DE INFORMATICA E REDES
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

7

Total announced

10

Announced prefixes

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

Prefixes announced by AS267160
45.230.96.0/22 IPv4 /22 not checked
45.230.96.0/23 IPv4 /23 not checked
45.230.98.0/23 IPv4 /23 not checked
2804:4908::/32 IPv6 /32 not checked
2804:4908:8000::/33 IPv6 /33 not checked
2804:4908::/33 IPv6 /33 not checked
2804:4908:4000::/34 IPv6 /34 not checked
2804:4908:8000::/34 IPv6 /34 not checked
2804:4908::/34 IPv6 /34 not checked
2804:4908:c000::/34 IPv6 /34 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 AS267160
Address families
IX.br (PTT.br) Recife: 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 AS267160 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS267160 in AS paths

Observed upstreams
Families
AS14840 ASN14840 1,208 3,181
v4 v6
AS264996 ASN264996 299 2,314
v4 v6
AS61568 ASN61568 449 822
v4 v6

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS267160 in AS paths

Observed downstreams
Families
AS268346 ASN268346 869 1,900
v4 v6
AS271409 469 1,470
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS28624 ASN28624 1 7
v6

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.