PlugZ platform status
Every line below comes from one shared platform snapshot, refreshed at most every 30 seconds. 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
OperationalHTTP 200 · 156ms
Catalog and search
Probe: the catalog query behind the marketplace grid (/sku/search)
OperationalHTTP 200 · 51ms
Infrastructure health
PlugZChain
Probe: height and sync state of the anchoring chain (/chain/status)
OperationalHTTP 200 · 154ms
API Gateway health
Probe: process liveness contract for the gateway reverse-proxy (/health)
OperationalHTTP 200 · 169ms
Geographic lookup
Probe: public geo lookup path (/api/v1/geo/detect/8.8.8.8)
Not respondingHTTP 500 · 169ms
Money-path surface
Payment methods
Probe: card vault contract /payment-methods
DegradedHTTP 401 – endpoint is auth-protected by design · 166ms
Seller connect balance
Probe: Stripe Connect payout-balance read path (/connect/balance)
DegradedHTTP 401 – endpoint is auth-protected by design · 166ms
Seller payouts
Probe: Stripe Connect payouts list path (/connect/payouts)
DegradedHTTP 401 – endpoint is auth-protected by design · 165ms
Seller Connect status
Probe: Stripe Connect account status read path (/connect/accounts/status)
DegradedHTTP 401 – endpoint is auth-protected by design · 165ms
Orders pipeline
Probe: authenticated order collection path (/orders)
DegradedHTTP 401 — endpoint requires auth · 168ms
Wallet pipeline
Probe: authenticated wallet surface (/wallet/wallets)
DegradedHTTP 401 — endpoint requires auth · 166ms
Service comms and security
Secure support careers
Probe: public careers listing from support surface (/support/careers)
OperationalHTTP 200 with payload · 179ms
Verification request
Probe: verification read surface with request id (/verification/:id)
DegradedHTTP 401 — endpoint is auth-protected by design · 167ms
Secure Messaging
Probe: public support surface for secure messaging (/support/faqs)
OperationalHTTP 200 with public FAQ payload · 176ms
Dispute and verification reliability
Disputes
Probe: buyer/seller dispute read/create surface (/disputes)
DegradedHTTP 401 — endpoint is auth-protected by design · 168ms
Node and service availability
PlugZ node health
Probe: aggregated node status snapshot from /api/v1/status
DegradedHTTP 404 — status-page public endpoint is not deployed on this hostname · 268ms
Feature availability surface
Feature flags surface
Probe: publicly available feature availability contract
DegradedHTTP 404 — no public feature-flags contract at this path · 264ms
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).