Skip to main content

AS271733

ASN271733

JRNET COMUNICACAO

Registry

Authoritative registration data

AS number
271733
Name
ASN271733
Organisation
JRNET COMUNICACAO
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

8

Total announced

13

Announced prefixes

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

Prefixes announced by AS271733
45.227.124.0/23 IPv4 /23 not checked
45.227.124.0/24 IPv4 /24 not checked
45.227.125.0/24 IPv4 /24 not checked
45.227.126.0/24 IPv4 /24 not checked
45.227.127.0/24 IPv4 /24 not checked
2804:8028::/32 IPv6 /32 RPKI not found
2804:8028:8000::/33 IPv6 /33 RPKI not found
2804:8028::/33 IPv6 /33 RPKI not found
2804:8028:4000::/34 IPv6 /34 RPKI not found
2804:8028:8000::/34 IPv6 /34 RPKI not found
2804:8028::/34 IPv6 /34 not checked
2804:8028:c000::/34 IPv6 /34 not checked
2804:8028::/40 IPv6 /40 RPKI not found

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 AS271733
Address families
IX.br (PTT.br) São Paulo: ATM/MPLA 25,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 AS271733 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

8 networks seen before AS271733 in AS paths

Observed upstreams
Families
AS11432 ASN11432 465 1,266
v4 v6
AS263966 ASN263966 528 1,151
v4 v6
AS6939 HURRICANE 120 550
v4 v6
AS35280 F5 7 28
v4 v6
AS137409 GSLNETWORKS-AS-AP 8 18
v4 v6
AS6057 6057 2 12
v4 v6
AS61626 ASN61626 1 6
v4 v6
AS39120 CONVERGENZE-AS 1 3
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS271733 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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