bgpreport

Network · data from 2026-11-12

AS205671 MAINPL MAIN Sp. z o.o.

Registry name: MAINPL MAIN Sp. z o.o., PL · not in PeeringDB

5IPv4 routes 20.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
5No 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 AS205671, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS205671, 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.
31.41.148.0/22 No ROA RIR databaseRIPE 672 100% 66
176.124.245.0/24 No ROA RIR databaseRIPE 672 100% 66
193.218.126.0/24 No ROA RIR databaseRIPE 672 100% 66
195.47.203.0/24 No ROA RIR databaseRIPE 672 100% 66
2a0b:5740::/29 No ROA RIR databaseRIPE 633 100% 69
185.210.124.0/22 Valid RIR databaseRIPE 672 100% 66

AS-SET

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

  • ROA: none5
ChangePrefix or setDetailFull-table peers
ROA: none31.41.148.0/22No ROA covers it. Add a ROA for AS205671, maxLength 22.672 of 673
ROA: none176.124.245.0/24No ROA covers it. Add a ROA for AS205671, maxLength 24.672 of 673
ROA: none193.218.126.0/24No ROA covers it. Add a ROA for AS205671, maxLength 24.672 of 673
ROA: none195.47.203.0/24No ROA covers it. Add a ROA for AS205671, maxLength 24.672 of 673
ROA: none2a0b:5740::/29No ROA covers it. Add a ROA for AS205671, maxLength 29.633 of 636

Route objects not announced

Every route object with origin AS205671 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.