WorldTimeAPI alternative: a drop-in replacement for worldtimeapi.org

Short answer: worldtimeapi.org is offline, and the quickest replacement keeps its URLs. TimeLogic answers the same /api/timezone and /api/ip paths, with the same JSON fields and .txt output, on https://api.timelogicapi.com. Change the host, add an API key, and your parser does not change.

# before
curl "http://worldtimeapi.org/api/timezone/Europe/London"

# after
curl "https://api.timelogicapi.com/api/timezone/Europe/London?api_key=YOUR_KEY"

What happened to worldtimeapi.org?

WorldTimeAPI was a free, keyless JSON and plain-text time API used everywhere from Python tutorials to Power BI reports and ESP32 clocks. Its reliability fell apart over 2025: in January 2025 its own status page showed 15.48% uptime for the previous month, and by November 2025 users reported 2.79% (Python forum thread). In 2026 it was shut down: since April 2026 its API has answered 410 Gone with {"error":"gone","status":410,"message":"WorldTimeAPI has been sunset. This endpoint is gone."} when it answers at all (see this archived response from September 1, 2026).

When we checked on October 30, 2026, worldtimeapi.org closed connections without answering. If your logs show Connection reset by peer, ERR_EMPTY_RESPONSE, timeouts, or error pages from worldtimeapi.org, the problem is not your code.

How do I migrate from WorldTimeAPI?

1. Create a free API key. The Free plan includes 10,000 requests per month; no card needed.
2. Replace worldtimeapi.org with api.timelogicapi.com and use https://.
3. Send the key. Use a header where you can (Authorization: Bearer … or X-API-Key: …); use the api_key query parameter for tools that cannot set headers.
4. Keep the rest of the path, and your response handling, exactly as it is.

No /v1 prefix: the WorldTimeAPI-compatible routes live at the same paths WorldTimeAPI used.

Code examples

JavaScript (Node 18+ or any runtime with fetch):

const res = await fetch("https://api.timelogicapi.com/api/timezone/Europe/London", {
  headers: { Authorization: `Bearer ${process.env.TIMELOGIC_API_KEY}` },
});
const data = await res.json();
console.log(data.datetime, data.abbreviation); // same fields as worldtimeapi.org

Python:

import os, requests

r = requests.get(
    "https://api.timelogicapi.com/api/ip",
    headers={"X-API-Key": os.environ["TIMELOGIC_API_KEY"]},
    timeout=10,
)
r.raise_for_status()
print(r.json()["timezone"])

Go:

req, _ := http.NewRequest("GET", "https://api.timelogicapi.com/api/timezone/Asia/Tokyo", nil)
req.Header.Set("Authorization", "Bearer "+os.Getenv("TIMELOGIC_API_KEY"))
res, err := http.DefaultClient.Do(req)

Plain text, for shell scripts and small devices:

curl "https://api.timelogicapi.com/api/timezone/Etc/UTC.txt" \
  -H "X-API-Key: $TIMELOGIC_API_KEY"

Power BI / Power Query, where headers are awkward:

= Json.Document(Web.Contents("https://api.timelogicapi.com/api/timezone/Etc/UTC?api_key=YOUR_KEY"))

Every language, line by line (PHP, Java, C#, Ruby, ESP32 and more), with fixes for common errors: Migrate from WorldTimeAPI.

What stays exactly the same?

• Paths: /api/timezone, /api/timezone/{area}, /api/timezone/{area}/{location}[/{region}], /api/ip, /api/ip/{ip}, each with a .txt variant.
• Fields: the same 15 fields with the same names, types and formats, including datetime with six fractional digits and an offset (2025-08-13T11:13:46.612000+01:00), dst_from/dst_until as null outside DST, and ISO week_number.
• Errors: 404 {"error":"unknown location"}, {"error":"malformed ip"} and {"error":"not found"}, or Error: … lines on .txt.
• Behaviour: case-insensitive zone names, the same zone list (WorldTimeAPI's final 596 names plus America/Coyhaique), open CORS, and application/json / text/plain with charset=utf-8.

What is different?

• A key is required on every request. It shares your plan's quota with the rest of the API.
• Microseconds always end in 000, because timestamps come from a millisecond clock.
• .txt lines are alphabetical, the fixed order WorldTimeAPI served from 2019 to July 2024 (later its order changed per request).
• Newer data: current tz and IP datasets, so a few IP addresses may resolve differently than they did years ago.
• Optional extra: add sign=true and the response carries an Ed25519 signature in six X-TimeLogic-* headers. The body is unchanged, JSON or .txt.

The complete contract (every route, field, header and error) is in the WorldTimeAPI-compatible routes documentation, with a machine-readable OpenAPI file and an interactive reference for the WorldTimeAPI-compatible API, where you can try each route with your key.

When should I use the /v1 API instead?

The compatible routes exist so old code keeps working. New code can use the same key with the /v1 World Time API, which adds what WorldTimeAPI never had: coordinate and IP time zone lookup, time zone conversion, DST transitions, business days with holiday calendars, up to 10 zones per bulk request, and signed responses. You can mix both in one project.

Read the launch post: WorldTimeAPI is gone. Your code doesn't have to change.

Still choosing? Compare TimeLogic with other providers in the time API comparison.