Skip to contentAPILayer: production APIs with free plansExplore APILayer
Rent Limits logo

Is Rent Limits API down?

Current status, daily uptime history and troubleshooting for the Rent Limits API (Government).

No, Rent Limits is up

Rent Limits answered our last daily check (Nov 15, 2026, 13:58 UTC) in 1280 ms with HTTP 200.

Checking Rent Limits now…

Sending a request from our server.

Rent Limits API uptime history

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

We check Rent Limits's listed URL (https://glazeddata.com/rent-limits/api/) once a day. History started when Rent Limits was first checked, so new entries show fewer than 30 days.

Rent Limits API not working for you?

  1. Rent Limits 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 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.

Government APIs up at their last check

  1. 1EU VAT Rates by Commodity Code logo

    EU VAT rates mapped to CN and CPA commodity codes, all 27 member states.

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

    MORVS API

    Online · 1121 ms

    Source-linked US regulatory and public records: SEC filings, enforcement actions, recalls.

    • No API key needed
    • 100% uptime (30 days)
    • Callable from the browser (CORS)
    • HTTPS
    No authHTTPSCORS
  3. 3nu:legal Deutsches Recht logo

    German federal and state statutes and 640,000 court decisions as JSON, with citation links.

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

    Tollmint API

    Online · 1163 ms

    Advertising, subscription, AI-disclosure and accessibility rules across the US, EU and UK.

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

    US Per Diem API

    Online · 660 ms

    GSA lodging and M&IE per diem rates for US cities by ZIP, state and fiscal year.

    • No API key needed
    • 100% uptime (30 days)
    • Returns JSON at its URL
    • Callable from the browser (CORS)
    No authHTTPSCORS

Compare all Rent Limits alternatives · APIs down right now

Rent Limits API status FAQ

Is Rent Limits API down right now?

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

How do you check whether Rent Limits API is up?

Once a day our checker requests Rent Limits's listed URL (https://glazeddata.com/rent-limits/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 Rent Limits API?

Rent Limits 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 Rent Limits API is down?

Free Government APIs that were up at their last check include EU VAT Rates by Commodity Code, MORVS, nu:legal Deutsches Recht. See the full list of Rent Limits alternatives for a comparison.

Why does Rent Limits API work for others but not for me?

Rent Limits 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 it works from one network but not another, check firewalls, VPNs and regional blocks.