<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>分流 on Panshi | Infrastructure · Quant Trading · AI Workflows</title>
    <link>https://blog.panshi.io/en/tags/%E5%88%86%E6%B5%81/</link>
    <description>Recent content in 分流 on Panshi | Infrastructure · Quant Trading · AI Workflows</description>
    <image>
      <title>Panshi | Infrastructure · Quant Trading · AI Workflows</title>
      <url>https://blog.panshi.io/og-default.png</url>
      <link>https://blog.panshi.io/og-default.png</link>
    </image>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://blog.panshi.io/en/tags/%E5%88%86%E6%B5%81/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Advanced Surge Routing Rules: Route AI Traffic through Residential IPs, Other Traffic through VPS Nodes</title>
      <link>https://blog.panshi.io/en/posts/surge-split-rules-ai-traffic/</link>
      <pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://blog.panshi.io/en/posts/surge-split-rules-ai-traffic/</guid>
      <description>AI services like Claude and ChatGPT are sensitive to IP quality, and datacenter IPs easily trigger restrictions. This article explains how to configure fine-grained routing rules in Surge to route AI requests exclusively through residential IP proxies while keeping regular traffic on VPS nodes.</description>
    </item>
  </channel>
</rss>
