RDS + SalesForce.com = whatever but love

De miercuri, 25 Iulie, conexiunea dintre RDS si SalesForce.com e borken undeva pe la mijloc.


Host Loss % Snt Last Avg Best Wrst StDev
3 bb01.bucuresti.rdsnet.ro 0.00% 4 9 10.1 9 12 1.3
4 213-154-125-62.rdsnet.ro 0.00% 4 42.8 42 41.6 42.8 0.5
5 xr01.frankfurt.rdsnet.ro 0.00% 4 42.3 42.1 41.8 42.3 0.2
6 xr01.londra.rdsnet.ro 0.00% 4 59.4 58.2 57.7 59.4 0.8
7 ge3-0.pr1.lhr1.uk.above.net 0.00% 4 57.7 58.1 57.5 59.1 0.7
8 so-7-0-0.cr1.dca2.us.above.net 0.00% 4 133.2 136.7 130.8 142.1 5.5
9 so-4-0-0.mpr2.atl6.us.above.net 0.00% 4 144.5 144.5 143.8 145.2 0.6
10 so-0-0-0.mpr1.atl6.us.above.net 0.00% 4 143.6 143.7 143.6 143.8 0.1
11 so-1-2-1.mpr4.iah1.us.above.net 0.00% 4 157.2 161.8 157.2 170 5.7
12 so-0-0-0.mpr3.iah1.us.above.net 0.00% 4 185.2 168.4 156 185.2 14.3
13 64.125.25.18.available.above.net 0.00% 4 189.1 189.9 189.1 191.2 0.9
14 so-0-1-0.mpr2.sjc2.us.above.net 0.00% 4 205.5 201.4 198.7 205.5 3.1
15 ???







Efectul? Clientii SalesForce.com ce au drept provider RDS platesc niste banii degeaba, nebeneficiind de serviciile SalesForce.com gratie unor provideri inteligenti.

RDS a fost notificat joi si vineri de aceasta problema, in asteptarea unei rezolutii de genul "am schimbat ruta catre X prin Y".

Luni, orele 17:41 situatia este neschimbata.

Deoarece avem clienti ce folosesc Salesforce.com si (inca) RDS, solutia adoptata pe moment a fost redirectarea traficului lor http/https prin noi, folosind o conexiune de backup a noastra.