OkSurf vs RSS2JSON

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

Uptime · 30d
Uptime · 90d100%96.1%
Uptime · 30d100%96.7%
P50 · ms624178
P95 · ms18701882
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

OkSurf vs RSS2JSON: common questions

Which is more reliable, OkSurf or RSS2JSON?

On our scheduled checks, OkSurf leads on measured uptime — OkSurf at 100% versus RSS2JSON at 96.1% 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, OkSurf or RSS2JSON?

RSS2JSON has the lower median latency in our checks — OkSurf responds in 624 ms versus RSS2JSON at 178 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 OkSurf and RSS2JSON need an API key?

Neither needs a paid key — OkSurf is callable with no signup, and RSS2JSON is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call OkSurf and RSS2JSON from the browser?

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

Are OkSurf and RSS2JSON free for commercial use?

OkSurf has unclear commercial terms, and RSS2JSON 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.