Network · data from 2026-11-12
AS34342 ATMAN AS34342
Registry name: ATMAN Atman Sp. z o.o., PL · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS34342, 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.
| 2001:1a68:19:400::/54 | Valid | None | 6 1%low visibility |
| 77.79.244.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 128.204.220.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.2.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 195.167.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 195.167.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 77.79.225.0/25 | Valid | RIR databaseRIPE | 1 0%low visibility |
AS-SET
AS34342'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 3 are in fix.csv.
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2001:1a68:19:400::/54 | No route object for it. Add a route object with origin AS34342 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS34342 whose prefix no peer sees AS34342 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 85.232.255.96/28 | RIPE | Invalid: origin |
| 128.204.216.80/28 | RIPE | Invalid: 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.