[Logs] Add AS202623 to Logpush egress ASN lists#28514
Merged
rianvdm merged 1 commit intoproductionfrom Feb 23, 2026
Merged
Conversation
Logpush load-balances delivery across PDX (AS132892) and AMS (AS202623), but the docs only listed AS13335 and AS132892. Customers filtering by ASN were inadvertently blocking AMS traffic and losing logs. - egress-ip.mdx: add AS202623 to ASN text and WAF rule example - splunk.mdx: update WAF rule from single ASN (132892) to all three ASNs
rianvdm
requested review from
a team,
angelampcosta and
soheiokamoto
as code owners
Contributor
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
Contributor
pedrosousa
approved these changes
Feb 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add missing Cloudflare ASN (202623) to Logpush egress IP documentation and Splunk destination WAF rule examples.
What changed
Updated:
/content/docs/logs/logpush/logpush-job/enable-destinations/egress-ip.mdxUpdated:
rc/content/docs/logs/logpush/logpush-job/enable-destinations/splunk.mdxWhy
Logpush load-balances log delivery across multiple core datacenters for resilience. Traffic can originate from ASN 13335, 132892, or 202623, but the docs only listed the first two. Customers using ASN-based filtering were inadvertently blocking legitimate Logpush traffic and losing logs.
The egress IP page was missing one ASN. The Splunk page was more incomplete — it only referenced a single ASN (132892) with an equals operator, which would also block traffic from AS13335.