# Relay Post-Intall Webpage Error: Check IPv6 Availability

**URL:** https://forum.torproject.org/t/relay-post-intall-webpage-error-check-ipv6-availability/20009
**Category:** Websites Feedback
**Created:** [July 22, 2025, 9:08am UTC](https://forum.torproject.org/t/relay-post-intall-webpage-error-check-ipv6-availability/20009 "2025-07-22T09:08:54Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![streamstrad](https://forum.torproject.org/letter_avatar_proxy/v4/letter/s/58956e/32.png) [@streamstrad](https://forum.torproject.org/u/streamstrad)
#### Post date: [July 22, 2025, 9:08am UTC](https://forum.torproject.org/t/relay-post-intall-webpage-error-check-ipv6-availability/20009/1 "2025-07-22T09:08:54Z")

</div>

hello,

while attempting to set up IPv6 compatibility via Section 8 of [Tor Project | Relay Post-install and good practices](https://community.torproject.org/relay/setup/post-install/), I noticed an error:

Section 8 states the following: " The following command line will ping the IPv6 addresses of Tor directory authorities from your server:  
`ping6 -c2 2001:858:2:2:aabb:0:563b:1526 && ping6 -c2 2620:13:4000:6000::1000:118 && ping6 -c2 2001:67c:289c::9 && ping6 -c2 2001:678:558:1000::244 && ping6 -c2 2001:638:a000:4140::ffff:189 && echo OK.`

when attempting this command on the machine that is running my relay, the command fails during the first `ping6 -c2 2001:858:2:2:aabb:0:563b:1526`.

I removed the that portion of the command and `ping6 -c2 2620:13:4000:6000::1000:118 && ping6 -c2 2001:67c:289c::9 && ping6 -c2 2001:678:558:1000::244 && ping6 -c2 2001:638:a000:4140::ffff:189 && echo OK.` outputs “OK.” with no issues.

just wanted to let you know that the Tor directory authority with IPv6 2001:858:2:2:aabb:0:563b:1526 seems to be down.

NOTE: I noticed January 2023 [similar feedback](https://v236xhqtyullodhf26szyjepvkbv6iitrhjgrqj4avaoukebkk6n6syd.onion/t/tor-relays-ipv6-tor-authority-is-down/6186), but that feedback seems to be for a different Tor directory authority (2607:8500:154::3), which now pings fine.

I hope that this helps. cheers