bgpreport

Network · data from 2026-11-12

AS43769 EUROLAN-AS Eurolan Sp. zoo

Registry name: EUROLAN-AS Eurolan Sp. zoo, PL · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS43769, 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.
82.177.100.129/32 Invalid: maxLength Nonecovered by 82.177.100.0/24 4 1%low visibility 11
82.177.92.0/23 Valid RIR databaseRIPE 673 100% 66
82.177.95.0/24 Valid RIR databaseRIPE 673 100% 66
82.177.100.0/24 Valid RIR databaseRIPE 673 100% 66
82.177.110.0/24 Valid RIR databaseRIPE 673 100% 66
91.200.36.0/22 Valid RIR databaseRIPE 673 100% 66
91.200.36.0/24 Valid RIR databaseRIPE 673 100% 66
91.200.37.0/24 Valid RIR databaseRIPE 673 100% 66
194.183.50.0/24 Valid RIR databaseRIPE 673 100% 66
195.136.197.0/24 Valid RIR databaseRIPE 673 100% 66
195.178.26.0/23 Valid RIR databaseRIPE 673 100% 66
81.15.187.0/24 Valid RIR databaseRIPE 672 100% 66

AS-SET

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

  • ROA: maxLength1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: maxLength82.177.100.129/32ROA 82.177.100.0/24 AS43769 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 82.177.100.129/32.4 of 673
Route object: none82.177.100.129/32No route object for it. A route object for 82.177.100.0/24 with origin AS43769 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS43769 in the RIR database for the space.4 of 673

Route objects not announced

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

2a00:4120:8001::/48RIPEValid
2a10:f781:10:b91c::/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.