User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Cloud & developer
qive.com.br · Cloud & developer
Is Qive down?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
Live diagnosis
Is it just me?
Finds the most likely layer (the service, your ISP or area, DNS, or your Wi-Fi) and gives two steps to try.
Your browser → qive.com.br—
Your browser → us—
Our checksReaching it
Official · ReportsAll clear · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
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.
Live outage map
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.
What's broken
Recent reports
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.
Our checks
Reaching it
Last checked 2 hr ago. Last stored result reached it in 187 ms.
Official status
All clear
All Systems Operational Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 08:00 | 0 | 0.0 | 212 ms | 0 |
| 10:15 | 0 | 0.0 | 50 ms | 0 |
| 12:15 | 0 | 0.0 | 196 ms | 0 |
| 14:15 | 0 | 0.0 | 231 ms | 0 |
| 16:15 | 0 | 0.0 | 108 ms | 0 |
| 18:30 | 0 | 0.0 | 141 ms | 0 |
| 19:45 | 0 | 0.0 | 215 ms | 0 |
| 21:45 | 0 | 0.0 | 171 ms | 0 |
| 23:45 | 0 | 0.0 | 222 ms | 0 |
| 02:00 | 0 | 0.0 | 250 ms | 0 |
| 04:00 | 0 | 0.0 | 253 ms | 0 |
| 06:15 | 0 | 0.0 | 187 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
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 8 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Qive badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · badge docs · JSON · MCP server
Past outages
No outages on record for Qive yet. Outages of 10 minutes or more get their own page here.
Having trouble with Qive?
One report per service every 10 minutes from this network. No account.
Follow Qive
Get an email when Qive goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Qive alerts to Slack, Discord or a webhook — free.
About Qive
Qive is listed in our Cloud & developer category and checked at qive.com.br. Automação de ponta a ponta para pagamentos, documentos e fornecedores, com controle, escala e previsibilidade financeira.
Qive publishes an official status page at status.qive.com.br; when we can read it, its incident level is folded into the status shown here.
Typical issues with cloud & developer services: API errors, failed deploys or builds, and dashboard or console outages.
Measured uptime from our checks: 100% over 8 days of checks. No public incidents logged since monitoring began 8 days ago.
Response time over the last 24 hours: 186 ms average, 50–253 ms range across 12 successful checks.
Questions
Is Qive down right now?
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
When was Qive last down?
We have not recorded a public Qive incident since monitoring began 8 days ago.
What is Qive's uptime?
From our own checks: 100% over 8 days of checks.
How fast does Qive respond?
186 ms on average over the last 24 hours (50–253 ms).
Does Qive have an official status page?
Yes, at https://status.qive.com.br.
Qive not working for me but the status is fine. What now?
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 Qive here at once, the problem is on Qive'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 Qive. 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.