{
  "schema_version": "1.1",
  "id": "s4:https://vercel.com/changelog/vercel-sandbox-routing-is-now-18x-faster-globally",
  "slug": "vercel-sandbox-routing-is-now-18x-faster-globally-1xr4uw7",
  "url": "https://feed7.dev/p/vercel-sandbox-routing-is-now-18x-faster-globally-1xr4uw7",
  "title": "Vercel Sandbox routing is now 18x faster globally",
  "why_included": "Vercel cut median Sandbox domain lookup latency from 62 ms to 3.4 ms by resolving domains from regional replicas. Agent sandboxes get the change automatically with no pricing change.",
  "summary": "Vercel now resolves Sandbox public domains from the nearest regional replica rather than one centralized store. **Median lookup latency fell from 62 ms to 3.4 ms**, an **18× reduction**.",
  "practical_implication": "Builders running browser previews, callbacks, or agent-generated services on Sandbox domains get lower routing overhead automatically. No SDK migration or configuration change is described.",
  "agent_context": "Vercel now resolves Sandbox public domains from the nearest regional replica rather than one centralized store. **Median lookup latency fell from 62 ms to 3.4 ms**, an **18× reduction**.\n\nBuilders running browser previews, callbacks, or agent-generated services on Sandbox domains get lower routing overhead automatically. No SDK migration or configuration change is described.\n\nThe largest reported gains are regional p99 figures—up to **112× in Sydney** and **146× in Cape Town**—so they should not be read as typical global latency. Process startup and application latency are outside this measurement.",
  "source": {
    "name": "Vercel",
    "url": "https://vercel.com/changelog/vercel-sandbox-routing-is-now-18x-faster-globally",
    "published_at": "2026-09-08T20:00:00.000Z"
  },
  "source_class": "blog_post",
  "content_type": "Engineering Post",
  "layer": "infra",
  "domains": [
    "coding"
  ],
  "topics": [
    "sandboxing"
  ],
  "verification": {
    "status": "official_source",
    "label": "Official Source",
    "method": "source_feed",
    "verified_at": null
  },
  "uncertainty": [
    "The largest reported gains are regional p99 figures—up to **112× in Sydney** and **146× in Cape Town**—so they should not be read as typical global latency. Process startup and application latency are outside this measurement."
  ],
  "connected_context": {
    "meaning": "This removes a specific infrastructure tax for public Sandbox endpoints by distributing domain resolution, benefiting previews, callbacks, and agent-hosted services without a described migration. It complements sandbox capability and isolation improvements, but the measurement is only routing lookup latency; it neither demonstrates faster process startup nor establishes lower end-to-end application latency.",
    "corpus_size": 713,
    "generated_at": "2026-09-09T10:12:01.795Z",
    "connections": [
      {
        "title": "Vercel AI Gateway and Vercel Sandbox now available on Hermes Agent",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/changelog/vercel-ai-gateway-and-vercel-sandbox-now-available-on-hermes-agent",
        "feed7_url": "https://feed7.dev/p/vercel-ai-gateway-and-vercel-sandbox-now-available-on-hermes-agent-04gyfsv",
        "reason": "Hermes can use Sandbox as an opt-in execution backend; the routing change reduces lookup overhead for public endpoints created by that deployment choice without changing its runtime, linking, or OIDC prerequisites."
      },
      {
        "title": "How Sandstone grew 40x in 147 days on Vercel",
        "source_name": "Vercel",
        "source_url": "https://vercel.com/blog/how-sandstone-grew-40x-in-147-days-on-vercel",
        "feed7_url": "https://feed7.dev/p/how-sandstone-grew-40x-in-147-days-on-vercel-1bhjz28",
        "reason": "Sandstone uses preview deployments as part of an agent workflow, making lower public-domain routing overhead relevant to one concrete deployment pattern, while still leaving its missing end-to-end latency and reliability evidence unresolved."
      },
      {
        "title": "TencentCloud/CubeSandbox",
        "source_name": "GitHub",
        "source_url": "https://github.com/TencentCloud/CubeSandbox",
        "feed7_url": "https://feed7.dev/p/cubesandbox-1d2cg1q",
        "reason": "CubeSandbox’s cold-start claim measures sandbox creation, while Vercel measures domain lookup; the contrast prevents treating either number as a complete measure of time to a usable agent service."
      },
      {
        "title": "Scaling Managed Agents: Decoupling the brain from the hands",
        "source_name": "Anthropic",
        "source_url": "https://www.anthropic.com/engineering/managed-agents",
        "feed7_url": "https://feed7.dev/p/managed-agents-00zpz67",
        "reason": "Managed Agents reports improvement in time-to-first-token through harness–sandbox decoupling, whereas this change optimizes endpoint routing; they address distinct latency stages in hosted agent infrastructure."
      }
    ]
  },
  "lifecycle": "Current",
  "published_at": "2026-09-08T20:00:00.000Z",
  "modified_at": "2026-09-08T20:00:00.000Z",
  "supersedes": [],
  "expires_at": null,
  "formats": {
    "html": "https://feed7.dev/p/vercel-sandbox-routing-is-now-18x-faster-globally-1xr4uw7",
    "json": "https://feed7.dev/p/vercel-sandbox-routing-is-now-18x-faster-globally-1xr4uw7.json",
    "markdown": "https://feed7.dev/p/vercel-sandbox-routing-is-now-18x-faster-globally-1xr4uw7.md"
  }
}