Network · data from 2026-11-12
AS202004 GreenLan Fiber sp. z o.o. sp.k.
Registry name: GREENLAN-AS GreenLan Fiber Sp. z o.o. Sp.k., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202004, 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.
| 185.56.211.0/32 | Invalid: maxLength | Nonecovered by 185.56.208.0/22 | 2 0%low visibility |
| 45.11.60.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.56.208.0/22 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS202004'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 5 are in fix.csv.
- ROA: maxLength1
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 185.56.211.0/32 | ROA 185.56.208.0/22 AS202004 has maxLength 24; the route is a /32. Raise the maxLength, or add a ROA for 185.56.211.0/32. |
| Route object: none | 185.56.211.0/32 | No route object for it. A route object for 185.56.208.0/22 with origin AS202004 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS202004 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202004 whose prefix no peer sees AS202004 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.38.222.0/23 | RIPE | Valid |
| 2a02:55e0::/32 | RIPE | No ROA |
| 2a10:f781:10:4c::/64 | RIPE | No 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.