bgpreport

Network · data from 2026-11-12

AS23116 Enovum Data Centers Corp.

Registry name: EDCC-1-23116 - Enovum Data Centers Corp., CA · PeeringDB

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

Announced routes

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

154.51.46.0/23 No ROA Other IRR onlyRADB 671 100% 68
198.13.251.0/24 No ROA Other IRR onlyRADB 671 100% 68

AS-SET

PeeringDB's irr_as_set for AS23116: AS-ENOVUM. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS23116 isn't in the set, or no route object for AS23116 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS23116 in itNot covered
AS-ENOVUM RADB 114 Yes 0

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.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none154.51.46.0/23No ROA covers it. Add a ROA for AS23116, maxLength 23.671 of 673
Route object: RIR154.51.46.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none198.13.251.0/24No ROA covers it. Add a ROA for AS23116, maxLength 24.671 of 673
Route object: RIR198.13.251.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673

Route objects not announced

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

154.51.47.0/24RADBNo ROA
2001:470:4ac::/48ARINValid

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.