bgpreport

Network · data from 2026-11-12

AS402167 AS-NEBIUS-CENTRAL - Nebius Inc.

Registry name: AS-NEBIUS-CENTRAL - Nebius Inc., US · not in PeeringDB

3IPv4 routes 66.7% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
1No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS402167, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS402167, 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.

204.12.176.0/21 No ROA RIR databaseARIN 673 100% 67
204.12.174.0/24 Valid RIR databaseARIN 673 100% 67
204.12.175.0/24 Valid RIR databaseARIN 673 100% 67
2607:e840:220::/44 Valid RIR databaseARIN 618 97% 68
2607:e840:221::/48 Valid RIR databaseARIN 618 97% 68

AS-SET

AS402167 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 4 are in fix.csv.

  • ROA: none1
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none204.12.176.0/21No ROA covers it. Add a ROA for AS402167, maxLength 21.673 of 673

Route objects not announced

Route objects with origin AS402167 whose prefix no peer sees AS402167 announce. Many are kept on purpose (backup routes, space announced only in some places).

204.12.184.0/23ARINNo ROA
204.12.186.0/26ARINNo ROA
2607:e840:200::/40ARINNo ROA

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.