bgpreport

Network · data from 2026-11-12

AS394256 Tech Futures Interactive Inc.

Registry name: CLOUDSINGULARITY - Tech Futures Interactive Inc., CA · PeeringDB

22IPv4 routes 45.5% RPKI valid · 86.4% with a route object
12IPv6 routes 100.0% RPKI valid · 50.0% with a route object
2RPKI invalid 0 origin · 2 maxLength
10No ROA 9 with no route object for this origin
7Low visibility seen by under 10% of full-table peers
27Route objects not announced registered with origin AS394256, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS394256, 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.83.208.0/22 Invalid: maxLength Nonecovered by 23.83.208.0/21 1 0%low visibility 1
23.83.212.0/22 Invalid: maxLength Nonecovered by 23.83.208.0/21 1 0%low visibility 1
38.88.124.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.240.224.0/24 No ROA Other IRR onlyRADB 670 100% 67
38.240.225.0/24 No ROA Other IRR onlyRADB 670 100% 67
38.240.226.0/24 No ROA Other IRR onlyRADB 670 100% 68
38.240.227.0/24 No ROA Other IRR onlyRADB 670 100% 68
104.218.61.0/24 No ROA Other IRR onlyRADB 670 100% 68
205.137.251.0/24 No ROA Other IRR onlyRADB 670 100% 68
104.250.160.0/24 No ROA Other IRR onlyRADB 668 99% 68
172.111.142.0/23 No ROA Other IRR onlyRADB 664 99% 68
172.111.239.0/24 No ROA Other IRR onlyRADB 664 99% 68
2606:9580:438::/48 Valid Nonecovered by 2606:9580:400::/40 635 100% 69
2606:9580:ff03::/48 Valid Nonecovered by 2606:9580::/32 635 100% 69
192.30.88.0/24 Valid Nonecovered by 192.30.88.0/23 1 0%low visibility 1
2606:9580:89::/48 Valid Nonecovered by 2606:9580::/40 1 0%low visibility 1
2606:9580:101::/48 Valid Nonecovered by 2606:9580:100::/40 1 0%low visibility 1
2606:9580:104::/48 Valid Nonecovered by 2606:9580:100::/40 1 0%low visibility 1
2606:9580:105::/48 Valid Nonecovered by 2606:9580:100::/40 1 0%low visibility 1
193.188.2.0/24 Valid Other IRR onlyRADB 671 100% 67
193.188.3.0/24 Valid Other IRR onlyRADB 671 100% 67
23.173.88.0/24 Valid Other IRR onlyRADB 670 100% 68
104.193.132.0/24 Valid Other IRR onlyRADB 670 100% 68
104.193.135.0/24 Valid Other IRR onlyRADB 670 100% 68
192.30.88.0/23 Valid Other IRR onlyRADB 670 100% 68
193.188.15.0/24 Valid Other IRR onlyRADB 670 100% 68
2606:9580:300::/40 Valid Other IRR onlyRADB 636 100% 67
2602:f95a::/36 Valid Other IRR onlyRADB 635 100% 69
2606:9580::/40 Valid Other IRR onlyRADB 635 100% 69
2606:9580:100::/40 Valid Other IRR onlyRADB 635 100% 69
2606:9580:400::/40 Valid Other IRR onlyRADB 635 100% 69
2606:9580:fffa::/48 Valid Other IRR onlyRADB 635 100% 69
193.188.14.0/24 Valid Other IRR onlyRADB 98 15% 37
23.83.208.0/21 Valid RIR databaseARIN, RADB 670 100% 68

AS-SET

PeeringDB's irr_as_set for AS394256: AS-CLOUDSINGULARITY. 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 (AS394256 isn't in the set, or no route object for AS394256 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 objectsAS394256 in itNot covered
AS-CLOUDSINGULARITY RADB4 member sets in no database: AS-MOTP, AS-ROUTE48, AS199746:AS-NEXTSERV, AS203867:AS-CUSTOMERS 5039811,445 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 76 are in fix.csv.

  • ROA: maxLength2
  • ROA: none10
  • Route object: none9
  • Route object: RIR24
  • AS-SET: missing member4
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: maxLength23.83.208.0/22ROA 23.83.208.0/21 AS394256 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 23.83.208.0/22.1 of 673
Route object: none23.83.208.0/22No route object for it. A route object for 23.83.208.0/21 with origin AS394256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394256 in the RIR database for the space.1 of 673
ROA: maxLength23.83.212.0/22ROA 23.83.208.0/21 AS394256 has maxLength 21; the route is a /22. Raise the maxLength, or add a ROA for 23.83.212.0/22.1 of 673
Route object: none23.83.212.0/22No route object for it. A route object for 23.83.208.0/21 with origin AS394256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394256 in the RIR database for the space.1 of 673
ROA: none38.88.124.0/24No ROA covers it. Add a ROA for AS394256, maxLength 24.670 of 673
Route object: RIR38.88.124.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.240.224.0/24No ROA covers it. Add a ROA for AS394256, maxLength 24.670 of 673
Route object: RIR38.240.224.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.240.225.0/24No ROA covers it. Add a ROA for AS394256, maxLength 24.670 of 673
Route object: RIR38.240.225.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.240.226.0/24No ROA covers it. Add a ROA for AS394256, maxLength 24.670 of 673
Route object: RIR38.240.226.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none38.240.227.0/24No ROA covers it. Add a ROA for AS394256, maxLength 24.670 of 673
Route object: RIR38.240.227.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none104.218.61.0/24No ROA covers it. Add a ROA for AS394256, maxLength 24.670 of 673
Route object: RIR104.218.61.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none205.137.251.0/24No ROA covers it. Add a ROA for AS394256, maxLength 24.670 of 673
Route object: RIR205.137.251.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none104.250.160.0/24No ROA covers it. Add a ROA for AS394256, maxLength 24.668 of 673
Route object: RIR104.250.160.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none172.111.142.0/23No ROA covers it. Add a ROA for AS394256, maxLength 23.664 of 673
Route object: RIR172.111.142.0/23Route object only in RADB. Add it in the RIR database for the space.664 of 673
ROA: none172.111.239.0/24No ROA covers it. Add a ROA for AS394256, maxLength 24.664 of 673
Route object: RIR172.111.239.0/24Route object only in RADB. Add it in the RIR database for the space.664 of 673
Route object: none2606:9580:438::/48No route object for it. A route object for 2606:9580:400::/40 with origin AS394256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394256 in the RIR database for the space.635 of 636
Route object: none2606:9580:ff03::/48No route object for it. A route object for 2606:9580::/32 with origin AS394256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394256 in the RIR database for the space.635 of 636
Route object: none192.30.88.0/24No route object for it. A route object for 192.30.88.0/23 with origin AS394256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394256 in the RIR database for the space.1 of 673
Route object: none2606:9580:89::/48No route object for it. A route object for 2606:9580::/40 with origin AS394256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394256 in the RIR database for the space.1 of 636
Route object: none2606:9580:101::/48No route object for it. A route object for 2606:9580:100::/40 with origin AS394256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394256 in the RIR database for the space.1 of 636
Route object: none2606:9580:104::/48No route object for it. A route object for 2606:9580:100::/40 with origin AS394256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394256 in the RIR database for the space.1 of 636
Route object: none2606:9580:105::/48No route object for it. A route object for 2606:9580:100::/40 with origin AS394256 covers it (filters allowing more-specifics accept it). Add a route object with origin AS394256 in the RIR database for the space.1 of 636
Route object: RIR193.188.2.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR193.188.3.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR23.173.88.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR104.193.132.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR104.193.135.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR192.30.88.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR193.188.15.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR2606:9580:300::/40Route object only in RADB. Add it in the RIR database for the space.636 of 636
Route object: RIR2602:f95a::/36Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2606:9580::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2606:9580:100::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2606:9580:400::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR2606:9580:fffa::/48Route object only in RADB. Add it in the RIR database for the space.635 of 636
Route object: RIR193.188.14.0/24Route object only in RADB. Add it in the RIR database for the space.98 of 673
AS-SET: missing memberAS-CLOUDSINGULARITYAS-CLOUDSINGULARITY (RADB) lists AS-MOTP; no IRR database read has it.
AS-SET: missing memberAS-CLOUDSINGULARITYAS-CLOUDSINGULARITY (RADB) lists AS-ROUTE48; no IRR database read has it.
AS-SET: missing memberAS-CLOUDSINGULARITYAS-CLOUDSINGULARITY (RADB) lists AS199746:AS-NEXTSERV; no IRR database read has it.
AS-SET: missing memberAS-CLOUDSINGULARITYAS-CLOUDSINGULARITY (RADB) lists AS203867:AS-CUSTOMERS; no IRR database read has it.

Route objects not announced

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

23.190.64.0/24RADBValid
38.15.168.0/21RADBNo ROA
38.15.176.0/21RADBNo ROA
38.88.88.0/24RADBNo ROA
38.88.124.0/23RADBNo ROA
38.88.125.0/24RADBNo ROA
38.240.226.0/23RADBNo ROA
44.135.193.0/24RADBNo ROA
104.192.172.0/22RADBNo ROA
104.193.132.0/22RADBValid
104.218.56.0/21RADBNo ROA
104.218.60.0/23RADBNo ROA
104.218.63.0/24RADBNo ROA
172.111.238.0/23RADBNo ROA
192.34.26.0/23RADBNo ROA
193.188.2.0/23RADBValid
193.188.14.0/23RADBValid
206.123.136.0/23RADBNo ROA
206.123.136.0/24ARINInvalid: origin
2001:470:1bf::/48ARINInvalid: origin
2001:470:1ce::/48ARINInvalid: origin
2001:470:1d1::/48ARINInvalid: origin
2001:470:5e8::/48ARINValid
2606:1a40:200c::/48RADBNo ROA
2606:1a40:200d::/48RADBNo ROA
2606:9580::/32RADBValid
2606:9580:200::/40RADBValid

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.