Crypto ETF Status
system status · checked every minute from cloudflare's network · updated 16:43 utc

OPERATIONAL

All three services answer normally.

Last incident: Sun 11 Oct, API and MCP server unreachable for 1 min.

Services

uptime = share of successful checks
service status now 24 h avg 24 h 90 days response time · 24 h
Website
cryptoetf.today
Up
267 ms
292 ms
100.00%
99.68%
API
api.cryptoetf.today
Up
254 ms
287 ms
100.00%
99.55%
MCP server
mcp.cryptoetf.today · on API backend
Up
321 ms
301 ms
100.00%
99.54%

Uptime · 90 days

≥ 99.9% 99–99.9% below 99% no data
Website99.68%
API99.55%
MCP server99.54%
17 julmonitoring started 30 augtoday

Response time · 24 hours

avg 287 ms peak 369 ms failed checks 0 15-min window with a failure
430 ms215 ms0 ms
24 h ago12 h agonow

Incidents · last 30 days

4 incidents · 3 h 34 min down
  1. Sun 11 Oct05:31–05:32 utc
    API and MCP server unreachableresolved
    APIMCP server· HTTP 502
    1 min
  2. Sat 3 Oct07:02–07:03 utc
    API and MCP server unreachableresolved
    APIMCP server· HTTP 502
    1 min
  3. Thu 17 Sep09:16–12:46 utc
    All services unreachableresolved
    WebsiteAPIMCP server· no answer within 10 s

    Website came back and dropped out again — 25 short outages in this window.

    3 h 30 min
  4. Wed 16 Sep19:56–19:59 utc
    All services unreachableresolved
    WebsiteAPIMCP server· no answer within 10 s
    3 min
An incident opens on the second failed check in a row, so one dropped packet is not an outage. Failures that start within 5 minutes of each other are one incident.

Build on this status

JSON Every service, its uptime and the 30-day incident list. Refreshed every minute, CORS open. GET https://status.cryptoetf.today/api/status.json
Status badge API status: up ![status](https://status.cryptoetf.today/badge/api.svg) Also /badge/website.svg, /badge/mcp.svg and /badge.svg for all services.
MCP server Streamable HTTP, no key. Five tools for flows, CEFI and prices. https://mcp.cryptoetf.today/api/mcp Install guide