Skip to main content

AS270820

ASN270820

COMPUNET DO BRASIL TELECOM LTDA

Registry

Authoritative registration data

AS number
270820
Name
ASN270820
Organisation
COMPUNET DO BRASIL TELECOM LTDA
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

7

IPv6 prefixes

3

Total announced

10

Announced prefixes

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

Prefixes announced by AS270820
186.194.168.0/22 IPv4 /22 not checked
186.194.168.0/23 IPv4 /23 not checked
186.194.170.0/23 IPv4 /23 not checked
186.194.168.0/24 IPv4 /24 not checked
186.194.169.0/24 IPv4 /24 not checked
186.194.170.0/24 IPv4 /24 not checked
186.194.171.0/24 IPv4 /24 not checked
2804:71ec::/32 IPv6 /32 RPKI valid
2804:71ec:8000::/33 IPv6 /33 RPKI valid
2804:71ec::/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 AS270820
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 AS270820 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS270820 in AS paths

Observed upstreams
Families
AS27693 ASN27693 1,239 5,099
v4 v6
AS22381 ASN22381 925 3,416
v4 v6
AS6939 HURRICANE 161 447
v4 v6
AS35280 F5 8 40
v4 v6
AS137409 GSLNETWORKS-AS-AP 6 20
v4 v6
AS6057 6057 4 20
v4 v6
AS39120 CONVERGENZE-AS 1 4
v4 v6
AS61626 ASN61626 1 4
v4 v6
AS7195 7195 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS270820 in AS paths

Observed downstreams
Families
AS53213 ASN53213 570 4,785
v4 v6
AS52893 ASN52893 473 1,529
v4 v6
AS263606 ASN263606 279 356
v4

No rows match “”.

Showing – of

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.