diff --git a/Distcc_Cross-Compiling.md b/Distcc_Cross-Compiling.md
index 27dd5e7..10e15c9 100644
--- a/Distcc_Cross-Compiling.md
+++ b/Distcc_Cross-Compiling.md
@@ -13,10 +13,10 @@ In lieu of building the toolchain as detailed below, if you are running a 64-bit
 
 It is *highly recommended* to use these tarballs as they have been thoroughly tested, and are maintained to be version- and source-matched to the current toolchain components for our ARM architectures.  If you build the toolchain yourself, you must assemble patched source tarballs to build versions that match what is in use here.
 
-* [ARMv5te soft](/builder/xtools/x-tools.tar.xz) (df3fe198c989fe36e6209e65e4d6ae57)
-* [ARMv6l hard](/builder/xtools/x-tools6h.tar.xz) (89905d219fb8dbdce02ed57694e9419c)
-* [ARMv7l hard](/builder/xtools/x-tools7h.tar.xz) (577b4ce8f5dbd2c0b3b760701aaa05cd)
-* [ARMv8](/builder/xtools/x-tools8.tar.xz) (bcd483b67915b22397dd77f926e948d3)
+* [ARMv5te soft](/builder/xtools/x-tools.tar.xz) (c5e18a5a4f7162d6609ce8e550052feb)
+* [ARMv6l hard](/builder/xtools/x-tools6h.tar.xz) (1835bc76e909c77258a36b414ed3ff86)
+* [ARMv7l hard](/builder/xtools/x-tools7h.tar.xz) (8d61c218fd68b454883d8cd01216eb82)
+* [ARMv8](/builder/xtools/x-tools8.tar.xz) (75e7f6d60626727ac01409638516c569)
 
 If you want to save yourself time and configuration, see [WarheadsSE's distccd-alarm](https://github.com/WarheadsSE/PKGs/tree/master/distccd-alarm) package. This will generate 3 packages (one for each architecture), and contains configuration and systemd service units for each. It is for x86_64 only, like these toolchain tarballs.
 
@@ -91,4 +91,4 @@ PATH=/home/your_user/x-tools[6h|7h|8]/arm-unknown-linux-gnueabi[hf]/bin:$PATH
 Back on ARM "master" device, make sure that distcc has been enabled in makepkg.conf per the [[Distributed Compiling]] guide, and specify the cross-compiler computer's IP address in the DISTCC_HOSTS variable. Now all builds using makepkg will make use of the distcc and cross compiler setup.
 
 ## Crap, it's not working
-If you've followed this guide to the letter and you know you've done everything right, the likely problem is that the user distccd is running as does not have permission to access the location of the crosstool-ng binaries.  Either change distccd's user or relocate the x-tools directory to somewhere it can read it, then be sure the PATH set above reflects the new location.
\ No newline at end of file
+If you've followed this guide to the letter and you know you've done everything right, the likely problem is that the user distccd is running as does not have permission to access the location of the crosstool-ng binaries.  Either change distccd's user or relocate the x-tools directory to somewhere it can read it, then be sure the PATH set above reflects the new location.