bgpreport

Network · data from 2026-11-12

AS401661 EMBNEX, LLC

Registry name: EMBNEX-AS - EMBNEX, LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS401661, 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.
16.5.0.0/24 Invalid: origin Other origin only 2 0%low visibility 2
2604:be0::/32 Valid None 635 100% 67
198.89.99.0/24 Valid RIR databaseARIN 671 100% 67
104.234.112.0/24 Valid RIR databaseARIN, RADB 668 99% 67

AS-SET

PeeringDB's irr_as_set for AS401661: AS401661:AS-CONE. 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 (AS401661 isn't in the set, or no route object for AS401661 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 objectsAS401661 in itNot covered
AS401661:AS-CONE ARIN 10262 Yes 2

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

  • ROA: origin1
  • Route object: none2
ChangePrefix or setDetailFull-table peers
ROA: origin16.5.0.0/24ROAs covering it name AS834, not AS401661. If AS401661 should announce it, add a ROA for AS401661.2 of 673
Route object: none16.5.0.0/24Route objects for it name AS834. Add a route object with origin AS401661 in the RIR database for the space.2 of 673
Route object: none2604:be0::/32No route object for it. Add a route object with origin AS401661 in the RIR database for the space.635 of 636

Route objects not announced

Every route object with origin AS401661 is announced.

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.