Network · data from 2026-11-12
AS40662 Layer7 Technologies
Registry name: LAYER7-MITIGATION - Layer7 Technologies Inc, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS40662, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
| 2a0b:b480::/29 | Invalid: origin | None | 6 1%low visibility |
| 31.57.201.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 95.155.151.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 74.0.42.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
| 74.0.48.0/24 | Valid | RIR databaseARIN, RADB | 670 100% |
AS-SET
AS40662's PeeringDB record names no AS-SET.
Fix list
The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 4 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a0b:b480::/29 | An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS40662 should announce it, add a ROA for AS40662. |
| Route object: none | 2a0b:b480::/29 | No route object for it. Add a route object with origin AS40662 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS40662 whose prefix no peer sees AS40662 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 23.136.148.0/24 | ARIN | Valid |
| 2001:3480::/29 | RIPE | Valid |
Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.