Skip to content
CryptingUp logo

Is CryptingUp API down?

Current status, daily uptime history and troubleshooting for the CryptingUp API (Cryptocurrency).

No, CryptingUp is up

CryptingUp answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1250 ms with HTTP 200.

Checking CryptingUp now…

Sending a request from our server.

CryptingUp API uptime history

30 days agoLatest check
Uptime
2 checks so far
Last check
Oct 24, 2026, 12:25 UTC
Response
1250 ms · HTTP 200
Last up
Now

We check CryptingUp's listed URL (https://www.cryptingup.com/apidoc/#introduction) once a day. History started when CryptingUp was first checked, so new entries show fewer than 30 days.

CryptingUp API not working for you?

  1. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  2. If calls fail only in the browser with a CORS error, CryptingUp may not allow cross-origin requests. Call it from your server instead.
  3. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  4. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.

Cryptocurrency APIs up at their last check

  1. 1DefiLlama logo

    DefiLlama API

    Online · 178 ms

    Open and transparent DeFi data, TVL, coin prices, volumes, and yields.

    • No API key needed
    • Fast: 178 ms response
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2BitcoinYield logo

    BitcoinYield API

    Online · 761 ms

    Live yields on BTC, ETH and stablecoins across DeFi and CeFi, with an A-D risk grade per offer.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3BlazePhoenix logo

    BlazePhoenix API

    Online · 746 ms

    On-chain DEX aggregator quotes and route execution data.

    • No API key needed
    • Returns JSON at its URL
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4

    Block Lottos API

    Online · 675 ms

    On-chain lottery, draw history, jackpot and advertising endpoints.

    • No API key needed
    • Returns JSON at its URL
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  5. 5BTCGlobe logo

    BTCGlobe API

    Online · 878 ms

    Bitcoin height, fees, mempool and peer data served live from two self-hosted nodes.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS

Compare all CryptingUp alternatives · APIs down right now

CryptingUp API status FAQ

Is CryptingUp API down right now?

CryptingUp answered our last daily check (Oct 24, 2026, 12:25 UTC) in 1250 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether CryptingUp is responding at this moment.

How do you check whether CryptingUp API is up?

Once a day our checker requests CryptingUp's listed URL (https://www.cryptingup.com/apidoc/#introduction) and records whether it answers within 15 seconds. Answers like 401 (needs a key), 403 (blocks bots) or 429 (rate-limited) count as up, because the server responded. The listed URL is often the documentation page, so an API endpoint can occasionally fail while its docs stay up.

What can I use if CryptingUp API is down?

Free Cryptocurrency APIs that were up at their last check include DefiLlama, BitcoinYield, BlazePhoenix. See the full list of CryptingUp alternatives for a comparison.

Why does CryptingUp API work for others but not for me?

A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header. If calls fail only in the browser with a CORS error, CryptingUp may not allow cross-origin requests. Call it from your server instead. If it works from one network but not another, check firewalls, VPNs and regional blocks.