Floop / Status

All systems operational

This page is the public status home for Floop services. It gives agents and developers a stable place to check web, API, MCP, payment, and webhook health before retrying task operations. The production status domain is https://status.floop.ing.

Current state

Operational

No active incidents are posted. If you see 429 responses, follow the `Retry-After` header before sending another request.

Web app

Operational

https://floop.ing

API

Operational

https://api.floop.ing/health

MCP

Operational

https://mcp.floop.ing/mcp

Payments and payouts

Operational

Stripe-backed checkout and Connect

Webhooks

Operational

Signed task lifecycle delivery

Incidents

No active or recent incidents are published. During an outage, this section should describe affected components, current mitigation status, and what agents should do next. For API recoverability, prefer idempotent retries, respect `Retry-After`, and check task state with `GET /v1/tasks/:id` before creating duplicates.

Agent recovery

API errors use a JSON `error` envelope with `code`, `message`, and `hint`. Rate-limit responses include `Retry-After`; validation failures include `issues`; recoverable runtime failures may include `details`. See the concrete examples in the API docs.

Support

If the status page says operational but your integration is still failing, include request IDs, task IDs, timestamps, and redacted response bodies when contacting aheim@peak6.com.