bgpreport

Network · data from 2026-11-12

AS22606 EXACT-7

Registry name: EXACT-7 - Salesforce.com, Inc., US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS22606, 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.
64.132.88.0/24 No ROA Other origin onlycovered by 64.132.88.0/23 670 100% 67
64.132.89.0/24 No ROA Nonecovered by 64.132.88.0/23 670 100% 67
64.132.92.0/24 No ROA Other IRR onlyALTDB 670 100% 67
207.67.38.0/24 No ROA Other IRR onlyALTDB 670 100% 67
207.250.68.0/24 No ROA Other IRR onlyALTDB 670 100% 67

AS-SET

AS22606'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 18 are in fix.csv.

  • ROA: none5
  • Route object: none2
  • Route object: RIR3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none64.132.88.0/24No ROA covers it. Add a ROA for AS22606, maxLength 24.670 of 673
Route object: none64.132.88.0/24Route objects for it name AS198948. A route object for 64.132.88.0/23 with origin AS22606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22606 in the RIR database for the space.670 of 673
ROA: none64.132.89.0/24No ROA covers it. Add a ROA for AS22606, maxLength 24.670 of 673
Route object: none64.132.89.0/24No route object for it. A route object for 64.132.88.0/23 with origin AS22606 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22606 in the RIR database for the space.670 of 673
ROA: none64.132.92.0/24No ROA covers it. Add a ROA for AS22606, maxLength 24.670 of 673
Route object: RIR64.132.92.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none207.67.38.0/24No ROA covers it. Add a ROA for AS22606, maxLength 24.670 of 673
Route object: RIR207.67.38.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673
ROA: none207.250.68.0/24No ROA covers it. Add a ROA for AS22606, maxLength 24.670 of 673
Route object: RIR207.250.68.0/24Route object only in ALTDB. Add it in the RIR database for the space.670 of 673

Route objects not announced

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

13.111.0.0/16ALTDBValid
64.132.88.0/23ALTDBNo ROA
66.231.80.0/20RADBValid
68.232.192.0/20RADBValid
136.147.176.0/20ALTDB, RADBValid
198.245.80.0/20ALTDB, RADBValid
199.122.120.0/21ALTDBValid
2620:102:700a::/48ALTDBNo 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.