bgpreport

Network · data from 2026-11-12

AS33923 ART-COM Sp. z o.o.

Registry name: ART-COM ART-COM Sp. z o.o., PL · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS33923, 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.
94.246.133.230/32 Valid Nonecovered by 94.246.128.0/19 2 0%low visibility 6
94.246.136.64/32 Valid Nonecovered by 94.246.128.0/19 2 0%low visibility 6
94.246.146.222/32 Valid Nonecovered by 94.246.128.0/19 2 0%low visibility 6
94.246.151.165/32 Valid Nonecovered by 94.246.128.0/19 2 0%low visibility 6
94.246.163.3/32 Valid Nonecovered by 94.246.160.0/19 2 0%low visibility 6
94.246.128.0/18 Valid RIR databaseRIPE 671 100% 68
185.183.236.0/22 Valid RIR databaseRIPE 671 100% 68
194.6.246.0/24 Valid RIR databaseRIPE 671 100% 68
194.145.184.0/22 Valid RIR databaseRIPE 671 100% 68
2a00:1a40::/32 Valid RIR databaseRIPE 634 100% 67
94.246.128.0/19 Valid RIR databaseRIPE 22 3%low visibility 23
94.246.160.0/19 Valid RIR databaseRIPE 22 3%low visibility 23

AS-SET

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

  • Route object: none5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none94.246.133.230/32No route object for it. A route object for 94.246.128.0/19 with origin AS33923 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS33923 in the RIR database for the space.2 of 673
Route object: none94.246.136.64/32No route object for it. A route object for 94.246.128.0/19 with origin AS33923 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS33923 in the RIR database for the space.2 of 673
Route object: none94.246.146.222/32No route object for it. A route object for 94.246.128.0/19 with origin AS33923 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS33923 in the RIR database for the space.2 of 673
Route object: none94.246.151.165/32No route object for it. A route object for 94.246.128.0/19 with origin AS33923 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS33923 in the RIR database for the space.2 of 673
Route object: none94.246.163.3/32No route object for it. A route object for 94.246.160.0/19 with origin AS33923 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS33923 in the RIR database for the space.2 of 673

Route objects not announced

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

2a10:f781:10:8ec3::/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.