Skip to main content

AS273798

ASN273798

JS MELO COMUNICAÇÂO MULTIMIDIA LTDA

Registry

Authoritative registration data

AS number
273798
Name
ASN273798
Organisation
JS MELO COMUNICAÇÂO MULTIMIDIA LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

3

Total announced

4

Announced prefixes

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

Prefixes announced by AS273798
187.109.121.0/24 IPv4 /24 not checked
2804:8c5c::/32 IPv6 /32 not checked
2804:8c5c:8000::/33 IPv6 /33 RPKI valid
2804:8c5c::/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

Internet Exchange memberships listed for AS273798
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 AS273798 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS273798 in AS paths

Observed upstreams
Families
AS28220 ASN28220 126 203
v4 v6
AS6939 HURRICANE 58 188
v4 v6
AS28359 ASN28359 36 49
v4 v6
AS35280 F5 3 10
v4 v6
AS6057 6057 2 8
v4 v6
AS61626 ASN61626 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS273798 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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