bgpreport

Network · data from 2026-11-12

AS57367 ATMAN XaaS

Registry name: ECO-ATMAN-PL Atman Sp. z o.o., PL · PeeringDB

40IPv4 routes 95.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.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
17Route objects not announced registered with origin AS57367, seen from no peer

Announced routes

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

192.54.220.0/24 No ROA RIR databaseRIPE 673 100% 66
194.33.187.0/24 No ROA RIR databaseRIPE 673 100% 66
31.186.80.0/21 Valid RIR databaseRIPE 673 100% 66
85.194.240.0/22 Valid RIR databaseRIPE 673 100% 66
85.194.242.0/24 Valid RIR databaseRIPE 673 100% 66
85.194.244.0/22 Valid RIR databaseRIPE 673 100% 66
85.194.246.0/24 Valid RIR databaseRIPE 673 100% 66
85.194.247.0/24 Valid RIR databaseRIPE 673 100% 66
85.232.241.0/24 Valid RIR databaseRIPE 673 100% 66
91.150.187.0/24 Valid RIR databaseRIPE 673 100% 66
91.185.184.0/24 Valid RIR databaseRIPE 673 100% 66
91.185.185.0/24 Valid RIR databaseRIPE 673 100% 66
91.185.186.0/24 Valid RIR databaseRIPE 673 100% 66
91.185.187.0/24 Valid RIR databaseRIPE 673 100% 67
91.185.188.0/24 Valid RIR databaseRIPE 673 100% 66
91.185.189.0/24 Valid RIR databaseRIPE 673 100% 66
91.185.190.0/24 Valid RIR databaseRIPE 673 100% 66
91.185.191.0/24 Valid RIR databaseRIPE 673 100% 66
128.204.216.0/24 Valid RIR databaseRIPE 673 100% 66
128.204.217.0/24 Valid RIR databaseRIPE 673 100% 66
128.204.218.0/24 Valid RIR databaseRIPE 673 100% 66
128.204.219.0/24 Valid RIR databaseRIPE 673 100% 66
128.204.220.0/22 Valid RIR databaseRIPE 673 100% 66
128.204.222.0/24 Valid RIR databaseRIPE 673 100% 66
128.204.223.0/24 Valid RIR databaseRIPE 673 100% 66
185.36.168.0/22 Valid RIR databaseRIPE 673 100% 66
195.167.159.0/24 Valid RIR databaseRIPE 673 100% 66
206.252.232.0/24 Valid RIR databaseRIPE 673 100% 66
206.252.251.0/24 Valid RIR databaseRIPE 673 100% 66
212.91.26.0/24 Valid RIR databaseRIPE 673 100% 66
212.91.27.0/24 Valid RIR databaseRIPE 673 100% 66
213.189.52.0/24 Valid RIR databaseRIPE 673 100% 66
213.189.53.0/24 Valid RIR databaseRIPE 673 100% 66
213.189.54.0/24 Valid RIR databaseRIPE 673 100% 66
213.189.55.0/24 Valid RIR databaseRIPE 673 100% 66
213.189.56.0/24 Valid RIR databaseRIPE 673 100% 66
213.189.58.0/24 Valid RIR databaseRIPE 673 100% 66
77.79.227.0/24 Valid RIR databaseRIPE 672 100% 66
77.79.248.0/24 Valid RIR databaseRIPE 672 100% 66
77.79.250.0/24 Valid RIR databaseRIPE 672 100% 66
2001:1a68:19::/48 Valid RIR databaseRIPE 634 100% 70
2001:1a68:ec00::/40 Valid RIR databaseRIPE 634 100% 70

AS-SET

AS57367's PeeringDB record names no 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 19 are in fix.csv.

  • ROA: none2
  • Route object: not announced17
ChangePrefix or setDetailFull-table peers
ROA: none192.54.220.0/24No ROA covers it. Add a ROA for AS57367, maxLength 24.673 of 673
ROA: none194.33.187.0/24No ROA covers it. Add a ROA for AS57367, maxLength 24.673 of 673

Route objects not announced

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

77.79.211.0/24RIPEValid
85.194.240.0/24RIPEInvalid: maxLength
91.185.184.0/22RIPENo ROA
91.194.210.0/23RIPENo ROA
91.214.180.0/23RIPENo ROA
91.214.182.0/23RIPENo ROA
128.204.216.0/21RIPENo ROA
128.204.220.0/24RIPEValid
128.204.221.0/24RIPEValid
185.2.112.0/24RIPEInvalid: origin
185.2.113.0/24RIPEInvalid: origin
185.2.114.0/24RIPEInvalid: origin
185.2.115.0/24RIPEInvalid: origin
212.91.4.0/25RIPEInvalid: origin
213.189.59.0/24RIPEInvalid: origin
2001:1a68:1a::/48RIPEValid
2001:1a68:32::/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.