<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Peakhour.IO - Incident Response</title><link>https://www.peakhour.io/</link><description></description><lastBuildDate>Sat, 01 Aug 2026 11:50:00 +1000</lastBuildDate><item><title>What a Residential Proxy Decision Log Should Contain</title><link>https://www.peakhour.io/blog/residential-proxy-decision-logging/</link><description>&lt;p&gt;A useful proxy event records the request, signal provenance, policy, action, and outcome. A timestamp and a risk score are not enough to explain an enforcement decision.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">AC</dc:creator><pubDate>Sat, 01 Aug 2026 11:50:00 +1000</pubDate><guid isPermaLink="false">tag:www.peakhour.io,2026-08-01:/blog/residential-proxy-decision-logging/</guid><category>Security</category><category>Residential Proxies</category><category>Security Logging</category><category>SIEM</category><category>Bot Management</category><category>Incident Response</category></item><item><title>Cloudflare outage proves Plan B depends on controlling DNS</title><link>https://www.peakhour.io/blog/cloudflare-outage-dns-plan-b/</link><description>&lt;p&gt;Tuesday’s Cloudflare incident reminded everyone that you can’t execute a Plan B if your DNS knobs are trapped behind the provider that’s failing. Here’s how Peakhour runs a detect-decide-divert playbook without touching your existing third-party DNS vendors.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dan</dc:creator><pubDate>Tue, 18 Nov 2025 21:00:00 +1100</pubDate><guid isPermaLink="false">tag:www.peakhour.io,2025-11-18:/blog/cloudflare-outage-dns-plan-b/</guid><category>Interest</category><category>CDN</category><category>DNS</category><category>Multi CDN</category><category>Incident Response</category></item></channel></rss>