Service status

Current health for VaultProof public services.

This page checks the public site, init and proxy edge, API control plane, and dashboard path. Use it to confirm whether a setup, scanner, or dashboard issue is local to your app or affecting VaultProof services.

Dashboard Contact support
Overall status
Checking services...

Auto-refresh every 30 seconds. Next check in 30s.

0 operational
0 needs review

Live checks

Core surfaces checked from the browser.

These checks are intentionally lightweight. They confirm that public endpoints respond, not that every customer account or provider integration is healthy.

Public site

Homepage, docs, downloads, and static assets.

Checking
Website edge -- ms

Init and proxy edge

Hosted init, provider catalog, and provider-compatible proxy routes.

Checking
init.vaultproof.dev -- ms

API control plane

Dashboard data, activity, alerts, keys, plans, and account requests.

Checking
api.vaultproof.dev -- ms

Dashboard shell

Login and app routes served from the public web deployment.

Checking
/app/login -- ms

History

Recent public status history.

The public page keeps the status view simple. For account-specific errors, check the dashboard Activity and Alerts pages first.

90 days ago Today
No public incident banner is currently active.

Coverage

What this page does and does not prove.

Status checks help separate a VaultProof availability issue from a local environment or provider configuration issue.

Public availability

Confirms the main web deployment and dashboard shell can load from the browser.

Runtime routing

Checks the init and proxy edge used by generated provider-compatible base URLs.

Control plane

Checks the API surface that powers dashboard operations and account workflows.

Still check your provider A healthy VaultProof route does not guarantee OpenAI, Anthropic, Stripe, or another upstream provider is healthy. If VaultProof is operational, check the provider status page and your provider-side key permissions.

Incident response

What to do if something looks down.

Use these steps to narrow the issue before rotating keys or changing production configuration.

  1. 1

    Check the affected surface

    If only the dashboard is affected, protected provider calls may still be routing. If proxy checks fail, pause risky deploys and avoid repeated retries.

  2. 2

    Review Activity and Alerts

    Open the dashboard when available and compare recent errors, latency, provider route, and request volume.

  3. 3

    Contact support with context

    Include the affected provider, route, timestamp, status code, and whether the issue appears in local, staging, or production.

FAQ

Status page details.

Why can a browser check show degraded when a service is working?

Some network, CORS, browser extension, or local firewall conditions can block a browser health request. If the page shows degraded but your app works, treat it as a signal to investigate rather than a final incident declaration.

Does this page check every customer token?

No. It checks shared public surfaces. Customer-specific token, budget, provider, or configuration issues should be reviewed in Activity, Alerts, Keys, and Settings.

How often does it refresh?

The browser refreshes checks every 30 seconds while the page is open.