bgpreport

Network · data from 2026-11-12

AS396417 SFDC-IT - Salesforce, Inc.

Registry name: SFDC-IT - Salesforce, Inc., US · not in PeeringDB

4IPv4 routes 25.0% RPKI valid · 100.0% with a route object
2IPv6 routes 0.0% RPKI valid · 0.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
3No ROA 2 with no route object for this origin
1Low visibility seen by under 10% of full-table peers
9Route objects not announced registered with origin AS396417, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS396417, 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.
2401:ce80:1001::/48 Invalid: origin None 95 15% 42
2401:ce80:1000::/48 Invalid: origin None 48 8%low visibility 28
104.161.242.0/23 No ROA Other IRR onlyRADB 673 100% 67
104.161.244.0/23 No ROA Other IRR onlyRADB 673 100% 67
104.161.246.0/23 No ROA Other IRR onlyRADB 673 100% 66
66.203.115.0/24 Valid Other IRR onlyRADB 673 100% 67

AS-SET

AS396417 isn't in PeeringDB, where networks name their 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 20 are in fix.csv.

  • ROA: origin2
  • ROA: none3
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced9
ChangePrefix or setDetailFull-table peers
ROA: origin2401:ce80:1001::/48ROAs covering it name AS14340, not AS396417. If AS396417 should announce it, add a ROA for AS396417.95 of 636
Route object: none2401:ce80:1001::/48No route object for it. Add a route object with origin AS396417 in the RIR database for the space.95 of 636
ROA: origin2401:ce80:1000::/48ROAs covering it name AS14340, not AS396417. If AS396417 should announce it, add a ROA for AS396417.48 of 636
Route object: none2401:ce80:1000::/48No route object for it. Add a route object with origin AS396417 in the RIR database for the space.48 of 636
ROA: none104.161.242.0/23No ROA covers it. Add a ROA for AS396417, maxLength 23.673 of 673
Route object: RIR104.161.242.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none104.161.244.0/23No ROA covers it. Add a ROA for AS396417, maxLength 23.673 of 673
Route object: RIR104.161.244.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none104.161.246.0/23No ROA covers it. Add a ROA for AS396417, maxLength 23.673 of 673
Route object: RIR104.161.246.0/23Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR66.203.115.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673

Route objects not announced

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

66.203.114.0/23RADBNo ROA
66.203.114.0/24RADBValid
192.195.4.0/23RADBNo ROA
192.195.4.0/24ARIN, RADBValid
192.195.5.0/24ARINValid
2600:e807:1111::/48RADBNo ROA
2600:e807:11f1::/48RADBNo ROA
2620:113:f000::/45RADBNo ROA
2631:a000::/24ARINValid

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.