Fedora Messaging API vs mail.tm

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

Uptime · 30d
Uptime · 90d97.1%84.3%
Uptime · 30d98.3%75.0%
P50 · ms1510709
P95 · ms49752351
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — temporary mailboxes
Rate limitUnpublishedRate limited (429 on exceed); exact policy per docs.mail.tm
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fedora Messaging API vs mail.tm: common questions

Which is more reliable, Fedora Messaging API or mail.tm?

On our scheduled checks, Fedora Messaging API leads on measured uptime — Fedora Messaging API at 97.1% versus mail.tm at 84.3% 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, Fedora Messaging API or mail.tm?

mail.tm has the lower median latency in our checks — Fedora Messaging API responds in 1510 ms versus mail.tm at 709 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 Fedora Messaging API and mail.tm need an API key?

Neither needs a paid key — Fedora Messaging API is callable with no signup, and mail.tm is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Fedora Messaging API and mail.tm from the browser?

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

Are Fedora Messaging API and mail.tm free for commercial use?

Fedora Messaging API has unclear commercial terms, and mail.tm 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.