# RingConn (Gen 2 / Gen 3) at North America: deployment

Canonical ID: `c2b615dc-23a6-4ece-8687-580deefff93c`

North American operational deployment. RingConn (Gen 2 / Gen 3) operations.

**Trust tier:** Catalog entry · 1 source · not yet field-verified

_Last updated: 2026-06-08_

- **Slug:** ringconn-gen2-north-america
- **Status:** operational
- **Model:** [RingConn (Gen 2 / Gen 3)](/models/ringconn-gen2.md) (id: `da93282e-f971-48ed-aa6a-0c795348314d`)
- **Company:** [RingConn](/companies/ringconn.md) (id: `dd249a2a-1d52-4dfd-8578-6d2cf51ad6a3`)
- **Location:** [North America](/locations/north-america.md) (id: `aaf012fa-168b-4846-953c-a3295195aebc`)

## Verification log (0, append-only)

_No verifications recorded._

## Sources (1)

1. https://rover.report

## Common questions

### What is the RingConn (Gen 2 / Gen 3) deployment at North America?

RingConn (Gen 2 / Gen 3), built by RingConn, is recorded as a deployment at North America on the DEPLOY registry. RingConn operates the deployment directly.

### Who operates RingConn (Gen 2 / Gen 3) at North America?

RingConn, the manufacturer of RingConn (Gen 2 / Gen 3), operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.

### Have there been incidents at the RingConn (Gen 2 / Gen 3) deployment at North America?

No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.


_API: GET /v1/robots/c2b615dc-23a6-4ece-8687-580deefff93c · feeds: GET /v1/feeds?deploymentId=c2b615dc-23a6-4ece-8687-580deefff93c · canonical URL: /deployments/ringconn-gen2-north-america_