Skip to main content

AS268860

ASN268860

74 JC INFORMATICA LTDA

Registry

Authoritative registration data

AS number
268860
Name
ASN268860
Organisation
74 JC INFORMATICA LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

8

IPv6 prefixes

3

Total announced

11

Announced prefixes

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

Prefixes announced by AS268860
45.173.84.0/22 IPv4 /22 not checked
45.173.84.0/23 IPv4 /23 not checked
45.173.86.0/23 IPv4 /23 not checked
45.173.84.0/24 IPv4 /24 not checked
45.173.85.0/24 IPv4 /24 not checked
45.173.86.0/24 IPv4 /24 not checked
45.173.87.0/24 IPv4 /24 not checked
87.120.130.0/24 IPv4 /24 RPKI valid
2804:5ba4::/32 IPv6 /32 not checked
2804:5ba4:8000::/48 IPv6 /48 RPKI valid
2804:5ba4::/48 IPv6 /48 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 AS268860
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 5,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 AS268860 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS268860 in AS paths

Observed upstreams
Families
AS267056 ASN267056 771 3,507
v4 v6
AS10733 ASN10733 424 1,067
v4 v6
AS6939 HURRICANE 220 685
v4 v6
AS266931 ASN266931 241 637
v4
AS267280 ASN267280 50 73
v6
AS6057 6057 6 34
v4 v6
AS137409 GSLNETWORKS-AS-AP 7 29
v4 v6
AS61626 ASN61626 1 1
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS268860 in AS paths

Observed downstreams
Families
AS52675 ASN52675 302 1,919
v4
AS272477 ASN272477 366 714
v4 v6
AS267280 ASN267280 2 3
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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