Deploy docs

concepts/analysis_gotchas.html

@@ -220,6 +220,7 @@ <h2 id="notable-historic-events"><a class="header" href="#notable-historic-event
 <ul>
 <li><strong>Apr 18, 2024</strong> - Google began rolling out a new SERP experience on Firefox Android, which impacted standard search metrics. See <a href="https://docs.google.com/spreadsheets/d/16Cyx_KBieRdQkSBKolivqpBaK2H-VceN9LEZcL0snHg/edit#gid=0">the spreadsheet</a> for more details.</li>
 <li><strong>Jan 15 - May 1, 2024</strong> - Legacy Telemetry pings containing os information from Arch Linux clients without the <code>lsb-release</code> package were <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1875874">dropped</a>.</li>
+<li><strong>Dec 8, 2023</strong> - (ongoing) Firefox iOS Clients coming through the French ISP Netskope report an increased number of 4xx HTTP errors on submission (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1870670">bug 1870670</a>).</li>
 <li><strong>Dec 7, 2023</strong> - Contextual Services data for Firefox Desktop versions 116 and up <a href="http://mozilla-hub.atlassian.net/browse/DSRE-1489">now supplied by Glean</a>.</li>
 <li><strong>Nov 20, 2023</strong> - Changeover day for Onboarding data sent via Messaging System from PingCentre to Glean. Views and datasets downstream of <code>messaging_system.onboarding</code> <a href="https://github.com/mozilla/bigquery-etl/pull/4457">began being fueled by Glean-sent data instead of PingCentre-sent data</a>.</li>
 <li><strong>Jul 16, 2023 - Jul 24, 2023</strong> - During the migration from release to ESR of Firefox users on obsolete versions of MacOS and Windows, Firefox sent deletion request pings for clients in the migration, which also reset the <code>client_id</code>. <a href="https://docs.google.com/document/d/1vdn9OFSoKPD5wt14dmTwyh0kGs-96fWx26ESui95jo0/edit">See the summary of the incident here.</a>. Approximately 2 million clients were affected by this bug; as a result of this, around 1.3 million clients were double counted due to both the old <code>client_id</code> and reset <code>client_id</code> being active on the same day.</li>

print.html

@@ -5944,6 +5944,7 @@ <h2 id="notable-historic-events"><a class="header" href="#notable-historic-event
 <ul>
 <li><strong>Apr 18, 2024</strong> - Google began rolling out a new SERP experience on Firefox Android, which impacted standard search metrics. See <a href="https://docs.google.com/spreadsheets/d/16Cyx_KBieRdQkSBKolivqpBaK2H-VceN9LEZcL0snHg/edit#gid=0">the spreadsheet</a> for more details.</li>
 <li><strong>Jan 15 - May 1, 2024</strong> - Legacy Telemetry pings containing os information from Arch Linux clients without the <code>lsb-release</code> package were <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1875874">dropped</a>.</li>
+<li><strong>Dec 8, 2023</strong> - (ongoing) Firefox iOS Clients coming through the French ISP Netskope report an increased number of 4xx HTTP errors on submission (<a href="https://bugzilla.mozilla.org/show_bug.cgi?id=1870670">bug 1870670</a>).</li>
 <li><strong>Dec 7, 2023</strong> - Contextual Services data for Firefox Desktop versions 116 and up <a href="http://mozilla-hub.atlassian.net/browse/DSRE-1489">now supplied by Glean</a>.</li>
 <li><strong>Nov 20, 2023</strong> - Changeover day for Onboarding data sent via Messaging System from PingCentre to Glean. Views and datasets downstream of <code>messaging_system.onboarding</code> <a href="https://github.com/mozilla/bigquery-etl/pull/4457">began being fueled by Glean-sent data instead of PingCentre-sent data</a>.</li>
 <li><strong>Jul 16, 2023 - Jul 24, 2023</strong> - During the migration from release to ESR of Firefox users on obsolete versions of MacOS and Windows, Firefox sent deletion request pings for clients in the migration, which also reset the <code>client_id</code>. <a href="https://docs.google.com/document/d/1vdn9OFSoKPD5wt14dmTwyh0kGs-96fWx26ESui95jo0/edit">See the summary of the incident here.</a>. Approximately 2 million clients were affected by this bug; as a result of this, around 1.3 million clients were double counted due to both the old <code>client_id</code> and reset <code>client_id</code> being active on the same day.</li>