Cargo A/C

Service Status

Live health of the cargo.ac identity backbone and every registered spoke — the source feed for the future status.cargo.ac page.

Core services

4

Auth, admin, bridge, API

Registered spokes

14

Apps, consoles & sites

Verified origins

4/14

Production-confirmed

Open incidents

0

No active disruptions

Core platform

  • auth.cargo.ac (Identity Provider)

    Token issuer for every ecosystem surface.

    Operational
  • admin.cargo.ac (this console)

    Internal super-admin control plane.

    Operational
  • go.cargo.ac (reserved)

    Reserved namespace — not deployed, not part of any active auth flow.

    Reserved
  • api.cargo.ac (reserved)

    Reserved namespace — identity API shape lives inside existing projects.

    Reserved

Spoke connectivity

  • CW Network HUB

    https://cargoworks.network

    internal
    Reachable
  • Exchange

    https://exchange.cargoworks.network

    internal
    Awaiting heartbeat
  • CargoWorks ID

    https://id.cargoworks.network

    internal
    Awaiting heartbeat
  • Expert

    https://expert.cargoworks.network

    internal
    Awaiting heartbeat
  • Support

    https://cargoworks.support

    internal
    Reachable
  • Delivery

    https://delivery.cargoworks.network

    internal
    Awaiting heartbeat
  • Cloud

    https://cloud.cargoworks.network

    internal
    Awaiting heartbeat
  • CargoWorks AI

    https://exim.cargoworks.ai

    client
    Reachable
  • CargoWorks IO

    https://track.cargoworks.io

    client
    Awaiting heartbeat
  • Cargo Directory

    https://global.cargo.directory

    client
    Awaiting heartbeat
  • Cargo E-Mail

    https://cargo.email

    client
    Awaiting heartbeat
  • CW AI Website

    https://cargoworks.ai

    website
    Awaiting heartbeat
  • CW IO Website

    https://cargoworks.io

    website
    Reachable
  • Directory Website

    https://cargodirectory.io

    website
    Awaiting heartbeat

Connectivity is derived from the federation registry. Live heartbeats land here once each spoke posts to the App Telemetry endpoint (Applications → Telemetry).