Skip to main content

AS19834

CNVR-ORD

Conversant, LLC

Registry

Authoritative registration data

AS number
19834
Name
CNVR-ORD
Organisation
Conversant, LLC
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

6

Total announced

7

Announced prefixes

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

Prefixes announced by AS19834
159.127.104.0/22 IPv4 /22 RPKI not found
2606:ae80:1430::/44 IPv6 /44 RPKI not found
2606:ae80:1c20::/44 IPv6 /44 not checked
2606:ae80:1c30::/44 IPv6 /44 not checked
2606:ae80:1432::/47 IPv6 /47 RPKI not found
2606:ae80:1434::/48 IPv6 /48 RPKI not found
2606:ae80:1435::/48 IPv6 /48 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 AS19834
Address families
Equinix Chicago 200,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 AS19834 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

7 networks seen before AS19834 in AS paths

Observed upstreams
Families
AS6461 ZAYO-6461 189 873
v4 v6
AS6939 HURRICANE 118 818
v4 v6
AS3356 LEVEL3 130 501
v4 v6
AS26762 CNVR-US-EAST 11 70
v6
AS137409 GSLNETWORKS-AS-AP 3 3
v4
AS8220 COLT 2 3
v4
AS25751 VALUECLICK 1 2
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS19834 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 21
v4 v6
AS49544 i3Dnet 1 14
v4 v6
AS1828 UNITAS 1 7
v4 v6
AS36236 NETACTUATE 1 7
v4 v6
AS35280 F5 1 1
v4

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.