Spoofing Information for AS 8866 (BTC-AS)
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 | ||
|---|---|---|---|---|---|
| 46.249.78.x/24 | 2025-03-27 19:07:37 GMT | rewritten | rewritten | ||
| 212.5.158.x/24 | 2025-01-28 20:35:38 GMT | blocked | blocked | ||
| 2a01:5a8:5xx::/40 | 2025-01-28 20:35:38 GMT | blocked | blocked | ||
| 2a01:5a8:4xx::/40 | 2024-12-23 20:44:49 GMT | blocked | blocked | ||
Address Space Announcement History
The customer cone for 8866 is too large for a prefix list to be useful.