User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
indexmed.com.br · 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 2 hr ago. Last stored result reached it in 854 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Tue 01 | 0 | 0.0 | 1039 ms | 0 |
| Tue 03 | 0 | 0.0 | 1074 ms | 0 |
| Tue 05 | 0 | 0.0 | 1035 ms | 0 |
| Tue 08 | 0 | 0.0 | 1075 ms | 0 |
| Tue 10 | 0 | 0.0 | 1000 ms | 0 |
| Tue 12 | 0 | 0.0 | 958 ms | 0 |
| Tue 14 | 0 | 0.0 | 749 ms | 0 |
| Tue 16 | 0 | 0.0 | 817 ms | 0 |
| Tue 18 | 0 | 0.0 | 1152 ms | 0 |
| Tue 21 | 0 | 0.0 | 1002 ms | 0 |
| Tue 23 | 0 | 0.0 | 1086 ms | 0 |
| Wed 01 | 0 | 0.0 | 1004 ms | 0 |
| Wed 03 | 0 | 0.0 | 1114 ms | 0 |
| Wed 06 | 0 | 0.0 | 1033 ms | 0 |
| Wed 08 | 0 | 0.0 | 1033 ms | 0 |
| Wed 10 | 0 | 0.0 | 1027 ms | 0 |
| Wed 12 | 0 | 0.0 | 1020 ms | 0 |
| Wed 14 | 0 | 0.0 | 768 ms | 0 |
| Wed 16 | 0 | 0.0 | 808 ms | 0 |
| Wed 19 | 0 | 0.0 | 1774 ms | 0 |
| Wed 21 | 0 | 0.0 | 973 ms | 0 |
| Wed 23 | 0 | 0.0 | 959 ms | 0 |
| Thu 01 | 0 | 0.0 | 910 ms | 0 |
| Thu 03 | 0 | 0.0 | 924 ms | 0 |
| Thu 05 | 0 | 0.0 | 937 ms | 0 |
| Thu 07 | 0 | 0.0 | 487 ms | 0 |
| Thu 09 | 0 | 0.0 | 920 ms | 0 |
| Thu 12 | 0 | 0.0 | 1012 ms | 0 |
| Thu 14 | 0 | 0.0 | 992 ms | 0 |
| Thu 16 | 0 | 0.0 | 943 ms | 0 |
| Thu 18 | 0 | 0.0 | 883 ms | 0 |
| Thu 20 | 0 | 0.0 | 857 ms | 0 |
| Thu 22 | 0 | 0.0 | 1054 ms | 0 |
| Fri 00 | 0 | 0.0 | 980 ms | 0 |
| Fri 02 | 0 | 0.0 | 805 ms | 0 |
| Fri 04 | 0 | 0.0 | 1019 ms | 0 |
| Fri 06 | 0 | 0.0 | 1026 ms | 0 |
| Fri 08 | 0 | 0.0 | 898 ms | 0 |
| Fri 10 | 0 | 0.0 | 907 ms | 0 |
| Fri 12 | 0 | 0.0 | 1021 ms | 0 |
| Fri 14 | 0 | 0.0 | 1111 ms | 0 |
| Fri 16 | 0 | 0.0 | 1095 ms | 0 |
| Fri 18 | 0 | 0.0 | 1018 ms | 0 |
| Fri 19 | 0 | 0.0 | 1057 ms | 0 |
| Fri 21 | 0 | 0.0 | 869 ms | 0 |
| Fri 23 | 0 | 0.0 | 757 ms | 0 |
| Sat 01 | 0 | 0.0 | 1104 ms | 0 |
| Sat 03 | 0 | 0.0 | 854 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 Indexmed 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 Indexmed goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Indexmed alerts to Slack, Discord or a webhook — free.
Indexmed is listed in our Cloud & developer category and checked at indexmed.com.br. Software de gestão de SST para centralizar saúde ocupacional, segurança do trabalho, riscos psicossociais e eSocial em um único ambiente.
Indexmed publishes an official status page at status.indexmed.com.br; when we can read it, its incident level is folded into the status shown here.
What usually goes wrong with 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: 976 ms average, 757–1111 ms range across 12 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public Indexmed incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
976 ms on average over the last 24 hours (757–1111 ms).
Yes, at https://status.indexmed.com.br.
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 Indexmed here at once, the problem is on Indexmed'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 Indexmed. 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.