Announcement

Collapse
No announcement yet.

What is your ping time to api.betfair.com?

Collapse
X
Collapse
 
  • Page of 3
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 template Next
  • #1

    What is your ping time to api.betfair.com?

    The api.betfair.com servers don't respond to regular ping requests, but Microsoft have a special PsPing utility which can do a "TCP ping". This utility can be downloaded from here:

    http://technet.microsoft.com/en-us/s...rnals/jj729731

    To measure the latency, the following command can be used:

    Code:
    psping -n 20 api.betfair.com:443
    On my Windows 7 machine here in Copenhagen, the command above gives me the following output:

    Code:
    TCP connect statistics for 84.20.200.10:443:
  Sent = 20, Received = 20, Lost = 0 (0% loss),
  Minimum = 48.64ms, Maximum = 61.56ms, Average = 51.09ms
    What kind of latency do you get? And where is your approximate location?
    Tags: None
  • #2
    On a Windows Server 2012 R2 virtual machine in the Windows Azure cloud in "North Europe", i.e. Ireland, I get the following response:

    Code:
    TCP connect statistics for 84.20.200.10:443:
  Sent = 20, Received = 20, Lost = 0 (0% loss),
  Minimum = 29.71ms, Maximum = 36.30ms, Average = 31.08ms
    Since the Betfair servers are in Dublin, this should be pretty close. But perhaps some cloud providers are even closer? What about Amazon AWS, they should also have a data center in Ireland?

    Comment

    • #3
      Code:
      TCP connect statistics for 84.20.200.10:443:
  Sent = 20, Received = 20, Lost = 0 (0% loss),
  Minimum = 13.99ms, Maximum = 15.79ms, Average = 14.73ms
      If you want more luck... Take more chances!

      Comment

      • #4
        Originally posted by Cran View Post
        Code:
        TCP connect statistics for 84.20.200.10:443:
  Sent = 20, Received = 20, Lost = 0 (0% loss),
  Minimum = 13.99ms, Maximum = 15.79ms, Average = 14.73ms
        Yeah, that sounds more proper. Is that from Basel or from a VPS somewhere?

        Comment

        • #5
          Originally posted by dude67 View Post
          Yeah, that sounds more proper. Is that from Basel or from a VPS somewhere?
          That's the Tagadab VPS that my bot runs on, It's up north somewhere.

          My Basel ping is average 48ms.
          If you want more luck... Take more chances!

          Comment

          • #6
            Originally posted by Cran View Post
            That's the Tagadab VPS that my bot runs on, It's up north somewhere.

            My Basel ping is average 48ms.
            Does this mean your VPS is faster for you? I always thought they were slower as it was another destination for the info to travel to. I'm not that clued in with technology to be honest, I can't get my ping test to work.

            Comment

            • #7
              TCP connect statistics for 84.20.200.10:443:
              Sent = 20, Received = 20, Lost = 0 (0% loss),
              Minimum = 28.66ms, Maximum = 167.24ms, Average = 43.00ms

              Comment

              • #8
                when I double click psping.exe it opens and then just closes.

                Comment

                • #9
                  Originally posted by lcredd View Post
                  when I double click psping.exe it opens and then just closes.
                  Your computer is probably close to exploding then.

                  What you describe is a classic pre-bang symptom.

                  Comment

                  • #10
                    You were right, damn it!

                    <sent from my google glasses>

                    Comment

                    • #11
                      Originally posted by lcredd View Post
                      Does this mean your VPS is faster for you? I always thought they were slower as it was another destination for the info to travel to. I'm not that clued in with technology to be honest, I can't get my ping test to work.
                      My bot is running on the VPS and what it does is automatic, there is no live input required from me, so there is no additional delay.

                      If you run an interactive API program (e.g. TheToy) on a VPS there will be additional delay because the info from Betfair still has to get from the VPS to your screen and then your mouse/keyboard input has to get sent to the VPS before anything goes to Betfair.

                      copy pstest.exe to the c:/windows/system32 folder and run it from the command line:

                      Click start
                      Type: cmd[enter]
                      in the command window that opens type psping -n 20 api.betfair.com:443
                      If you want more luck... Take more chances!

                      Comment

                      • #12
                        From a computer at my workplace (in Copenhagen), connected to the Internet via WiFi.

                        Code:
                        TCP connect statistics for 84.20.200.10:443:
  Sent = 20, Received = 20, Lost = 0 (0% loss),
  Minimum = 36.79ms, Maximum = 37.70ms, Average = 37.10ms

                        Comment

                        • #13
                          Originally posted by doubleback View Post
                          TCP connect statistics for 84.20.200.10:443:
                          Sent = 20, Received = 20, Lost = 0 (0% loss),
                          Minimum = 28.66ms, Maximum = 167.24ms, Average = 43.00ms
                          That's a lot of variance! But a good minimum value.

                          Are you using WiFi? Where is your computer located geographically?

                          Comment

                          • #14
                            Originally posted by dude67 View Post
                            That's a lot of variance! But a good minimum value.

                            Are you using WiFi? Where is your computer located geographically?
                            Yes, that was wireless. I ran the test again plugged in...

                            [London, btw]

                            Code:
                            TCP connect to 84.20.200.10:443:
21 iterations (warmup 1) connecting test:
Connecting to 84.20.200.10:443 (warmup): 30.02ms
Connecting to 84.20.200.10:443: 29.63ms
Connecting to 84.20.200.10:443: 28.65ms
Connecting to 84.20.200.10:443: 29.65ms
Connecting to 84.20.200.10:443: 28.66ms
Connecting to 84.20.200.10:443: 28.70ms
Connecting to 84.20.200.10:443: 29.66ms
Connecting to 84.20.200.10:443: 29.61ms
Connecting to 84.20.200.10:443: 29.63ms
Connecting to 84.20.200.10:443: 29.67ms
Connecting to 84.20.200.10:443: 28.65ms
Connecting to 84.20.200.10:443: 29.62ms
Connecting to 84.20.200.10:443: 28.56ms
Connecting to 84.20.200.10:443: 29.63ms
Connecting to 84.20.200.10:443: 29.66ms
Connecting to 84.20.200.10:443: 28.61ms
Connecting to 84.20.200.10:443: 28.63ms
Connecting to 84.20.200.10:443: 29.65ms
Connecting to 84.20.200.10:443: 29.66ms
Connecting to 84.20.200.10:443: 29.62ms
Connecting to 84.20.200.10:443: 29.64ms

TCP connect statistics for 84.20.200.10:443:
  Sent = 20, Received = 20, Lost = 0 (0% loss),
  Minimum = 28.56ms, Maximum = 29.67ms, Average = 29.29ms

                            Comment

                            • #15
                              TCP connect to 84.20.200.10:443:
                              21 iterations (warmup 1) connecting test:
                              Connecting to 84.20.200.10:443 (warmup): 28.57ms
                              Connecting to 84.20.200.10:443: 28.03ms
                              Connecting to 84.20.200.10:443: 28.58ms
                              Connecting to 84.20.200.10:443: 28.67ms
                              Connecting to 84.20.200.10:443: 29.37ms
                              Connecting to 84.20.200.10:443: 28.57ms
                              Connecting to 84.20.200.10:443: 28.64ms
                              Connecting to 84.20.200.10:443: 27.14ms
                              Connecting to 84.20.200.10:443: 27.81ms
                              Connecting to 84.20.200.10:443: 27.70ms
                              Connecting to 84.20.200.10:443: 27.76ms
                              Connecting to 84.20.200.10:443: 30.29ms
                              Connecting to 84.20.200.10:443: 28.21ms
                              Connecting to 84.20.200.10:443: 28.07ms
                              Connecting to 84.20.200.10:443: 28.20ms
                              Connecting to 84.20.200.10:443: 28.16ms
                              Connecting to 84.20.200.10:443: 28.01ms
                              Connecting to 84.20.200.10:443: 28.79ms
                              Connecting to 84.20.200.10:443: 29.04ms
                              Connecting to 84.20.200.10:443: 27.84ms
                              Connecting to 84.20.200.10:443: 28.56ms

                              TCP connect statistics for 84.20.200.10:443:
                              Sent = 20, Received = 20, Lost = 0 (0% loss),
                              Minimum = 27.14ms, Maximum = 30.29ms, Average = 28.37ms
                              Location: The Netherlands

                              Comment

                              Previous 1 2 3 template Next
                              Working...
                              X