User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
frotcom.com · Cloud & developer
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
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.
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.
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.
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Reaching it
Last checked 44 min ago. Last stored result reached it in 1448 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 12 | 0 | 0.0 | 1523 ms | 0 |
| Mon 14 | 0 | 0.0 | 1424 ms | 0 |
| Mon 16 | 0 | 0.0 | 1753 ms | 0 |
| Mon 19 | 0 | 0.0 | 1616 ms | 0 |
| Mon 21 | 0 | 0.0 | 1430 ms | 0 |
| Mon 23 | 0 | 0.0 | 1372 ms | 0 |
| Tue 01 | 0 | 0.0 | 1630 ms | 0 |
| Tue 03 | 0 | 0.0 | 1374 ms | 0 |
| Tue 05 | 0 | 0.0 | 1476 ms | 0 |
| Tue 07 | 0 | 0.0 | 1547 ms | 0 |
| Tue 09 | 0 | 0.0 | 1588 ms | 0 |
| Tue 11 | 0 | 0.0 | 1404 ms | 0 |
| Tue 14 | 0 | 0.0 | 1124 ms | 0 |
| Tue 16 | 0 | 0.0 | 1525 ms | 0 |
| Tue 18 | 0 | 0.0 | 1463 ms | 0 |
| Tue 20 | 0 | 0.0 | 1704 ms | 0 |
| Tue 23 | 0 | 0.0 | 1620 ms | 0 |
| Wed 01 | 0 | 0.0 | 1666 ms | 0 |
| Wed 03 | 0 | 0.0 | 1421 ms | 0 |
| Wed 05 | 0 | 0.0 | 1633 ms | 0 |
| Wed 08 | 0 | 0.0 | 1682 ms | 0 |
| Wed 10 | 0 | 0.0 | 1738 ms | 0 |
| Wed 12 | 0 | 0.0 | 1713 ms | 0 |
| Wed 14 | 0 | 0.0 | 1481 ms | 0 |
| Wed 16 | 0 | 0.0 | 1409 ms | 0 |
| Wed 18 | 0 | 0.0 | 1660 ms | 0 |
| Wed 21 | 0 | 0.0 | 1540 ms | 0 |
| Wed 23 | 0 | 0.0 | 1478 ms | 0 |
| Thu 01 | 0 | 0.0 | 1961 ms | 0 |
| Thu 03 | 0 | 0.0 | 1489 ms | 0 |
| Thu 05 | 0 | 0.0 | 1478 ms | 0 |
| Thu 07 | 0 | 0.0 | 1364 ms | 0 |
| Thu 09 | 0 | 0.0 | 1675 ms | 0 |
| Thu 11 | 0 | 0.0 | 1430 ms | 0 |
| Thu 13 | 0 | 0.0 | 1654 ms | 0 |
| Thu 15 | 0 | 0.0 | 1329 ms | 0 |
| Thu 17 | 0 | 0.0 | 1580 ms | 0 |
| Thu 19 | 0 | 0.0 | 1678 ms | 0 |
| Thu 22 | 0 | 0.0 | 1563 ms | 0 |
| Fri 00 | 0 | 0.0 | 1716 ms | 0 |
| Fri 02 | 0 | 0.0 | 1566 ms | 0 |
| Fri 04 | 0 | 0.0 | 1764 ms | 0 |
| Fri 06 | 0 | 0.0 | 1584 ms | 0 |
| Fri 08 | 0 | 0.0 | 1610 ms | 0 |
| Fri 10 | 0 | 0.0 | 1647 ms | 0 |
| Fri 12 | 0 | 0.0 | 1813 ms | 0 |
| Fri 14 | 0 | 0.0 | 1568 ms | 0 |
| Fri 16 | 0 | 0.0 | 1448 ms | 0 |
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.
No outages on record for Frotcom yet. Outages of 10 minutes or more get their own page here.
One report per service every 10 minutes from this network. No account.
Get an email when Frotcom goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Frotcom alerts to Slack, Discord or a webhook — free.
We track Frotcom (frotcom.com) as part of the Cloud & developer group. Frotcom is a leading global provider of intelligent vehicle fleet management and GPS tracking solutions, with a presence in more than 40 countries. Contact us.
Frotcom publishes an official status page at status.frotcom.com; when we can read it, its incident level is folded into the status shown here.
Common problems for cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
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: 1627 ms average, 1448–1813 ms range across 13 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Frotcom incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
1627 ms on average over the last 24 hours (1448–1813 ms).
Yes, at https://status.frotcom.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For cloud & developer services, watch for API errors, failed deploys or builds, and dashboard or console outages. If many people report Frotcom here at once, the problem is on Frotcom'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 Frotcom. 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.