Skip to content
Cutt.ly logo

Is Cutt.ly API down?

Current status, daily uptime history and troubleshooting for the Cutt.ly API (URL Shorteners).

No, Cutt.ly is up

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

Checking Cutt.ly now…

Sending a request from our server.

Cutt.ly API uptime history

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

We check Cutt.ly's listed URL (https://cutt.ly/api-documentation/cuttly-links-api) once a day. History started when Cutt.ly was first checked, so new entries show fewer than 30 days.

Cutt.ly API not working for you?

  1. Cutt.ly needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string.
  2. A 429 response means you're being rate-limited. Slow down, cache responses, and respect any Retry-After header.
  3. If calls fail only in the browser with a CORS error, Cutt.ly may not allow cross-origin requests. Call it from your server instead.
  4. If it works from one network but not another, check firewalls, VPNs and regional blocks.
  5. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.

URL Shorteners APIs up at their last check

  1. 1GoTiny logo

    GoTiny API

    Online · 1169 ms

    A lightweight URL shortener, focused on ease-of-use for the developer and end-user.

    • No API key needed
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 21pt logo

    1pt API

    Online · 1454 ms

    A simple URL shortener. A free url shorteners API by 1pt-co.

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

    Git.io API

    Online · 956 ms

    Do you have a GitHub URL you’d like to shorten?

    • No API key needed
    • HTTPS
    No authHTTPSCORS ?
  4. 4RedirHub logo

    RedirHub API

    Online · 1169 ms

    URL redirect management with custom domains, HTTPS, analytics, and REST API.

    • Callable from the browser (CORS)
    • HTTPS
    apiKeyHTTPSCORS
  5. 5UrlBae logo

    UrlBae API

    Online · 682 ms

    Simple and efficient short link creation.

    • Callable from the browser (CORS)
    • HTTPS
    apiKeyHTTPSCORS

Compare all Cutt.ly alternatives · APIs down right now

Cutt.ly API status FAQ

Is Cutt.ly API down right now?

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

How do you check whether Cutt.ly API is up?

Once a day our checker requests Cutt.ly's listed URL (https://cutt.ly/api-documentation/cuttly-links-api) 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 Cutt.ly API is down?

Free URL Shorteners APIs that were up at their last check include GoTiny, 1pt, Git.io. See the full list of Cutt.ly alternatives for a comparison.

Why does Cutt.ly API work for others but not for me?

Cutt.ly needs an API key. A 401 or 403 usually means a missing, expired or mis-sent credential: check whether it belongs in a header or the query string. 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, Cutt.ly may not allow cross-origin requests. Call it from your server instead.