shipapis
StarSubmit an APISubmit API

GitHub Project Issues vs YADG

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

APIGitHub Project IssuesHEALTHY90YADGDEAD0
Uptime · 30d
Uptime · 90d99.02%2.9%
Uptime · 30d98.3%0.0%
P50 · ms4781308
P95 · ms43101359
AuthnoneapiKey
CORSnono
HTTPSyesyes
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

GitHub Project Issues vs YADG: common questions

Which is more reliable, GitHub Project Issues or YADG?

On our scheduled checks, GitHub Project Issues leads on measured uptime — GitHub Project Issues at 99.02% versus YADG at 2.9% 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, GitHub Project Issues or YADG?

GitHub Project Issues has the lower median latency in our checks — GitHub Project Issues responds in 478 ms versus YADG at 1308 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 GitHub Project Issues and YADG need an API key?

GitHub Project Issues needs no key, while YADG requires a free API key. If you want to start calling without signup, reach for GitHub Project Issues first.

Can I call GitHub Project Issues and YADG from the browser?

Neither sends browser-friendly CORS headers reliably, so call GitHub Project Issues and YADG from a server or proxy rather than client-side. The CORS and HTTPS rows above show exactly what we detected for each.

Are GitHub Project Issues and YADG free for commercial use?

GitHub Project Issues has unclear commercial terms, and YADG 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.