bgpreport

Network · data from 2026-11-19

AS64271 rixCloud, Inc.

Registry name: RIXCLOUD-INC - rixCloud, US · PeeringDB

1IPv4 routes 100.0% RPKI valid · 100.0% with a route object
0IPv6 routes
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
6Route objects not announced registered with origin AS64271, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS64271, things to look at first. Visibility = full-table peers that see it, of 672 (IPv4) and 633 (IPv6) on 75 collectors. Also as routes.csv.

23.150.33.0/24 Valid RIR databaseARIN 669 100% 67

AS-SET

PeeringDB's irr_as_set for AS64271: AS-RIXCLOUD. 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 (AS64271 isn't in the set, or no route object for AS64271 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 objectsAS64271 in itNot covered
AS-RIXCLOUD RADB 183854 Yes 0
ARIN (also) 117 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.

  • Route object: not announced6

Route objects not announced

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

103.147.198.0/23APNICValid
103.147.198.0/24APNICValid
103.147.199.0/24APNICValid
2404:bac0::/32RADBNo ROA
2604:d6c0::/32ARIN, RADBValid
2604:d6c0:5000::/36RADBValid

Routes: the 08:00 UTC snapshots of 2026-11-19 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.