He has worked for Sygic as a marketer and co-led the implementation and development of a product acquired from a competitor. He has also worked as a freelance developer, helping clients from various areas.
Tomas brings a wealth of industry experience to our team. He spent a few years in the blockchain industry, leading projects and marketing teams at multiple blockchain-based companies. He has presented products and managed deals in more than 10 countries around the world, managed the ICO, and built a successful marketing team at Fuergy that continues to thrive.
Tomas managed a product team for the biggest job site in Slovakia, covering development and transformation to a new B2B app.
Not only is Tomas skilled at web development, but he also has a deep understanding of SaaS businesses, which makes him an invaluable asset in shaping and leading various projects at UptimeRobot. His focus is always on the continual improvement of our service and user experience.
In addition to his professional achievements, Tomas is a devoted father. His personal interests include cycling (he traveled around the whole country of Slovakia), playing guitar (he even played in a band), servicing bikes, music, and enjoying good beer.
Tip: While using Uptime Robot until now, if you didn't need to do anything with the IPs of the service, then feel free to skip this post. Actually 99.9% of the users don't need this info. Around a month ago, we had shared that a new IP was added to our engine to strengthen the […]
In order to make Uptime Robot faster and more stable, a new server is being added to the tiny : ) cluster (3 machines now). If you're using a firewall and had needed to unblock the IPs of the service, than you may want to unblock this new IP as well: 74.86.179.131. Also, it can […]
Today, Uptime Robot adds a new monitor type besides the http(s) and keyword checking: Ping. It is actually the most basic command to find out if a network is up or down. How does it differ from http(s)? Http(s) monitoring sends a request to the web server and, in return, gets a status code from […]
Since the beginning, Uptime Robot was supporting URLs with SSL certificates (https). However, self-signed certificates (the ones with unknown CAs) were not supported as they were generating errors like "unknown certificate", etc. and Uptime Robot was considering these websites to be down. Today, URLs with self-signed certificates are now supported just like any other URL […]
We get many questions regarding "if Uptime Robot will ever become paid or not" and thought it'll be the best to share it in detail. Why Is Uptime Robot Free? We have launched Uptime Robot in January 2010 hoping to offer a non-complicated uptime service (where every website owner actually needs). Also, we had created […]
Since the launch of Uptime Robot, we’re analyzing the cost of keeping logs in means of performance and size. With lots of tweaks to our engine and code, Uptime Robot now saves every action to present them as reports and charts. The first report activated is the “Last 24 Hours Status” which can be found […]
Incident management
Status pages
Integrations
Subscribe