bgpreport

Network · data from 2026-11-12

AS204444 LanTech

Registry name: LANTECH-AS LanTech Piotr Pilek, PL · PeeringDB

7IPv4 routes 100.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
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS204444, seen from no peer

Announced routes

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

2001:67c:2b68::/48 No ROA RIR databaseRIPE 636 100% 67
80.94.28.0/23 Valid RIR databaseRIPE 671 100% 67
194.76.41.0/24 Valid RIR databaseRIPE 671 100% 67
194.76.44.0/24 Valid RIR databaseRIPE 671 100% 67
194.76.53.0/24 Valid RIR databaseRIPE 671 100% 67
212.14.60.0/24 Valid RIR databaseRIPE 671 100% 67
213.155.167.0/24 Valid RIR databaseRIPE 671 100% 67
80.94.27.0/24 Valid RIR databaseRIPE 670 100% 67

AS-SET

PeeringDB's irr_as_set for AS204444: RIPE::AS-LTNT. 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 (AS204444 isn't in the set, or no route object for AS204444 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 objectsAS204444 in itNot covered
RIPE::AS-LTNT RIPE 3131 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 3 are in fix.csv.

  • ROA: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2001:67c:2b68::/48No ROA covers it. Add a ROA for AS204444, maxLength 48.636 of 636

Route objects not announced

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

2a0f:adc0::/29RIPENo ROA
2a10:f781:10:aea6::/64RIPENo 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.