If you manage a fleet of vehicles, you know the feeling. You open your tracking app, expecting to see your trucks on the map, and the screen is blank. No positions. No updates. Nothing.

Your first instinct: check the device. Then the SIM card. Then the network. You call your driver. You restart the app. You check your internet connection. Ten minutes later, you still don't know if the problem is on your end or on the platform's.

That uncertainty is the real problem. Not the downtime itself, but the silence around it.

Most GPS tracking providers don't publish their uptime. When something breaks, you find out the hard way. There is no status page, no incident log, no way to tell if the issue is yours or theirs. You are left guessing.

Introducing status.traxelio.com

We built a public, real-time status page at status.traxelio.com so you never have to guess again.

The page monitors 19 endpoints across four groups, each checked at intervals that match their importance:

Group What It Covers Check Interval
Core Website, app, health check Every 60 seconds
Marketing Pricing, demo, blog, contact, enterprise, login Every 120 seconds
Pages Trackers, features, industries, locations, guides, glossary, sitemap Every 5 minutes
DNS traxelio.com, app.traxelio.com, status.traxelio.com Every 5 minutes

If something goes down, you will see it on the status page before you even notice it in the app. The page shows current status, response times, and uptime history so you can see exactly how reliable the platform has been over time.

The status page is powered by Uptime Kuma, an open-source, self-hosted monitoring tool. No third-party SaaS dependency for something this critical.

How It Works Behind the Scenes

The status page runs on a dedicated EC2 instance, completely separate from the main Traxelio application. This matters because if the app goes down, the status page stays up. You can still check what is happening even during an outage.

Here is what the infrastructure looks like:

  • Isolated hosting: the monitoring server is independent from the application servers. One can fail without taking the other down.
  • Automated provisioning: monitors and the status page are created via script on every deploy. No manual configuration to forget or misconfigure.
  • Daily encrypted backups: the monitoring database is backed up to S3 every day, encrypted at rest.
  • Custom user agent (TraxelioUptimeKuma/1.0): monitoring traffic is tagged so it gets excluded from analytics. Our uptime checks don't inflate your visit counts.
  • Cloudflare bypass header (X-Uptime-Monitor): a custom header ensures monitoring requests pass through Cloudflare protection without triggering bot detection. The checks measure real availability, not Cloudflare challenge pages.

What This Means for You

You can self-diagnose. Before opening a support ticket, check the status page. If all services show green, the issue is likely on your end (device, SIM, network). If something shows red, we already know about it and are working on it.

You get transparency, not promises. Anyone can claim 99.9% uptime. We publish ours. The status page is a public record that holds us accountable. If we have a bad day, it shows.

You save time. No more back-and-forth emails asking "is the platform down?" The answer is always one click away.

Most GPS tracking providers in our market don't offer a public status page. Enterprise SaaS companies like Stripe, GitHub, and AWS do. We believe fleet managers deserve the same level of transparency, regardless of the size of their fleet or the price of their plan.

We built Traxelio to be the kind of service we would want to use ourselves. That means being honest about our uptime, transparent about incidents, and proactive about giving you the tools to stay informed.

Check it out at status.traxelio.com. If you have questions or feedback, reach out to us.