bgpreport

Network · data from 2026-11-12

AS214905 Layer3 Layer3 for Wireless communication Mixed LLC

Registry name: Layer3 Layer3 for Wireless communication Mixed LLC, SA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS214905, 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.
185.54.2.0/24 Valid RIR databaseRIPE 673 100% 67
185.54.3.0/24 Valid RIR databaseRIPE 673 100% 67
185.222.40.0/24 Valid RIR databaseRIPE 673 100% 67
213.254.176.0/23 Valid RIR databaseRIPE 673 100% 67
200.225.56.0/24 Valid RIR databaseRIPE 672 100% 67
2a14:4ac0::/29 Valid RIR databaseRIPE 632 99% 67
200.225.57.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

AS-SET

AS214905 isn't in PeeringDB, where networks name their 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 15 are in fix.csv.

  • Route object: not announced15

Route objects not announced

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

78.40.16.0/21RIPEValid
78.40.16.0/22RIPEValid
78.40.16.0/23RIPEValid
78.40.16.0/24RIPEValid
78.40.17.0/24RIPEValid
78.40.18.0/23RIPEValid
78.40.18.0/24RIPEValid
78.40.19.0/24RIPEValid
78.40.20.0/22RIPEValid
78.40.20.0/23RIPEValid
78.40.20.0/24RIPEValid
78.40.21.0/24RIPEValid
78.40.22.0/23RIPEValid
78.40.22.0/24RIPEValid
78.40.23.0/24RIPEValid

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.