User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Productivity
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 35 min ago. Last stored result reached it in 950 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 12 | 0 | 0.0 | 880 ms | 0 |
| Tue 15 | 0 | 0.0 | 966 ms | 0 |
| Tue 17 | 0 | 0.0 | 994 ms | 0 |
| Tue 19 | 0 | 0.0 | 988 ms | 0 |
| Tue 21 | 0 | 0.0 | 869 ms | 0 |
| Wed 00 | 0 | 0.0 | 852 ms | 0 |
| Wed 02 | 0 | 0.0 | 889 ms | 0 |
| Wed 04 | 0 | 0.0 | 907 ms | 0 |
| Wed 06 | 0 | 0.0 | 857 ms | 0 |
| Wed 09 | 0 | 0.0 | 829 ms | 0 |
| Wed 11 | 0 | 0.0 | 891 ms | 0 |
| Wed 13 | 0 | 0.0 | 874 ms | 0 |
| Wed 15 | 0 | 0.0 | 958 ms | 0 |
| Wed 17 | 0 | 0.0 | 870 ms | 0 |
| Wed 20 | 0 | 0.0 | 1137 ms | 0 |
| Wed 22 | 0 | 0.0 | 865 ms | 0 |
| Thu 00 | 0 | 0.0 | 843 ms | 0 |
| Thu 02 | 0 | 0.0 | 964 ms | 0 |
| Thu 04 | 0 | 0.0 | 1035 ms | 0 |
| Thu 06 | 0 | 0.0 | 939 ms | 0 |
| Thu 08 | 0 | 0.0 | 872 ms | 0 |
| Thu 10 | 0 | 0.0 | 868 ms | 0 |
| Thu 12 | 0 | 0.0 | 906 ms | 0 |
| Thu 14 | 0 | 0.0 | 867 ms | 0 |
| Thu 16 | 0 | 0.0 | 951 ms | 0 |
| Thu 19 | 0 | 0.0 | 988 ms | 0 |
| Thu 21 | 0 | 0.0 | 782 ms | 0 |
| Thu 23 | 0 | 0.0 | 827 ms | 0 |
| Fri 01 | 0 | 0.0 | 865 ms | 0 |
| Fri 03 | 0 | 0.0 | 948 ms | 0 |
| Fri 05 | 0 | 0.0 | 887 ms | 0 |
| Fri 06 | 0 | 0.0 | 917 ms | 0 |
| Fri 08 | 0 | 0.0 | 989 ms | 0 |
| Fri 10 | 0 | 0.0 | 944 ms | 0 |
| Fri 12 | 0 | 0.0 | 990 ms | 0 |
| Fri 14 | 0 | 0.0 | 1121 ms | 0 |
| Fri 16 | 0 | 0.0 | 945 ms | 0 |
| Fri 18 | 0 | 0.0 | 777 ms | 0 |
| Fri 20 | 0 | 0.0 | 875 ms | 0 |
| Fri 22 | 0 | 0.0 | 916 ms | 0 |
| Sat 00 | 0 | 0.0 | 952 ms | 0 |
| Sat 02 | 0 | 0.0 | 849 ms | 0 |
| Sat 04 | 0 | 0.0 | 946 ms | 0 |
| Sat 06 | 0 | 0.0 | 992 ms | 0 |
| Sat 08 | 0 | 0.0 | 947 ms | 0 |
| Sat 10 | 0 | 0.0 | 892 ms | 0 |
| Sat 11 | 0 | 0.0 | 825 ms | 0 |
| Sat 14 | 0 | 0.0 | 950 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 GTMaritime 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 GTMaritime goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send GTMaritime alerts to Slack, Discord or a webhook — free.
We track GTMaritime (gtmaritime.com) as part of the Productivity group. GTMaritime, the Leading Experts in Secure Maritime Solutions with industry leading Maritime Email product GTMailPlus.
GTMaritime publishes an official status page at status.gtmaritime.com; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with productivity services: files not syncing, editors not loading, and sign-in problems.
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: 909 ms average, 777–992 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 GTMaritime incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
909 ms on average over the last 24 hours (777–992 ms).
Yes, at https://status.gtmaritime.com.
It is usually local: try another browser or the app, switch between Wi-Fi and mobile data, and clear the cache. For productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report GTMaritime here at once, the problem is on GTMaritime'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 GTMaritime. 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.