The Mistake that Caused 1.1.1.3 to Block LGBTQIA+ Sites Today

This post details an incident where a mistake in the categorization data for the 1.1.1.1 for Families service led to the inadvertent blocking of LGBTQIA+ sites. The issue was caused by selecting the wrong 'Adult Content' feed from a licensed provider, which included a broader set of topics than intended. The fix involved pulling the incorrect data feed, regenerating the data structure with the correct definition, and pushing it out to all data centers. Additionally, individual sites were added to an allow list immediately as they were reported. Future protections include setting up checks for known sites that should fall outside the intended categories before defaults are updated.