# Galaxy.ansible.com currently down (500 errors)

**URL:** <https://forum.ansible.com/t/galaxy-ansible-com-currently-down-500-errors/45170>\
**Category:** Get Help\
**Tags:** galaxy-ng\
**Created:** [January 25, 2026, 9:35am UTC](https://forum.ansible.com/t/galaxy-ansible-com-currently-down-500-errors/45170 "2026-01-25T09:35:44Z")\
**Posts on this page:** 1\
**Showing post:** 36

<div class="post-metadata">

**Author:** ![utoddl](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/utoddl/32/249_2.png) [@utoddl](https://forum.ansible.com/u/utoddl)\
**Post date:** [January 27, 2026, 4:50pm UTC](https://forum.ansible.com/t/galaxy-ansible-com-currently-down-500-errors/45170/36 "2026-01-27T16:50:22Z")

</div>

This has come up [before](https://forum.ansible.com/t/ansible-galaxy-not-functional/4757/29). I’ve toyed briefly with, and am sorely tempted by, @sivel’s [amanda](https://github.com/sivel/amanda) project, which serves a directory of collection artifacts with the Galaxy v2 API. I don’t really want to stand up a full private galaxy\_ng service — until galaxy itself is not available.

---

_[View the full topic](https://forum.ansible.com/t/galaxy-ansible-com-currently-down-500-errors/45170)._