# RingConn (Gen 2 / Gen 3) at Global: deployment

Canonical ID: `00b193b7-77d2-4b3e-8a27-fcbe74ec0cc5`

Aggregate global 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-global
- **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:** [Global](/locations/global.md) (id: `6753d6b9-d63f-41f8-b672-4d80bdb4dd82`)

## 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 Global?

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

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

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 Global?

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/00b193b7-77d2-4b3e-8a27-fcbe74ec0cc5 · feeds: GET /v1/feeds?deploymentId=00b193b7-77d2-4b3e-8a27-fcbe74ec0cc5 · canonical URL: /deployments/ringconn-gen2-global_