Skip to main content

AS61922

ASN61922

CNX TELECOM

Registry

Authoritative registration data

AS number
61922
Name
ASN61922
Organisation
CNX TELECOM
Country
Flag of Brazil BR Brazil
RIR
—
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS61922
200.7.8.0/22 IPv4 /22 not checked
200.7.10.0/23 IPv4 /23 not checked
200.7.8.0/23 IPv4 /23 not checked
200.7.11.0/24 IPv4 /24 not checked
2804:1830::/32 IPv6 /32 RPKI valid

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 AS61922
Address families
IX.br (PTT.br) Brasília: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) Goiânia: ATM/MPLA 10,000 Mbps IPv4 · IPv6
IX.br (PTT.br) São Paulo: 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 AS61922 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

12 networks seen before AS61922 in AS paths

Observed upstreams
Families
AS16735 ASN16735 588 3,444
v4 v6
AS14840 ASN14840 1,410 2,832
v4 v6
AS6939 HURRICANE 436 883
v4 v6
AS35280 F5 16 40
v4 v6
AS6057 6057 10 36
v4 v6
AS137409 GSLNETWORKS-AS-AP 11 26
v4 v6
AS39120 CONVERGENZE-AS 2 3
v4 v6
AS61626 ASN61626 2 3
v4 v6
AS7195 7195 2 2
v6
AS52468 52468 2 2
v6
AS22381 ASN22381 1 1
v6
AS37468 ORG-AC4-AFRINIC 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

5 networks seen after AS61922 in AS paths

Observed downstreams
Families
AS270699 ASN270699 325 2,760
v4 v6
AS262993 ASN262993 615 2,296
v4 v6
AS265476 ASN265476 435 854
v4 v6
AS263343 ASN263343 353 461
v4 v6
AS274506 ASN274506 131 156
v6

No rows match “”.

Showing – of

Uncertain adjacencies

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