bgpreport

Network · data from 2026-11-12

AS47277 LWLCOM-HOSTING LWLcom GmbH

Registry name: LWLCOM-HOSTING LWLcom GmbH, DE · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS47277, 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.
176.65.153.0/24 No ROA RIR databaseRIPE 673 100% 67
2a06:de04:10::/48 No ROA RIR databaseRIPE 635 100% 67
89.106.78.0/24 Valid RIR databaseRIPE 673 100% 67
94.249.199.0/24 Valid RIR databaseRIPE 673 100% 67
81.85.82.0/24 Valid RIR databaseRIPE 672 100% 67
81.85.83.0/24 Valid RIR databaseRIPE 672 100% 67

AS-SET

AS47277 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 6 are in fix.csv.

  • ROA: none2
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
ROA: none176.65.153.0/24No ROA covers it. Add a ROA for AS47277, maxLength 24.673 of 673
ROA: none2a06:de04:10::/48No ROA covers it. Add a ROA for AS47277, maxLength 48.635 of 636

Route objects not announced

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

45.151.240.0/24RIPEValid
81.85.82.0/23RIPEInvalid: origin
193.3.128.0/24RIPEValid
2a00:c380:b801::/48RIPEInvalid: origin

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.