Network · data from 2026-11-12
AS204326 Gate t1
Registry name: firstAS-gatet1 GATE T1 SRL, IT · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204326, 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.132.40.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 171.22.92.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.18.240.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 2a04:d00::/29 | Valid | RIR databaseRIPE | 379 60% |
| 2a09:3cc0::/29 | Valid | RIR databaseRIPE | 379 60% |
| 2a0d:9f40::/29 | Valid | RIR databaseRIPE | 379 60% |
AS-SET
AS204326'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 12 are in fix.csv.
- Route object: not announced12
Route objects not announced
Route objects with origin AS204326 whose prefix no peer sees AS204326 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.132.40.0/24 | RIPE | Valid |
| 31.132.41.0/24 | RIPE | Valid |
| 31.132.42.0/24 | RIPE | Valid |
| 31.132.43.0/24 | RIPE | Valid |
| 171.22.92.0/24 | RIPE | Valid |
| 171.22.93.0/24 | RIPE | Valid |
| 171.22.94.0/24 | RIPE | Valid |
| 171.22.95.0/24 | RIPE | Valid |
| 185.18.240.0/24 | RIPE | Valid |
| 185.18.241.0/24 | RIPE | Valid |
| 185.18.242.0/24 | RIPE | Valid |
| 185.18.243.0/24 | RIPE | 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.