Skip to contentAPILayer: production APIs with free plansExplore APILayer
High Valyrian Translators logo

Is High Valyrian Translators API down?

Current status, daily uptime history and troubleshooting for the High Valyrian Translators API (Dictionaries).

No, High Valyrian Translators is up

High Valyrian Translators answered our last daily check (Nov 15, 2026, 13:58 UTC) in 577 ms with HTTP 200.

Checking High Valyrian Translators now…

Sending a request from our server.

High Valyrian Translators API uptime history

30 days agoLatest check
Uptime
100% of 8 checks
Last check
Nov 15, 2026, 13:58 UTC
Response
577 ms · HTTP 200
Last up
Now

We check High Valyrian Translators's listed URL (https://github.com/HVTranslators/high-valyrian-api) once a day. History started when High Valyrian Translators was first checked, so new entries show fewer than 30 days.

High Valyrian Translators 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 it works from one network but not another, check firewalls, VPNs and regional blocks.
  3. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.

Dictionaries APIs up at their last check

  1. 1Random Lexicon logo

    Random Lexicon API

    Online · 702 ms

    Random words and definitions using optional filters.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  2. 2Wiktionary logo

    Wiktionary API

    Online · 1077 ms

    Collaborative dictionary data. A free dictionaries API by Wiktionary.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3WordSoHard logo

    WordSoHard API

    Online · 760 ms

    Word definitions with Scrabble validity and tile score in one call, built for word games.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  4. 4Free Dictionary logo

    Free Dictionary API

    Online · 551 ms

    Definitions, phonetics, pronunciations, parts of speech, examples, synonyms.

    • No API key needed
    • 100% uptime (30 days)
    • HTTPS
    No authHTTPSCORS ?
  5. 5Chinese Text Project logo

    Chinese Text Project API

    Online · 570 ms

    Online open-access digital library for pre-modern Chinese texts.

    • No API key needed
    • 100% uptime (30 days)
    • HTTPS
    No authHTTPSCORS ?

Compare all High Valyrian Translators alternatives · APIs down right now

High Valyrian Translators API status FAQ

Is High Valyrian Translators API down right now?

High Valyrian Translators answered our last daily check (Nov 15, 2026, 13:58 UTC) in 577 ms with HTTP 200. This page also runs a live check from our server when you open it, so you can see whether High Valyrian Translators is responding at this moment.

How do you check whether High Valyrian Translators API is up?

Once a day our checker requests High Valyrian Translators's listed URL (https://github.com/HVTranslators/high-valyrian-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.

How reliable is High Valyrian Translators API?

High Valyrian Translators answered 100% of our last 8 daily checks. Above 99% is excellent for a free API; below 95% means you should cache responses and keep a fallback ready.

What can I use if High Valyrian Translators API is down?

Free Dictionaries APIs that were up at their last check include Random Lexicon, Wiktionary, WordSoHard. See the full list of High Valyrian Translators alternatives for a comparison.

Why does High Valyrian Translators 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 it works from one network but not another, check firewalls, VPNs and regional blocks. Check the provider's documentation, status page or social accounts for planned maintenance or a changed endpoint.