# Is https://check.ci.ocaml.org being deprecated? **URL:** \ **Category:** Ecosystem\ **Tags:** ci, opam\ **Created:** [July 12, 2026, 8:03am UTC](https://discuss.ocaml.org/t/is-https-check-ci-ocaml-org-being-deprecated/18346 "2026-07-12T08:03:02Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Kakadu](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/kakadu/32/1204_2.png) [@Kakadu](https://discuss.ocaml.org/u/Kakadu)\ **Post date:** [July 12, 2026, 8:03am UTC](https://discuss.ocaml.org/t/is-https-check-ci-ocaml-org-being-deprecated/18346/1 "2026-07-12T08:03:02Z")
It looks like that last run was in 2025… ---
**Author:** ![sim642](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/sim642/32/3597_2.png) [@sim642](https://discuss.ocaml.org/u/sim642)\ **Post date:** [July 12, 2026, 11:12am UTC](https://discuss.ocaml.org/t/is-https-check-ci-ocaml-org-being-deprecated/18346/2 "2026-07-12T11:12:59Z")
I was wondering the same a few weeks ago on Discord, but got no replies. The whole website is very slow to load as well: the results table only loads packages starting with a-c. ---
**Author:** ![Kakadu](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/kakadu/32/1204_2.png) [@Kakadu](https://discuss.ocaml.org/u/Kakadu)\ **Post date:** [July 13, 2026, 4:46pm UTC](https://discuss.ocaml.org/t/is-https-check-ci-ocaml-org-being-deprecated/18346/3 "2026-07-13T16:46:43Z")
Do you know any other way to check installability of packages, mainatained by me? ---
**Author:** ![mtelvers](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/mtelvers/32/5834_2.png) [@mtelvers](https://discuss.ocaml.org/u/mtelvers)\ **Post date:** [July 14, 2026, 12:22pm UTC](https://discuss.ocaml.org/t/is-https-check-ci-ocaml-org-being-deprecated/18346/4 "2026-07-14T12:22:02Z")
The jobs have been failing to create the appropriate switches so the runs have been failing. I’ve resolved this now and a new run is in progress with a reduced set of compilers matching opam-repo-ci. Check back in a few days but which time the run should have finished. ---
**Author:** ![Kakadu](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/kakadu/32/1204_2.png) [@Kakadu](https://discuss.ocaml.org/u/Kakadu)\ **Post date:** [July 17, 2026, 3:22pm UTC](https://discuss.ocaml.org/t/is-https-check-ci-ocaml-org-being-deprecated/18346/5 "2026-07-17T15:22:02Z")
No visible update. I will wait more… ---
**Author:** ![Kakadu](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/kakadu/32/1204_2.png) [@Kakadu](https://discuss.ocaml.org/u/Kakadu)\ **Post date:** [July 28, 2026, 1:21pm UTC](https://discuss.ocaml.org/t/is-https-check-ci-ocaml-org-being-deprecated/18346/6 "2026-07-28T13:21:38Z")
Currently website is missing compiler 5.1 and 5.3. Is it intentional? ---
**Author:** ![mtelvers](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/mtelvers/32/5834_2.png) [@mtelvers](https://discuss.ocaml.org/u/mtelvers)\ **Post date:** [July 28, 2026, 1:36pm UTC](https://discuss.ocaml.org/t/is-https-check-ci-ocaml-org-being-deprecated/18346/7 "2026-07-28T13:36:42Z")
Yes. The tested versions match the versions tested by opam-repo-ci. opam-repo-ci tracks “significant” versions. See [ocaml-version/ocaml\_version.ml at de164f480705dd214cd406bbd762d3da2d3612b5 · ocurrent/ocaml-version · GitHub](https://github.com/ocurrent/ocaml-version/blob/de164f480705dd214cd406bbd762d3da2d3612b5/ocaml_version.ml#L257-L261) ---
**Author:** ![avsm](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ocaml.org/avsm/32/6_2.png) [@avsm](https://discuss.ocaml.org/u/avsm)\ **Post date:** [July 29, 2026, 11:44am UTC](https://discuss.ocaml.org/t/is-https-check-ci-ocaml-org-being-deprecated/18346/8 "2026-07-29T11:44:25Z")
> [@Kakadu](#): > > Currently website is missing compiler 5.1 and 5.3. Is it intentional? It would be helpful to know if you actually need 5.1 and 5.3, or are just curious. We have to limit the amount of CI to a reasonable subset versions, unless there’s a good reason for sticking to a particular version. The check service is under [quite a lot of scraper load](https://www.tunbury.org/2026/07/27/week-30-2025/#:~:text=starting%20point.%20check.mint.caelum.ci.dev-,check.ci.ocaml.org,-outage), contributing to the outages as well. It’s holding up now thanks to Mark’s efforts, but if it gets worse then we’ll have to find some sort of authentication solution to dodge the slopobot army.