Network · data from 2026-11-12
AS50937 INFINITIUM CORPORATION
Registry name: INFINITIUM-AS INFINITIUM CORPORATION, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS50937, 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.
| 2a14:3b41::/48 | Valid | Other origin onlycovered by 2a14:3b41::/32 | 49 8%low visibility |
| 194.117.85.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 66.33.37.0/24 | Valid | RIR databaseRIPE | 645 96% |
| 2a14:3b40::/48 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS50937'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 4 are in fix.csv.
- Route object: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2a14:3b41::/48 | Route objects for it name AS216357. A route object for 2a14:3b41::/32 with origin AS50937 covers it (filters allowing more-specifics accept it). Add a route object with origin AS50937 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS50937 whose prefix no peer sees AS50937 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a14:3b40::/32 | RIPE | Valid |
| 2a14:3b40::/36 | RIPE | Valid |
| 2a14:3b41::/32 | 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.