# \#infrastructure

**URL:** https://discourse.julialang.org/tag/infrastructure/212.md

[Latest](https://discourse.julialang.org/latest.md) · [Categories](https://discourse.julialang.org/categories.md) · [Tags](https://discourse.julialang.org/tags.md)

---

## [Julia servers are down again](https://discourse.julialang.org/t/julia-servers-are-down-again/132820)

<div class="topic-metadata">

**Author:** [@juliohm](https://discourse.julialang.org/u/juliohm)\
**Replies:** 1\
**Last updated:** [October 2, 2025, 3:28pm UTC](https://discourse.julialang.org/t/julia-servers-are-down-again/132820 "2025-10-02T15:28:57Z")

</div>

I don’t know what is causing these frequent issues with the servers, but it would be really nice if someone could restart them somehow: Currently unable to bump versions of packages.

---

## [how to compare objects by memory address forcedly.](https://discourse.julialang.org/t/how-to-compare-objects-by-memory-address-forcedly/13339)

<div class="topic-metadata">

**Author:** [@thautwarm](https://discourse.julialang.org/u/thautwarm)\
**Replies:** 5\
**Last updated:** [August 13, 2018, 12:17pm UTC](https://discourse.julialang.org/t/how-to-compare-objects-by-memory-address-forcedly/13339 "2018-08-13T12:17:51Z")

</div>

Just like is in Python, there’re some use cases requiring comparison by memory address, no matter whether the object is mutable or not. === doesn’t satisfy the demand for it compares immutable data in bit level. It’s e…