System Status

Check MyClaude system status at GET /api/health or programmatically via curl. All components are independently monitored.

Current status

MyClaude launched on March 25, 2026. All systems are operational. As the platform builds a track record, this page will include historical uptime data and incident reports.

Health check endpoint

MyClaude exposes a health check endpoint that returns the status of core dependencies.

Request

$ curl https://myclaude.sh/api/health

Response

{
  "status": "ok",
  "timestamp": "2026-03-25T12:00:00.000Z",
  "components": {
    "firestore": "ok",
    "auth": "ok",
    "storage": "ok"
  }
}

A 200 response with "status": "ok" means all systems are functioning normally. A 200 with "status": "degraded" means the platform is partially functional — check the components object for details. A 503 response means the platform is experiencing a significant outage.

Programmatic monitoring

You can integrate the health endpoint into your own monitoring. Example with a cron job:

# Check every 5 minutes, alert if not ok
*/5 * * * * curl -sf https://myclaude.sh/api/health | grep -q '"status":"ok"' || echo "MyClaude health check failed" | mail -s "Alert" you@example.com

For CI/CD pipelines that depend on MyClaude (for example, publishing products as part of a release process):

# Bail out if MyClaude is down
STATUS=$(curl -sf https://myclaude.sh/api/health | jq -r '.status')
if [ "$STATUS" != "ok" ]; then
  echo "MyClaude is not healthy (status: $STATUS). Skipping publish."
  exit 1
fi
myclaude publish

Monitored components

Each component is monitored independently. A failure in one component does not necessarily affect others.

Web application

The Next.js application running on Vercel. Handles all page rendering (server-side and client-side), static assets, and the user interface.

Depends on: Vercel edge network, Firebase Auth (for authenticated pages), Firestore (for SSR pages).

Impact if down: Users cannot browse the marketplace or access their dashboard. The CLI continues to function if the API layer is served independently.

API layer

The /api/* routes that handle all mutations: authentication verification, Stripe checkout session creation, product publishing, file downloads, and webhook processing.

Depends on: Firebase Admin SDK, Stripe API, Cloudflare R2.

Impact if down: No purchases, no publishing, no downloads. Browse continues to work via cached SSR.

CLI registry

The @myclaude-cli/cli npm package. The CLI itself is a thin client — once installed, it calls the API layer for all operations.

Depends on: npm registry (for installation and updates), API layer (for all commands except myclaude version).

Impact if down: Cannot install or update the CLI. Existing installations continue to work if the API layer is available.

Stripe payments

Stripe processes all payment transactions, manages creator Connect accounts, and fires webhooks for order creation.

Depends on: Stripe's infrastructure (external).

Impact if down: Cannot purchase paid products. Free product installs still work. Existing orders and downloads are unaffected.

Firebase Auth

Handles user registration, login, and JWT token issuance/verification.

Depends on: Google Cloud (Firebase's underlying infrastructure).

Impact if down: Cannot log in, register, or perform any authenticated action. Unauthenticated browsing of public listings continues to work.

Incident response

When an issue affects platform availability or data integrity, MyClaude follows this process:

1. Detection — Automated monitoring or user report identifies the issue
2. Acknowledgment — Team confirms the issue and begins investigation
3. Communication — Status update posted (currently via this page and support channels)
4. Resolution — Fix deployed and verified
5. Post-mortem — For significant incidents, a post-mortem is published with root cause and prevention measures

Response time targets

These are targets for the launch period. As the platform matures, we will formalize SLAs.

Reporting issues

If you encounter a problem that is not reflected on this page:

When reporting a bug, include:

• What you were trying to do
• What happened instead
• Your CLI version (myclaude version) if applicable
• Browser and OS if it is a web issue
• Any error messages you received

Future plans

A dedicated status page with real-time component monitoring, historical uptime graphs, and incident timeline is planned. Until then, this page and the /api/health endpoint are the primary status indicators.

Planned improvements:

• Dedicated status page (status.myclaude.sh) with live dashboard
• Automated incident notifications via email for subscribed users
• Historical uptime percentages per component
• Scheduled maintenance window announcements

Related pages

• Changelog — platform version history and upcoming features
• Architecture — how the system is built
• Vulnerability Disclosure — how to report security issues