Status & Incidents
Status & Incidents
There is no public status page for the PirateCrew Blockchain API yet. This page documents what to check during a suspected outage and where incident updates are posted.
Check liveness
The fastest way to confirm the API is reachable is a GET against the unauthenticated health endpoint:
curl https://api.piratecrew.fun/v2/health{
"data": {
"status": "healthy",
"service": "PirateCrew Blockchain API",
"version": "v2"
},
"meta": {
"request_id": "req_…",
"timestamp": "2026-05-19T18:42:11.000Z"
}
}A non-200 response, or a connection failure, means the service itself is down. A 200 response means the HTTP layer is up — it does not prove that the upstream Solana RPC, Privy, Supabase, or Helius are healthy.
Layered failure modes
When something looks broken, walk the stack:
- API process —
GET /v2/health. Non-200 or timeout → API is down. - Authentication — A
401/403on every request usually means a rotated or revoked key, not an outage. Generate a new key ondeveloper.piratecrew.funand retry. - Solana RPC — Symptoms include
POST /v2/transactionsreturning blockhash errors,GET /v2/accounts/{address}500ing, or transactions never confirming viaGET /v2/transactions/{signature}. Cross-check at status.solana.com. - Helius — Asset reads (
/v2/accounts/*with rich metadata,GET /v2/tokens/{mint}) degrade if Helius has an incident. The API will surface 502s in that case. - Jito — Bundle landings via
POST /v2/transactionswithbundle: truecan fail independently of the main RPC. Fall back to a non-bundled submit if you don't need bundle atomicity.
Where incidents are announced
Until a hosted status page exists, real-time updates are posted in the PirateCrew Discord, in the #dev channel. Major incidents are pinned for the duration of the outage and resolved with a post-mortem note afterwards.
If you need to escalate an active incident — for example, a launch-day partner integration is blocked — ping in #dev with your API key prefix and a brief description. See Contact for other channels.
A hosted status page is on the roadmap. When it lands it'll be linked from this page.