Spoofing Information for AS 2152 (CSUNET-NW)

Spoofing status per IP block for last year of data

(Results for all dates also available.)
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
207.62.80.x/242024-02-21 14:00:01 GMTblockedblocked
207.62.218.x/242024-02-21 14:00:01 GMTblockedblocked
2607:f380:xx::/402024-02-21 14:00:01 GMTblockedblocked

Customers of AS 2152 we have spoofer tests from

This is the list of directly connected customers of AS 2152 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
3701 (NERONET)usa (United States)6813AS 3701 testsreceived
6192 (UCDAVIS-CORE)usa (United States)70AS 6192 testsblocked
6106 (UCR-EDU)usa (United States)161AS 6106 testsblocked
7377 (UCSD)usa (United States)211AS 7377 testsblocked
195 (SDSC-AS)usa (United States)365AS 195 testsblocked

Address Space Announcement History

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

Last Modified