User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Travel
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 42 min ago. Last stored result reached it in 1248 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 00 | 0 | 0.0 | 1117 ms | 0 |
| Tue 02 | 0 | 0.0 | 1154 ms | 0 |
| Tue 05 | 0 | 0.0 | 1193 ms | 0 |
| Tue 07 | 0 | 0.0 | 1004 ms | 0 |
| Tue 09 | 0 | 0.0 | 1229 ms | 0 |
| Tue 11 | 0 | 0.0 | 997 ms | 0 |
| Tue 13 | 0 | 0.0 | 1134 ms | 0 |
| Tue 15 | 0 | 0.0 | 1331 ms | 0 |
| Tue 18 | 0 | 0.0 | 919 ms | 0 |
| Tue 20 | 0 | 0.0 | 1239 ms | 0 |
| Tue 22 | 0 | 0.0 | 1187 ms | 0 |
| Wed 00 | 0 | 0.0 | 1186 ms | 0 |
| Wed 03 | 0 | 0.0 | 1285 ms | 0 |
| Wed 05 | 0 | 0.0 | 734 ms | 0 |
| Wed 07 | 0 | 0.0 | 1047 ms | 0 |
| Wed 09 | 0 | 0.0 | 1205 ms | 0 |
| Wed 12 | 0 | 0.0 | 1004 ms | 0 |
| Wed 14 | 0 | 0.0 | 1166 ms | 0 |
| Wed 16 | 0 | 0.0 | 1385 ms | 0 |
| Wed 18 | 0 | 0.0 | 928 ms | 0 |
| Wed 20 | 0 | 0.0 | 1019 ms | 0 |
| Wed 22 | 0 | 0.0 | 885 ms | 0 |
| Thu 00 | 0 | 0.0 | 1156 ms | 0 |
| Thu 03 | 0 | 0.0 | 695 ms | 0 |
| Thu 05 | 0 | 0.0 | 1350 ms | 0 |
| Thu 07 | 0 | 0.0 | 1115 ms | 0 |
| Thu 09 | 0 | 0.0 | 1373 ms | 0 |
| Thu 11 | 0 | 0.0 | 746 ms | 0 |
| Thu 13 | 0 | 0.0 | 682 ms | 0 |
| Thu 15 | 0 | 0.0 | 894 ms | 0 |
| Thu 17 | 0 | 0.0 | 717 ms | 0 |
| Thu 19 | 0 | 0.0 | 1346 ms | 0 |
| Thu 21 | 0 | 0.0 | 1388 ms | 0 |
| Thu 23 | 0 | 0.0 | 1294 ms | 0 |
| Fri 01 | 0 | 0.0 | 1298 ms | 0 |
| Fri 03 | 0 | 0.0 | 1218 ms | 0 |
| Fri 04 | 0 | 0.0 | 730 ms | 0 |
| Fri 06 | 0 | 0.0 | 1146 ms | 0 |
| Fri 08 | 0 | 0.0 | 848 ms | 0 |
| Fri 10 | 0 | 0.0 | 1039 ms | 0 |
| Fri 11 | 0 | 0.0 | 1060 ms | 0 |
| Fri 13 | 0 | 0.0 | 926 ms | 0 |
| Fri 15 | 0 | 0.0 | 1161 ms | 0 |
| Fri 17 | 0 | 0.0 | 1527 ms | 0 |
| Fri 18 | 0 | 0.0 | 1271 ms | 0 |
| Fri 20 | 0 | 0.0 | 1432 ms | 0 |
| Fri 22 | 0 | 0.0 | 1154 ms | 0 |
| Sat 00 | 0 | 0.0 | 1248 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 9 days of data so far, so the 90-day numbers fill in over time.
No outages on record for AddSecure - Co-Driver 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 AddSecure - Co-Driver goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send AddSecure - Co-Driver alerts to Slack, Discord or a webhook — free.
AddSecure - Co-Driver, at codriver.com, is one of the Travel services we monitor. CoDriver brings telematics, video, compliance, transport-management integrations and fleet intelligence together in one connected ecosystem.
AddSecure - Co-Driver publishes an official status page at status.codriver.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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 1159 ms average, 730–1527 ms range across 16 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public AddSecure - Co-Driver incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
1159 ms on average over the last 24 hours (730–1527 ms).
Yes, at https://status.codriver.com.
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 AddSecure - Co-Driver here at once, the problem is on AddSecure - Co-Driver'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 AddSecure - Co-Driver. 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.