bgpreport

Network · data from 2026-11-12

AS11504 QUMULUSAI

Registry name: QUMULUSAI - The Cloud Minders, Inc., US · PeeringDB

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

Announced routes

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

69.8.146.0/24 No ROA Nonecovered by 69.8.144.0/20 671 100% 67
69.8.147.0/24 No ROA Nonecovered by 69.8.144.0/20 671 100% 67
69.8.148.0/24 No ROA Nonecovered by 69.8.144.0/20 671 100% 67
69.8.159.0/24 No ROA Nonecovered by 69.8.144.0/20 671 100% 67
69.8.144.0/24 No ROA Nonecovered by 69.8.144.0/20 670 100% 67
69.8.145.0/24 No ROA Nonecovered by 69.8.144.0/20 669 99% 67
205.196.19.0/24 No ROA None 666 99% 67
205.196.17.0/24 No ROA None 72 11% 38
157.254.50.0/24 Valid RIR databaseARIN, RADB 671 100% 67
66.92.198.0/24 Valid RIR databaseARIN, RADB 669 99% 67
205.196.144.0/24 Valid RIR databaseARIN, RADB 669 99% 67

AS-SET

PeeringDB's irr_as_set for AS11504: RS-AS11504. 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 (AS11504 isn't in the set, or no route object for AS11504 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 objectsAS11504 in itNot covered
RS-AS11504 A route-set, not an AS-SET; route-sets aren't expanded.

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

  • ROA: none8
  • Route object: none8
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none69.8.146.0/24No ROA covers it. Add a ROA for AS11504, maxLength 24.671 of 673
Route object: none69.8.146.0/24No route object for it. A route object for 69.8.144.0/20 with origin AS11504 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11504 in the RIR database for the space.671 of 673
ROA: none69.8.147.0/24No ROA covers it. Add a ROA for AS11504, maxLength 24.671 of 673
Route object: none69.8.147.0/24No route object for it. A route object for 69.8.144.0/20 with origin AS11504 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11504 in the RIR database for the space.671 of 673
ROA: none69.8.148.0/24No ROA covers it. Add a ROA for AS11504, maxLength 24.671 of 673
Route object: none69.8.148.0/24No route object for it. A route object for 69.8.144.0/20 with origin AS11504 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11504 in the RIR database for the space.671 of 673
ROA: none69.8.159.0/24No ROA covers it. Add a ROA for AS11504, maxLength 24.671 of 673
Route object: none69.8.159.0/24No route object for it. A route object for 69.8.144.0/20 with origin AS11504 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11504 in the RIR database for the space.671 of 673
ROA: none69.8.144.0/24No ROA covers it. Add a ROA for AS11504, maxLength 24.670 of 673
Route object: none69.8.144.0/24No route object for it. A route object for 69.8.144.0/20 with origin AS11504 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11504 in the RIR database for the space.670 of 673
ROA: none69.8.145.0/24No ROA covers it. Add a ROA for AS11504, maxLength 24.669 of 673
Route object: none69.8.145.0/24No route object for it. A route object for 69.8.144.0/20 with origin AS11504 covers it (filters allowing more-specifics accept it). Add a route object with origin AS11504 in the RIR database for the space.669 of 673
ROA: none205.196.19.0/24No ROA covers it. Add a ROA for AS11504, maxLength 24.666 of 673
Route object: none205.196.19.0/24No route object for it. Add a route object with origin AS11504 in the RIR database for the space.666 of 673
ROA: none205.196.17.0/24No ROA covers it. Add a ROA for AS11504, maxLength 24.72 of 673
Route object: none205.196.17.0/24No route object for it. Add a route object with origin AS11504 in the RIR database for the space.72 of 673

Route objects not announced

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

69.8.144.0/20ARINNo 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.