Sentry CDN is slow in Japan

1

Hello !

I’m willing to use a CDN-based Sentry SDK, but yours is quite slow in Japan (at least 200ms wait time when already fetched) - is it possible to improve it on your side ? Otherwise I’ll just host it on ours (Cloudflare), but it is less convenient to upgrade.

See:

DNS resolution: 0 ms
Connecting: 163 ms
TLS setup: 207 ms
Sending: 0 ms
Waiting: 146 ms
Receiving: 133 ms

Thanks !

2

Hey PuKoren, the CDN we use is Fastly, who supposedly have 3 different POPs in Tokyo.

Can you run their diagnostic stuff here? https://www.fastly-debug.com/

And I can forward along to their support. It sounds like you have a bad route to them, if it’s taking ~200ms just to connect to an edge server.

3

Thanks for your answer !

Indeed, there may be an issue. On the debugging tool they provide the RTT is between 140 and 180ms.
It connects to SJC datacenter (151.101.40.64) which is in USA, San Jose.

Here is the debugging token:

ewogICJnZW9pcCI6IHsKICAgICJjaSI6ICJzaGlidXlhIiwKICAgICJzdCI6ICIxMyIsCiAgICAiY3QiOiAiamFwYW4iLAogICAgImNvIjogIkFTIiwKICAgICJjX2lwIjogIjExNS4xNzkuODAuMTAyIiwKICAgICJjX2FzbiI6ICIyNTE5IiwKICAgICJjX2Fzbl9uYW1lIjogInZlY3RhbnQgbHRkLiIsCiAgICAicl9pcCI6ICIxNjMuMTM5LjIzMC4xNzciLAogICAgInJfYXNuIjogIjI1MTkiLAogICAgInJfYXNuX25hbWUiOiAidmVjdGFudCBsdGQuIiwKICAgICJyX2NpIjogImhhbmFtaWdhd2EiLAogICAgInJfc3QiOiAiMTIiLAogICAgInJfY3QiOiAiamFwYW4iLAogICAgInJfY28iOiAiQVMiCiAgfSwKICAicG9wTGF0ZW5jeSI6IHsKICAgICJucnQiOiAzNSwKICAgICJpdG0iOiA0MCwKICAgICJ0eW8iOiAzMywKICAgICJobmQiOiA1MSwKICAgICJoa2ciOiA4NiwKICAgICJzaW4iOiAxMTYsCiAgICAiYm9tIjogMTYyLAogICAgIm1hYSI6IDI3NiwKICAgICJmanIiOiAzMTQsCiAgICAibGF4IjogMTY0LAogICAgImZyYSI6IDI4NSwKICAgICJhbnkiOiAxNDQKICB9LAogICJwb3BBc3NpZ25tZW50cyI6IHsKICAgICJhYyI6ICJzamMiLAogICAgImFzIjogInNqYyIKICB9LAogICJyZXF1ZXN0IjogewogICAgInJlc29sdmVyX2lwIjogIjE2My4xMzkuMjMwLjE3NiIsCiAgICAicmVzb2x2ZXJfYXNfbmFtZSI6ICJWRUNUQU5UIEFSVEVSSUEgTmV0d29ya3MgQ29ycG9yYXRpb24sIEpQIiwKICAgICJyZXNvbHZlcl9hc19udW1iZXIiOiAiMjUxOSIsCiAgICAicmVzb2x2ZXJfY291bnRyeV9jb2RlIjogIkpQIiwKICAgICJjbGllbnRfaXAiOiAiMTE1LjE3OS44MC4xMDIiLAogICAgImNsaWVudF9hc19uYW1lIjogIlZFQ1RBTlQgQVJURVJJQSBOZXR3b3JrcyBDb3Jwb3JhdGlvbiwgSlAiLAogICAgImNsaWVudF9hc19udW1iZXIiOiAiMjUxOSIsCiAgICAidGltZSI6ICIyMDE5LTA1LTIyVDA1OjA4OjUxLjAwMFoiLAogICAgImhvc3QiOiAid3d3LmZhc3RseS1kZWJ1Zy5jb20iLAogICAgImFjY2VwdCI6ICJ0ZXh0L2h0bWwsYXBwbGljYXRpb24veGh0bWwreG1sLGFwcGxpY2F0aW9uL3htbDtxPTAuOSwqLyo7cT0wLjgiLAogICAgInVzZXJhZ2VudCI6ICJNb3ppbGxhLzUuMCAoWDExOyBMaW51eCB4ODZfNjQ7IHJ2OjY2LjApIEdlY2tvLzIwMTAwMTAxIEZpcmVmb3gvNjYuMCIsCiAgICAiYWNjZXB0bGFuZ3VhZ2UiOiAiZW4tVVMsZW47cT0wLjUiLAogICAgImFjY2VwdGVuY29kaW5nIjogImd6aXAiLAogICAgImZhc3RseXNlcnZlcmlwIjogIjE1MS4xMDEuNDAuNjQiLAogICAgInhmZiI6ICIxMTUuMTc5LjgwLjEwMiIsCiAgICAiZGF0YWNlbnRlciI6ICJTSkMiLAogICAgImJhbmR3aWR0aF9tYnBzIjogIjUuNDMiLAogICAgImN3bmQiOiAzNjgsCiAgICAibmV4dGhvcCI6ICIxNzIuMTYuNTQuNCIsCiAgICAicnR0IjogMTQ3LjEzNSwKICAgICJkZWx0YV9yZXRyYW5zIjogMCwKICAgICJ0b3RhbF9yZXRyYW5zIjogMAogIH0KfQ==

Thanks

4

Hi @PuKoren,

Could you run an MTR (https://docs.fastly.com/guides/debugging/debugging-with-mtr) or “traceroute” on the hostname you’re trying to reach?
E.g.
mtr -c 20 -w -r browser.sentry-cdn.com
or
traceroute browser.sentry-cdn.com

Fastly needs this information to get a better idea of what’s going on.

5

Thanks for your answer @tonyo

It looks fixed today,

Here are the results of the commands:

[koren:~]$ mtr -c 20 -w -r browser.sentry-cdn.com
Start: 2019-05-24T04:04:38+0200
HOST: korentop                           Loss%   Snt   Last   Avg  Best  Wrst StDev
  1.|-- _gateway                            0.0%    20    7.7   9.5   3.9  15.9   3.2
  2.|-- Tok2GFM1.vectant.ne.jp              0.0%    20   28.6  36.6  16.6  47.9   8.1
  3.|-- d245.GtokyoFL24.vectant.ne.jp       0.0%    20   26.7  38.1  25.6  50.3   7.6
  4.|-- 163-139-68-49.rv.vectant.ne.jp      0.0%    20   24.0  37.0  23.9  53.0   9.1
  5.|-- ae1.peer3.nihonbashi.vectant.ne.jp  0.0%    20   17.9  35.3  17.9  48.5   7.2
  6.|-- 218.100.7.48                       55.0%    20   30.2  40.9  30.2  54.9   8.2
  7.|-- 151.101.2.217                       0.0%    20   27.7  39.0  20.5  56.2   9.3

 traceroute browser.sentry-cdn.com
traceroute to browser.sentry-cdn.com (151.101.2.217), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.1)  6.295 ms  6.238 ms  6.194 ms
 2  Tok2GFM1.vectant.ne.jp (163.139.100.147)  40.095 ms  40.103 ms  40.064 ms
 3  d245.GtokyoFL24.vectant.ne.jp (163.139.155.245)  47.668 ms  47.659 ms  47.619 ms
 4  163-139-68-49.rv.vectant.ne.jp (163.139.68.49)  47.602 ms  47.564 ms  47.524 ms
 5  ae0.peer3.nihonbashi.vectant.ne.jp (163.139.128.190)  47.444 ms ae1.peer3.nihonbashi.vectant.ne.jp (163.139.128.194)  47.405 ms  47.366 ms

If I see another slow down I will post the results here again.

Thanks