bgpreport

Network · data from 2026-11-12

AS40911 L2Net (Synips xSP, Enguity nSP)

Registry name: L2NC-AS - L2Networks Corp., US · PeeringDB

7IPv4 routes 100.0% RPKI valid · 57.1% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
0No ROA 3 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
12Route objects not announced registered with origin AS40911, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS40911, 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.

65.48.124.0/24 Valid Nonecovered by 65.48.112.0/20 672 100% 66
65.48.122.0/24 Valid Nonecovered by 65.48.112.0/20 669 99% 67
65.48.123.0/24 Valid Nonecovered by 65.48.112.0/20 669 99% 67
65.48.115.0/24 Valid Other IRR onlyRADB 664 99% 67
65.48.116.0/24 Valid Other IRR onlyRADB 664 99% 67
65.48.127.0/24 Valid Other IRR onlyRADB 664 99% 67
65.48.112.0/20 Valid RIR databaseARIN, RADB 666 99% 67

AS-SET

AS40911'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 18 are in fix.csv.

  • Route object: none3
  • Route object: RIR3
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
Route object: none65.48.124.0/24No route object for it. A route object for 65.48.112.0/20 with origin AS40911 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40911 in the RIR database for the space.672 of 673
Route object: none65.48.122.0/24No route object for it. A route object for 65.48.112.0/20 with origin AS40911 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40911 in the RIR database for the space.669 of 673
Route object: none65.48.123.0/24No route object for it. A route object for 65.48.112.0/20 with origin AS40911 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40911 in the RIR database for the space.669 of 673
Route object: RIR65.48.115.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR65.48.116.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: RIR65.48.127.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673

Route objects not announced

Route objects with origin AS40911 whose prefix no peer sees AS40911 announce. Many are kept on purpose (backup routes, space announced only in some places).

63.166.22.0/24RADBNo ROA
65.48.114.0/24RADBValid
65.48.118.0/24RADBValid
65.48.125.0/24RADBValid
65.112.137.0/24RADBNo ROA
198.77.238.0/23RADBNo ROA
199.44.85.0/24RADBNo ROA
199.44.253.0/24RADBNo ROA
204.181.199.0/24RADBNo ROA
204.251.239.0/24RADBNo ROA
208.2.24.0/22RADBNo ROA
2607:fbb8::/32RADBNo ROA

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.