PlugZ LogoPlugZ

PlugZ platform status

Every line below comes from a shared snapshot reused for up to 30 seconds. After it expires, this page waits for fresh probes. Measured at records when the probes completed. Each line names the exact probe target, so green only means that contract answered that snapshot.

Measured at (UTC)

Core public surfaces

  • Accounts and sign-in

    Probe: public signing keys (/.well-known/jwks.json) — the same keys that validate a session

    Operational

    HTTP 200 · 1207ms

  • Catalog and search

    Probe: the catalog query behind the marketplace grid (/sku/search)

    Operational

    HTTP 200 · 783ms

Infrastructure health

  • PlugZChain

    Probe: height and sync state of the anchoring chain (/chain/status)

    Operational

    HTTP 200 · 721ms

  • API Gateway health

    Probe: process liveness contract for the gateway reverse-proxy (/health)

    Operational

    HTTP 200 · 1204ms

  • Geographic lookup

    Probe: public geo lookup path (/api/v1/geo/detect/8.8.8.8)

    Operational

    HTTP 200 with geo payload · 1204ms

Money-path surface

  • Payment methods

    Probe: card vault contract /payment-methods

    Protected

    HTTP 401 — the auth gate answered, which is the contract here · 1203ms

  • Seller connect balance

    Probe: Stripe Connect payout-balance read path (/connect/balance)

    Protected

    HTTP 401 — the auth gate answered, which is the contract here · 1202ms

  • Seller payouts

    Probe: Stripe Connect payouts list path (/connect/payouts)

    Protected

    HTTP 401 — the auth gate answered, which is the contract here · 1201ms

  • Seller Connect status

    Probe: Stripe Connect account status read path (/connect/accounts/status)

    Protected

    HTTP 401 — the auth gate answered, which is the contract here · 1201ms

  • Orders pipeline

    Probe: authenticated order collection path (/orders)

    Protected

    HTTP 401 — the auth gate answered, which is the contract here · 1204ms

  • Wallet pipeline

    Probe: authenticated wallet surface (/wallet/wallets)

    Protected

    HTTP 401 — the auth gate answered, which is the contract here · 1204ms

Service comms and security

  • Secure support careers

    Probe: public careers listing from support surface (/support/careers)

    Operational

    HTTP 200 with payload · 1201ms

  • Verification request

    Probe: verification read surface with request id (/verification/:id)

    Protected

    HTTP 401 — the auth gate answered, which is the contract here · 1201ms

  • Secure Messaging

    Probe: public support surface for secure messaging (/support/faqs)

    Operational

    HTTP 200 with public FAQ payload · 1201ms

Dispute and verification reliability

  • Disputes

    Probe: buyer/seller dispute read/create surface (/disputes)

    Protected

    HTTP 401 — the auth gate answered, which is the contract here · 1201ms

Node and service availability

  • PlugZ node health

    Probe: aggregated node status snapshot from /api/v1/status

    Degraded

    HTTP 404 — status-page public endpoint is not deployed on this hostname · 1215ms

Feature availability surface

  • Feature flags surface

    Probe: publicly available feature availability contract

    Degraded

    HTTP 404 — no public feature-flags contract at this path · 1213ms

Not covered by this page

  • Escrow and payout settlement include non-public/internal orchestration steps not suitable for this public status surface.
  • Payment creation and wallet top-up are mutations. This public page never probes them with POST requests.
  • Verification and shipping ops are internal or partner-integrated today; no read-only probe surface here yet.
  • Feature flags are currently a private/authenticated concern in this architecture path.

Reporting a problem

If something is broken while this page is green, that gap is itself worth reporting: support@plugz.market. Security issues go to security@plugz.market (see /.well-known/security.txt).