User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Travel
Is fireTMS down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → firetms.com—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses. Every report with a known place can appear on the map. Updates every minute.
What's broken
Recent reports
Each row is a time, a coarse place, and a problem type from a new report. Optional notes stay private. Places with fewer than 3 reports in the last 8 days are shown without a location.
No public reports yet.
Our checks
Reaching it
Last checked 1 hr ago. Last stored result reached it in 102 ms.
Official status
All clear
No active incidents in the official feed Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 7 | 0 | 0.0 | 776 ms | 0 |
| Nov 7 | 0 | 0.0 | 137 ms | 0 |
| Nov 8 | 0 | 0.0 | 152 ms | 0 |
| Nov 8 | 0 | 0.0 | 136 ms | 0 |
| Nov 8 | 0 | 0.0 | 177 ms | 0 |
| Nov 8 | 0 | 0.0 | 649 ms | 0 |
| Nov 9 | 0 | 0.0 | 806 ms | 0 |
| Nov 9 | 0 | 0.0 | 130 ms | 0 |
| Nov 9 | 0 | 0.0 | 189 ms | 0 |
| Nov 9 | 0 | 0.0 | 607 ms | 0 |
| Nov 10 | 0 | 0.0 | 127 ms | 0 |
| Nov 10 | 0 | 0.0 | 123 ms | 0 |
| Nov 10 | 0 | 0.0 | 200 ms | 0 |
| Nov 10 | 0 | 0.0 | 193 ms | 0 |
| Nov 11 | 0 | 0.0 | 198 ms | 0 |
| Nov 11 | 0 | 0.0 | 194 ms | 0 |
| Nov 11 | 0 | 0.0 | 182 ms | 0 |
| Nov 11 | 0 | 0.0 | 251 ms | 0 |
| Nov 12 | 0 | 0.0 | 653 ms | 0 |
| Nov 12 | 0 | 0.0 | 125 ms | 0 |
| Nov 12 | 0 | 0.0 | 226 ms | 0 |
| Nov 12 | 0 | 0.0 | 647 ms | 0 |
| Nov 13 | 0 | 0.0 | 692 ms | 0 |
| Nov 13 | 0 | 0.0 | 141 ms | 0 |
| Nov 13 | 0 | 0.0 | 138 ms | 0 |
| Nov 13 | 0 | 0.0 | 172 ms | 0 |
Reliability
100% uptime · No user reports in the last 24h
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 7 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live fireTMS badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for fireTMS yet. Outages of 10 minutes or more get their own page here.
Having trouble with fireTMS?
One report per service every 10 minutes from this network. No account.
Follow fireTMS
Get an email when fireTMS goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send fireTMS alerts to Slack, Discord or a webhook — free.
About fireTMS
fireTMS is listed in our Travel category and checked at firetms.com. fireTMS is a transport management system for carriers and forwarders. Orders, invoicing, payments, reports, GPS integration. Test it for free!
fireTMS publishes an official status page at status.firetms.com; when we can read it, its incident level is folded into the status shown here.
Typical issues with travel services: booking and check-in failures, flight-status pages not loading, and app errors.
Measured uptime from our checks: 100% over 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 281 ms average, 91–750 ms range across 13 successful checks.
Questions
Is fireTMS down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was fireTMS last down?
We have not recorded a public fireTMS incident since monitoring began 7 days ago.
What is fireTMS's uptime?
From our own checks: 100% over 7 days of checks.
How fast does fireTMS respond?
281 ms on average over the last 24 hours (91–750 ms).
Does fireTMS have an official status page?
Yes, at https://status.firetms.com.
fireTMS not working for me but the status is fine. What now?
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For travel services, watch for booking and check-in failures, flight-status pages not loading, and app errors. If many people report fireTMS here at once, the problem is on fireTMS's side.
How we detect and verify outages · Dispute this report · We review disputes within 24 hours.
Community comments
Share what you are seeing with fireTMS. No account needed. Comments are public, separate from outage reports. Do not include personal information.
No links or domains. 3 comments per service and 6 total per hour, per device and network. New contributors get one visible comment; further comments wait for review.