User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
amplimed.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 1 hr ago. Last stored result reached it in 2225 ms.
All clear
No active incidents in the official feed Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Nov 6 | 0 | 0.0 | 732 ms | 0 |
| Nov 7 | 0 | 0.0 | 1944 ms | 0 |
| Nov 7 | 0 | 0.0 | 2247 ms | 0 |
| Nov 7 | 0 | 0.0 | 2266 ms | 0 |
| Nov 7 | 0 | 0.0 | 2223 ms | 0 |
| Nov 8 | 0 | 0.0 | 2235 ms | 0 |
| Nov 8 | 0 | 0.0 | 2143 ms | 0 |
| Nov 8 | 0 | 0.0 | 2098 ms | 0 |
| Nov 8 | 0 | 0.0 | 2157 ms | 0 |
| Nov 9 | 0 | 0.0 | 2186 ms | 0 |
| Nov 9 | 0 | 0.0 | 2322 ms | 0 |
| Nov 9 | 0 | 0.0 | 2121 ms | 0 |
| Nov 9 | 0 | 0.0 | 2032 ms | 0 |
| Nov 10 | 0 | 0.0 | 2027 ms | 0 |
| Nov 10 | 0 | 0.0 | 2177 ms | 0 |
| Nov 10 | 0 | 0.0 | 2160 ms | 0 |
| Nov 10 | 0 | 0.0 | 1824 ms | 0 |
| Nov 11 | 0 | 0.0 | 1894 ms | 0 |
| Nov 11 | 0 | 0.0 | 2164 ms | 0 |
| Nov 11 | 0 | 0.0 | 2045 ms | 0 |
| Nov 11 | 0 | 0.0 | 2221 ms | 0 |
| Nov 12 | 0 | 0.0 | 2157 ms | 0 |
| Nov 12 | 0 | 0.0 | 2041 ms | 0 |
| Nov 12 | 0 | 0.0 | 2146 ms | 0 |
| Nov 12 | 0 | 0.0 | 2212 ms | 0 |
| Nov 13 | 0 | 0.0 | 2159 ms | 0 |
| Nov 13 | 0 | 0.0 | 2101 ms | 0 |
| Nov 13 | 0 | 0.0 | 2245 ms | 0 |
| Nov 13 | 0 | 0.0 | 2189 ms | 0 |
| Nov 14 | 0 | 0.0 | 2248 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 da Amplimed 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 da Amplimed goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send da Amplimed alerts to Slack, Discord or a webhook — free.
da Amplimed, at amplimed.com.br, is one of the Cloud & developer services we monitor. Conheça o sistema para clínicas e consultórios especialista em prontuário eletrônico, teleconsulta, agendamento online, faturamento TISS e muito mais.
da Amplimed publishes an official status page at status.amplimed.com.br; 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 9 days of checks. No public incidents logged since monitoring began 9 days ago.
Response time over the last 24 hours: 2152 ms average, 1453–2497 ms range across 15 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public da Amplimed incident since monitoring began 9 days ago.
From our own checks: 100% over 9 days of checks.
2152 ms on average over the last 24 hours (1453–2497 ms).
Yes, at https://status.amplimed.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 da Amplimed here at once, the problem is on da Amplimed'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 da Amplimed. 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.