Spoofing Information for AS 835

Spoofing status per IP block (all dates)

Spoof status key
receivedSpoofed packet was received.Pattern of tests from this IP block indicates a switch from allowing spoofing to blocking it.
rewrittenSpoofed packet was received, but the source address was changed en route.
blockedSpoofed packet was not received, but unspoofed packet was.
unknownNeither spoofed nor unspoofed packet was received.
IP blockLatest testSpoof
170.39.230.x/242023-06-11 00:11:23 GMTblockedblocked
2602:fd50:1xx::/402023-06-11 00:11:23 GMTblockedblocked

Customers of AS 835 we have spoofer tests from

This is the list of directly connected customers of AS 835 from which we have received a spoofer test, ordered by the customer's ability to send spoofed packets and the number of prefixes of an inferred ingress ACL derived from prefix announcements for the customer recorded in the latest month of public BGP data. BCP-84 describes ingress ACLs as "the most bulletproof solution when done properly" and the "best fit ... when the configuration is not too dynamic, ... if the number of used prefixes is low." Further detail about the size and dynamism of an inferred ACL is available by following the History link for each AS.

ASNCountryNumber of Prefixes
in Customer Cone
Number of ASes
in Customer Cone
200182usa (United States)30AS 200182 testsblocked
52210 (AsreTeleCoM-SP)can (Canada)333AS 52210 testsblocked
8674 (NETNOD-IX)swe (Sweden)13122AS 8674 testsblocked

Address Space Announcement History

The customer cone for 835 is too large for a prefix list to be useful.

Last Modified