bgpreport

Network · data from 2026-11-12

AS394808 DEMANDWARE

Registry name: DEMAN-AS - Salesforce.com, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS394808, 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.
104.161.255.0/24 No ROA Other IRR onlyNTTCOM 672 100% 67
104.161.232.0/24 No ROA Other IRR onlyRADB 668 99% 67
104.161.233.0/24 No ROA Other IRR onlyRADB 668 99% 67
104.161.252.0/24 Valid Other IRR onlyNTTCOM, RADB 667 99% 67
104.161.253.0/24 Valid Other IRR onlyNTTCOM, RADB 667 99% 67
104.161.234.0/24 Valid RIR databaseAPNIC, NTTCOM 668 99% 67
104.161.235.0/24 Valid RIR databaseAPNIC, NTTCOM 668 99% 67

AS-SET

AS394808's PeeringDB record names no AS-SET.

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

  • ROA: none3
  • Route object: RIR5
  • Route object: not announced15
ChangePrefix or setDetailFull-table peers
ROA: none104.161.255.0/24No ROA covers it. Add a ROA for AS394808, maxLength 24.672 of 673
Route object: RIR104.161.255.0/24Route object only in NTTCOM. Add it in the RIR database for the space.672 of 673
ROA: none104.161.232.0/24No ROA covers it. Add a ROA for AS394808, maxLength 24.668 of 673
Route object: RIR104.161.232.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none104.161.233.0/24No ROA covers it. Add a ROA for AS394808, maxLength 24.668 of 673
Route object: RIR104.161.233.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR104.161.252.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR104.161.253.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

75.98.80.0/24RADBNo ROA
83.231.150.192/27NTTCOMValid
104.161.232.0/23RADBNo ROA
104.161.234.0/23APNIC, NTTCOMValid
104.161.250.0/23NTTCOM, RADBNo ROA
104.161.250.0/24RADBNo ROA
104.161.251.0/24RADBNo ROA
104.161.252.0/22NTTCOM, RADBNo ROA
104.161.254.0/24NTTCOM, RADBNo ROA
151.106.192.0/24RADBNo ROA
151.106.204.0/24RIPENo ROA
151.106.209.0/24RIPENo ROA
194.145.0.0/19RIPENo ROA
194.145.24.0/21RIPENo ROA
194.145.31.0/24RIPENo 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.