Spoofing Information for AS 52468
Spoofing status per IP block for last year of data
(Results for all dates also available.)| Spoof status key | ||||
|---|---|---|---|---|
| received | Spoofed packet was received. | ✔ | Pattern of tests from this IP block indicates a switch from allowing spoofing to blocking it. | |
| rewritten | Spoofed packet was received, but the source address was changed en route. | |||
| blocked | Spoofed packet was not received, but unspoofed packet was. | |||
| unknown | Neither spoofed nor unspoofed packet was received. | |||
| IP block | Latest test | Spoof Private | Spoof Routable | ||
|---|---|---|---|---|---|
| 157.100.52.x/24 | 2026-01-13 21:19:59 GMT | rewritten | received | ||
| 190.60.48.x/24 | 2026-02-12 16:37:30 GMT | rewritten | rewritten | ||
| 190.61.87.x/24 | 2025-12-26 23:51:34 GMT | blocked | blocked | ||
| 200.24.159.x/24 | 2026-01-30 22:40:11 GMT | blocked | received | ||
Customers of AS 52468 we have spoofer tests from
This is the list of directly connected customers of AS 52468 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.
Address Space Announcement History
The customer cone for 52468 is too large for a prefix list to be useful.