{"version":"2.1.311","anchor":"datadog-telemetry-pauses-after-an-egress-refusal","canonical_anchor":"datadog-telemetry-pauses-after-an-egress-refusal","heading":"Usage data sending to Datadog pauses after a network refusal","tier":"notice","area":"Telemetry","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/datadog-telemetry-pauses-after-an-egress-refusal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Usage data sending to Datadog pauses after a network refusal\n\nClaude Code now stops sending usage data to Datadog once network rules refuse that traffic\n\n**What**\n\nClaude Code sends some usage data to Datadog, a monitoring service. It now stops sending this data once the network has refused it. This happens, for example, when rules about which outside addresses your machine may reach block the connection. Claude Code also keeps track of whether it has already reported the refusal.\n\n**Why**\n\nIf your network blocks this traffic, Claude Code pauses sending it rather than repeating attempts that will fail.\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}