LectServe vs Telegraph

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d92.2%100%
Uptime · 30d76.7%100%
P50 · ms334444
P95 · ms16333497
AuthnoneapiKey
CORSnoyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LectServe vs Telegraph: common questions

Which is more reliable, LectServe or Telegraph?

On our scheduled checks, Telegraph leads on measured uptime — LectServe at 92.2% versus Telegraph at 100% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, LectServe or Telegraph?

LectServe has the lower median latency in our checks — LectServe responds in 334 ms versus Telegraph at 444 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do LectServe and Telegraph need an API key?

LectServe needs no key, while Telegraph requires a free API key. If you want to start calling without signup, reach for LectServe first.

Can I call LectServe and Telegraph from the browser?

Only Telegraph is browser-friendly — it returns CORS headers over HTTPS. LectServe needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are LectServe and Telegraph free for commercial use?

LectServe has unclear commercial terms, and Telegraph has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.