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.
A status page is a very easy-to-setup, nice and automated way to share the status of the websites/servers with visitors, users and teammates. And, the ability to share additional info with users like current issues or an upcoming maintenance can only make it better. We have just added this feature (in the Pro Plan) where it is […]
Uptime Robot provided 2 api-key types: a master api_key and monitor-specific api_key. The master api_key can be used to perform almost every action exists in the dashboard and it must not be revealed for the security of the accounts. Yet, there are cases where the api_key may needed to be revealed like using it in […]
Caching is a great way to improve website performance and minimize the load. An ideal cache displays the cached version until the content changes and flushes the cache when there is a change. Yet, there may be cases where the cached version is not the most up-to-date one (if there is a DB error on […]
All the requests sent from Uptime Robot are using pre-defined IPs to make sure that we all know the source of the requests. A new IP block is being added to the system: 216.245.221.80/28 And, if exists, please make sure it is whitelisted in your firewalls. Also, the full list of the IPs used can be found here. P.S.> […]
Uptime Robot treats all HTTP statuses equally. They mean either up or down… except HTTP 401. HTTP 401 is expected in some situations and not expected in others. Currently, HTTP 401 is handled as: If auth info is mentioned in monitor’s settings but HTTP 401 is returned, monitor is marked as down if no auth […]
Last Thursday (10 Jan 2019), starting with 02:30, we experienced an issue that caused a full downtime of ~12 hours and intermittent issues more than that afterwards. First of all, so so sorry about this. And, as a summary, it was totally our fault. Uptime Robot is available since Jan 2010 and it is the […]
Incident management
Status pages
Integrations
Subscribe