Network · data from 2026-11-12

AS401753 BIXCE

Registry name: BIXCE - BIXCE Inc, VG · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object

26IPv6 routes 100.0% RPKI valid · 100.0% with a route object

0RPKI invalid 0 origin · 0 maxLength

0No ROA 0 with no route object for this origin

0Low visibility seen by under 10% of full-table peers

0Route objects not announced registered with origin AS401753, seen from no peer

Announced routes

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


23.140.68.0/24	Valid	RIR databaseARIN	673 100%	66
2602:f61e::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:1::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:2::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:3::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:4::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:5::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:6::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:7::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:8::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:9::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:a::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:b::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:c::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:d::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:e::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:f::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:10::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:11::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:12::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:13::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:14::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:15::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:16::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:17::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e:18::/48	Valid	RIR databaseARIN	636 100%	69
2602:f61e::/42	Valid	RIR databaseARIN	635 100%	69

AS-SET

PeeringDB's irr_as_set for AS401753: ARIN::AS-BIXCE. 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 (AS401753 isn't in the set, or no route object for AS401753 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.

Name	Database	ASNs	Sets	Route objects	AS401753 in it	Not covered
ARIN::AS-BIXCE	ARIN	2	2	30	Yes	0

Name

Database

ASNs

Sets

Route objects

AS401753 in it

Not covered

ARIN::AS-BIXCE

ARIN

Yes

Fix list

Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.

Route objects not announced

Every route object with origin AS401753 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.