{"version":"2.1.293","anchor":"network-egress-list-gains-a-performance-timing-service","canonical_anchor":"network-egress-list-gains-a-performance-timing-service","heading":"Outbound network services list now includes performance timing","tier":"internal","area":"Telemetry","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/network-egress-list-gains-a-performance-timing-service","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### Outbound network services list now includes performance timing\n\nThe list of services Claude Code connects to over the network now includes a 'Performance timing' entry beside 'Analytics events'\n\n**Unclear.** It is not clear whether Claude Code actually sends performance timing data in this version or only lists it.\n\n**What**\n\nClaude Code keeps a labelled list of the outside services it may send network traffic to. That list now includes an entry called 'Performance timing', next to the existing 'Analytics events' entry.\n\n**Why**\n\nPerformance timing data is now declared as its own kind of outbound traffic. If you review or restrict the network connections Claude Code makes, this entry is one to look out for.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: both\n- Heads-up: no"}