diff --git a/src/_blog/libp2p-hole-punching.md b/src/_blog/libp2p-hole-punching.md
index 758999d4..af559abc 100644
--- a/src/_blog/libp2p-hole-punching.md
+++ b/src/_blog/libp2p-hole-punching.md
@@ -163,7 +163,7 @@ Quite a process, huh?!
 
 # Closing
 
-Hole punching in libp2p is fully specified in the [libp2p specification](https://github.com/libp2p/specs/). It is implemented in [go-libp2p](https://github.com/libp2p/go-libp2p) and [rust-libp2p](https://github.com/libp2p/rust-libp2p/), though in the latter it is not yet released (see [tracking issue](https://github.com/libp2p/rust-libp2p/issues/2052)).
+Hole punching in libp2p is fully specified in the [libp2p specification](https://github.com/libp2p/specs/). It is implemented in [go-libp2p](https://github.com/libp2p/go-libp2p) and [rust-libp2p](https://github.com/libp2p/rust-libp2p/). If you want to try it out yourself, you can follow the [rust-libp2p tutorial](https://docs.rs/libp2p/latest/libp2p/tutorials/hole_punching/index.html).
 
 Compatible hole punching client shipped in [go-ipfs 0.11](https://github.com/ipfs/go-ipfs/releases/tag/v0.11.0). For now, it is hidden behind the [`Swarm.EnableHolePunching`](https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#swarmenableholepunching) configuration flag, but we will enable it by default later this year to improve the connectivity of peers behind firewalls. To follow the progress subscribe to [go-ipfs/#8748](https://github.com/ipfs/go-ipfs/pull/8748).