bgpreport

Network · data from 2026-11-12

AS12886 LEW TelNet

Registry name: LEWTELNET LEW TelNet GmbH, DE · PeeringDB

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

Announced routes

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

153.100.160.0/20 No ROA RIR databaseRIPE 672 100% 66
153.100.176.0/20 No ROA RIR databaseRIPE 672 100% 66
193.84.91.0/24 No ROA RIR databaseRIPE 672 100% 66
194.107.81.0/24 No ROA RIR databaseRIPE 672 100% 66
185.36.119.0/24 No ROA RIR databaseRIPE 671 100% 66
2001:678:113c::/48 No ROA RIR databaseRIPE 633 100% 67
2001:67c:2bac::/48 No ROA RIR databaseRIPE 633 100% 67
2a04:6780::/48 No ROA RIR databaseRIPE 633 100% 67
62.204.160.0/19 Valid RIR databaseRIPE 672 100% 66
94.101.120.0/22 Valid RIR databaseRIPE 672 100% 66
103.21.236.0/22 Valid RIR databaseRIPE 672 100% 66
103.51.228.0/22 Valid RIR databaseRIPE 672 100% 66
103.76.96.0/22 Valid RIR databaseRIPE 672 100% 66
103.192.160.0/22 Valid RIR databaseRIPE 672 100% 66
103.234.232.0/22 Valid RIR databaseRIPE 672 100% 66
128.65.144.0/21 Valid RIR databaseRIPE 672 100% 66
170.81.52.0/22 Valid RIR databaseRIPE 672 100% 66
170.84.228.0/22 Valid RIR databaseRIPE 672 100% 66
185.88.92.0/22 Valid RIR databaseRIPE 672 100% 66
185.255.248.0/22 Valid RIR databaseRIPE 672 100% 66
193.23.64.0/19 Valid RIR databaseRIPE 672 100% 66
193.23.148.0/22 Valid RIR databaseRIPE 672 100% 66
193.96.173.0/24 Valid RIR databaseRIPE 672 100% 66
212.118.192.0/19 Valid RIR databaseRIPE 672 100% 66
213.209.128.0/24 Valid RIR databaseRIPE 672 100% 66
213.209.142.0/24 Valid RIR databaseRIPE 672 100% 66
45.13.64.0/23 Valid RIR databaseRIPE 671 100% 66
185.188.18.0/24 Valid RIR databaseRIPE 671 100% 66
2a02:f90::/32 Valid RIR databaseRIPE 633 100% 67
2a13:8dc0::/47 Valid RIR databaseRIPE 632 99% 67

AS-SET

PeeringDB's irr_as_set for AS12886: RIPE::AS-LEWTELNET. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS12886 isn't in the set, or no route object for AS12886 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS12886 in itNot covered
RIPE::AS-LEWTELNET RIPE 6257 Yes 0

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

  • ROA: none8
ChangePrefix or setDetailFull-table peers
ROA: none153.100.160.0/20No ROA covers it. Add a ROA for AS12886, maxLength 20.672 of 673
ROA: none153.100.176.0/20No ROA covers it. Add a ROA for AS12886, maxLength 20.672 of 673
ROA: none193.84.91.0/24No ROA covers it. Add a ROA for AS12886, maxLength 24.672 of 673
ROA: none194.107.81.0/24No ROA covers it. Add a ROA for AS12886, maxLength 24.672 of 673
ROA: none185.36.119.0/24No ROA covers it. Add a ROA for AS12886, maxLength 24.671 of 673
ROA: none2001:678:113c::/48No ROA covers it. Add a ROA for AS12886, maxLength 48.633 of 636
ROA: none2001:67c:2bac::/48No ROA covers it. Add a ROA for AS12886, maxLength 48.633 of 636
ROA: none2a04:6780::/48No ROA covers it. Add a ROA for AS12886, maxLength 48.633 of 636

Route objects not announced

Every route object with origin AS12886 is announced.

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.