District of Columbia Open Data vs Neotimo DGFiP Mirror

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (DC Open Data terms)Unverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

District of Columbia Open Data vs Neotimo DGFiP Mirror: common questions

Which is more reliable, District of Columbia Open Data or Neotimo DGFiP Mirror?

On our scheduled checks, Neotimo DGFiP Mirror leads on measured uptime — District of Columbia Open Data at —% versus Neotimo DGFiP Mirror at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do District of Columbia Open Data and Neotimo DGFiP Mirror need an API key?

Neither needs a paid key — District of Columbia Open Data 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 District of Columbia Open Data and Neotimo DGFiP Mirror from the browser?

Yes — both District of Columbia Open Data and Neotimo DGFiP Mirror send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are District of Columbia Open Data and Neotimo DGFiP Mirror free for commercial use?

District of Columbia Open Data 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.