Network · data from 2026-11-12
AS51647 Gemeente-Amsterdam Gemeente Amsterdam
Registry name: Gemeente-Amsterdam Gemeente Amsterdam, NL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS51647, 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.
| 2a07:3500:1020::/46 | Valid | None | 634 100% |
| 46.17.24.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 194.13.133.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 194.104.80.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 194.104.84.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 2a04:9fc0::/29 | Valid | RIR databaseRIPE | 633 100% |
AS-SET
AS51647 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 2 are in fix.csv.
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a07:3500:1020::/46 | No route object for it. Add a route object with origin AS51647 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS51647 whose prefix no peer sees AS51647 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 194.104.80.0/24 | RIPE | Invalid: maxLength |
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.