Network · data from 2026-11-12
AS206793 EUROCONN EuroCon Global SP Z O.O.
Registry name: EUROCONN EuroCon Global SP Z O.O., PL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS206793, 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.
| 2a09:5740::/29 | No ROA | None | 634 100% |
| 185.176.120.0/22 | No ROA | RIR databaseRIPE | 671 100% |
| 185.176.120.0/24 | No ROA | RIR databaseRIPE | 671 100% |
| 185.176.122.0/24 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS206793 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 13 are in fix.csv.
- ROA: none4
- Route object: none1
- Route object: not announced8
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a09:5740::/29 | No ROA covers it. Add a ROA for AS206793, maxLength 29. |
| Route object: none | 2a09:5740::/29 | No route object for it. Add a route object with origin AS206793 in the RIR database for the space. |
| ROA: none | 185.176.120.0/22 | No ROA covers it. Add a ROA for AS206793, maxLength 22. |
| ROA: none | 185.176.120.0/24 | No ROA covers it. Add a ROA for AS206793, maxLength 24. |
| ROA: none | 185.176.122.0/24 | No ROA covers it. Add a ROA for AS206793, maxLength 24. |
Route objects not announced
Route objects with origin AS206793 whose prefix no peer sees AS206793 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2001:470:174::/48 | ARIN | Valid |
| 2001:470:23d::/48 | ARIN | Valid |
| 2001:470:2a1::/48 | ARIN | Valid |
| 2001:470:427::/48 | ARIN | Valid |
| 2001:470:44c::/48 | ARIN | Valid |
| 2001:470:4bd::/48 | ARIN | Valid |
| 2001:470:542::/48 | ARIN | Valid |
| 2001:470:647::/48 | ARIN | Valid |
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.