Salesforce issues

Mailman List Mirror (Read Only)
1

We are receiving latency complaints to Salesforce, anyone else seeing this?

Looks like Vocus Network might be possibly leaking some force.com (Salesforce) routes, causing 200ms of latency. Traffic is going Chicago → Vocus Networks → Australia → Akamai Atlanta

I have emailed both Vocus Networks and Akamai about this.

dig force.com +short

104.109.10.129 <<< Possible Leaked via Vocus Networks

104.109.11.129 <<< Possible Leaked via Vocus Networks

184.25.179.132 <<< Possible Leaked via Vocus Networks

184.31.3.130 <<<<< Route ok (NTT, TATA, Akamai) 25ms

184.31.10.133 <<< Route ok (NTT, Akamai) 16ms

23.1.35.132 <<< Possible Leaked via Vocus Networks

23.1.99.130 <<< Route ok (Akamai) 15 ms

23.1.106.133 <<< Route ok (NTT, Akamai) 16ms

2021-11-24T13:47:59-0600

Keys: Help Display mode Restart statistics Order of fields quit

Packets Pings

Host Loss% Snt Last Avg Best Wrst StDev

  1. AS??? 172.19.1.2 (172.19.1.2) 0.0% 7 1.7 1.9 0.9 4.8 1.3

  2. ???

  3. AS53828 207.200.193.193 (207.200.193.193) 0.0% 6 1.0 1.0 0.9 1.0 0.1

  4. AS??? eqix-ch1.vocusconnect.com (208.115.136.142) 0.0% 6 41.0 40.8 40.8 41.0 0.1

  5. AS4826 be101.bdr04.sjc01.ca.us.vocus.network (114.31.199.38) 40.0% 6 200.6 200.7 200.6 200.8 0.1

[MPLS: Lbl 24266 Exp 0 S 1 TTL 1]

  1. AS4826 be100.bdr03.sjc01.ca.us.vocus.network (114.31.199.32) 0.0% 6 197.4 197.5 197.4 197.5 0.0

[MPLS: Lbl 24807 Exp 0 S 1 TTL 1]

  1. AS4826 be202.cor02.syd04.nsw.vocus.network (114.31.199.42) 0.0% 6 197.4 197.4 197.3 197.5 0.1

[MPLS: Lbl 24932 Exp 0 S 1 TTL 1]

  1. AS4826 be100.bdr04.syd03.nsw.vocus.network (114.31.192.45) 0.0% 6 197.5 197.5 197.4 197.5 0.0

  2. AS4826 static-74.173.255.49.in-addr.VOCUS.net.au (49.255.173.74) 0.0% 6 200.2 200.7 197.4 205.2 3.0

  3. AS20940 a23-1-240-228.deploy.static.akamaitechnologies.com (23.1.240.228) 0.0% 6 197.1 197.3 197.1 197.6 0.2

  4. ???

  5. AS4826 static-73.173.255.49.in-addr.VOCUS.net.au (49.255.173.73) 0.0% 6 197.5 197.6 197.5 197.8 0.1

  6. AS4826 be114.cor02.syd04.nsw.vocus.network (114.31.192.44) 0.0% 6 348.7 349.0 348.7 349.4 0.3

  7. AS4826 be202.bdr03.sjc01.ca.us.vocus.network (114.31.199.43) 0.0% 6 349.0 349.1 348.9 349.3 0.1

  8. AS3257 173.205.35.1 (173.205.35.1) 0.0% 6 348.8 351.0 348.6 362.1 5.4

  9. AS3257 ae18-3416.cr11-fra2.ip4.gtt.net (89.149.180.134) 0.0% 6 356.0 350.5 349.1 356.0 2.7

  10. AS3257 ip4.gtt.net (98.124.180.42) 0.0% 6 348.9 349.0 348.9 349.2 0.1

  11. AS20940 ae12.r01.sjc01.icn.netarch.akamai.com (23.207.232.36) 0.0% 6 368.5 353.4 349.3 368.5 8.4

  12. AS20940 ae11.r01.ord01.icn.netarch.akamai.com (23.32.63.46) 0.0% 6 393.7 393.8 393.7 394.1 0.2

  13. AS20940 ae6.r02.iad01.icn.netarch.akamai.com (23.32.63.21) 0.0% 6 411.4 411.8 411.4 412.4 0.5

  14. AS20940 ae2.r12.iad01.ien.netarch.akamai.com (23.203.152.41) 0.0% 6 411.9 415.1 411.9 417.4 2.9

AS20940 ae2.r11.iad01.ien.netarch.akamai.com (23.203.152.39)

  1. ???

  2. AS33905 a184-25-179-132.deploy.static.akamaitechnologies.com (184.25.179.132) 0.0% 6 215.9 216.4 215.9 216.7 0.3

2

* ESundberg@nitelusa.com (Erik Sundberg) [Wed 24 Nov 2021, 20:57 CET]:

We are receiving latency complaints to Salesforce, anyone else seeing this?

[...]

dig force.com +short

force.com sends an immediate HTTP redirect to www.force.com. You should look up that hostname instead, and ideally you should have Salesforce customers file tickets with Salesforce, since they're in the best position to debug their web app that undoubtedly pulls in content from many different hostnames.

  -- Niels.