08/29/2026
Groups
Groups you've joined
Recent activity
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Facebook
Run Time Keepers
Greg Stewart ·
Admin
Group expert
All-star contributor
· S͏s͏t͏p͏d͏e͏o͏n͏r͏o͏m͏c͏6͏0͏a͏m͏1͏t͏l͏2͏u͏a͏3͏c͏0͏6͏m͏5͏3͏6͏c͏1͏4͏2͏h͏0͏5͏m͏3͏5͏2͏i͏g͏u͏0͏7͏m͏f͏6͏t͏8͏h͏a͏0͏9͏m͏6͏i͏i͏m͏ ·
From Google: Moving race timing infrastructure to the cloud offers significant advantages in scaling and accessibility, but it introduces distinct risks regarding connectivity and latency. The primary consideration when choosing between cloud and localized race timing is the reliability of your internet connection versus the need for real-time, decentralized data access.
From Orbiter: Thus, Timers know of CLOUD disruptions, and increasing server speed does not solve the problem that internet connections are never reliable.
Orbiter's approach is squarely localized, where the embedded code inside the Reader "is" the race. Thus, offering the greatest reliability and responsiveness, with push to the CLOUD on a FIFO basis providing the best of both worlds. We have consistently been doing this since 1996, and have always upgraded to the most modern C++, Java, and Android tools. Internet Outages will never end so why design the primary timing software to be dependent on the CLOUD? (This proves for Timing, the CLOUD is where you go when you die.)
ThousandEyes monitors network infrastructure, troubleshoots application delivery and maps Internet performance, all from a SaaS-based platform