City, Lviv vs Neotimo DGFiP Mirror

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

Uptime · 30d
Uptime · 90d74.5%100%
Uptime · 30d70.0%100%
P50 · ms965524
P95 · ms23012594
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

City, Lviv vs Neotimo DGFiP Mirror: common questions

Which is more reliable, City, Lviv or Neotimo DGFiP Mirror?

On our scheduled checks, Neotimo DGFiP Mirror leads on measured uptime — City, Lviv at 74.5% versus Neotimo DGFiP Mirror 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, City, Lviv or Neotimo DGFiP Mirror?

Neotimo DGFiP Mirror has the lower median latency in our checks — City, Lviv responds in 965 ms versus Neotimo DGFiP Mirror at 524 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 City, Lviv and Neotimo DGFiP Mirror need an API key?

Neither needs a paid key — City, Lviv is callable with no signup, and Neotimo DGFiP Mirror is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call City, Lviv and Neotimo DGFiP Mirror from the browser?

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

Are City, Lviv and Neotimo DGFiP Mirror free for commercial use?

City, Lviv has unclear commercial terms, and Neotimo DGFiP Mirror 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.