Network · data from 2026-11-12
AS216306 MAX_SET Max IT Finance Ltd
Registry name: MAX_SET Max IT Finance Ltd, IL · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS216306, 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.
| 50.21.28.0/22 | Valid | None | 673 100% |
| 50.21.28.0/24 | Valid | None | 672 100% |
| 50.21.29.0/24 | Valid | None | 672 100% |
| 50.21.30.0/24 | Valid | None | 672 100% |
| 50.21.31.0/24 | Valid | None | 672 100% |
AS-SET
AS216306 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 6 are in fix.csv.
- Route object: none5
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 50.21.28.0/22 | No route object for it. Add a route object with origin AS216306 in the RIR database for the space. |
| Route object: none | 50.21.28.0/24 | No route object for it. Add a route object with origin AS216306 in the RIR database for the space. |
| Route object: none | 50.21.29.0/24 | No route object for it. Add a route object with origin AS216306 in the RIR database for the space. |
| Route object: none | 50.21.30.0/24 | No route object for it. Add a route object with origin AS216306 in the RIR database for the space. |
| Route object: none | 50.21.31.0/24 | No route object for it. Add a route object with origin AS216306 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS216306 whose prefix no peer sees AS216306 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 91.208.118.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.