LogMeIn by the Numbers

It’s been just over 9 years since LogMeIn’s official inception (then called 3am Labs), and almost 8 years since we introduced our signature remote access product, LogMeIn Free.  At the time, if someone were to suggest that one day we’d have tens of millions of users, I’m pretty sure we’d have dismissed them as a dreamer.  As we pass one anniversary and approach another, I thought I’d share some interesting stats about LogMeIn and our users that drive us to dream of even bigger and better things.   Enjoy, thank you, and stay tuned.  The best is yet to come!

LogMeIn by the numbers:

Registered users: over 40,000,000
Application installations: over 190,000,000

Number of computers remotely fixed with LogMeIn Rescue: over 50,000,000
Number of troubleshooting sessions ran with LogMeIn Rescue: over 140,000,000

Number of remote access sessions with LogMeIn Free/Pro: well over 2 billion
Peer to peer data transferred for the above 2bn+ sessions: 22+ petabytes

Join.me screen sharing participants: over 50,000,000

Hamachi peer-to-peer VPN tunnels set up: over 24 billion. Relayed VPN tunnels (where a peer to peer connection was not possible to negotiate) total 4.5 billion.

Hamachi’s peer to peer traffic has been over 71 petabytes, traffic relayed through our datacenters a relatively meager 1.7 PB.

These are pretty impressive numbers, and our operations team did a stellar job at keeping the service humming along. Uptime for the most recent years:

2009: 99.96%
2010: 100%
2011: 99.9939%
2012 YTD: 99.9998%

Ok, there are a few more interesting numbers, but we’ll save those for the tenth anniversary retrospective.

Sandor Palfy

Written by

Sandor is the Chief Technology Officer of the Identity & Access Business Unit at LogMeIn.

2 thoughts on “LogMeIn by the Numbers

  1. Pingback: Remote Access and Remote Desktop Software for Your Computer | LogMeIn | TimBatchelder.com: Clean, Green + Social Technologies

  2. These numbers are great, but borderline incredible. I’m very interested in knowing how they’re produced. For example, do they include scheduled downtime? Did a failure have to occur from all moniotring sites before it’s counted against downtime? Are the numbers independently verified?

Comments are closed.