User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / Cloud & developer
dialogue.co · 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 899 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 20 | 0 | 0.0 | 663 ms | 0 |
| Mon 22 | 0 | 0.0 | 636 ms | 0 |
| Tue 00 | 0 | 0.0 | 685 ms | 0 |
| Tue 02 | 0 | 0.0 | 768 ms | 0 |
| Tue 04 | 0 | 0.0 | 625 ms | 0 |
| Tue 06 | 0 | 0.0 | 707 ms | 0 |
| Tue 07 | 0 | 0.0 | 642 ms | 0 |
| Tue 09 | 0 | 0.0 | 738 ms | 0 |
| Tue 11 | 0 | 0.0 | 584 ms | 0 |
| Tue 13 | 0 | 0.0 | 771 ms | 0 |
| Tue 15 | 0 | 0.0 | 765 ms | 0 |
| Tue 17 | 0 | 0.0 | 815 ms | 0 |
| Tue 20 | 0 | 0.0 | 1109 ms | 0 |
| Tue 22 | 0 | 0.0 | 670 ms | 0 |
| Wed 00 | 0 | 0.0 | 662 ms | 0 |
| Wed 02 | 0 | 0.0 | 827 ms | 0 |
| Wed 05 | 0 | 0.0 | 584 ms | 0 |
| Wed 07 | 0 | 0.0 | 720 ms | 0 |
| Wed 09 | 0 | 0.0 | 684 ms | 0 |
| Wed 11 | 0 | 0.0 | 755 ms | 0 |
| Wed 13 | 0 | 0.0 | 803 ms | 0 |
| Wed 15 | 0 | 0.0 | 706 ms | 0 |
| Wed 18 | 0 | 0.0 | 699 ms | 0 |
| Wed 20 | 0 | 0.0 | 749 ms | 0 |
| Wed 22 | 0 | 0.0 | 707 ms | 0 |
| Thu 00 | 0 | 0.0 | 585 ms | 0 |
| Thu 02 | 0 | 0.0 | 802 ms | 0 |
| Thu 04 | 0 | 0.0 | 580 ms | 0 |
| Thu 06 | 0 | 0.0 | 631 ms | 0 |
| Thu 08 | 0 | 0.0 | 747 ms | 0 |
| Thu 11 | 0 | 0.0 | 657 ms | 0 |
| Thu 13 | 0 | 0.0 | 735 ms | 0 |
| Thu 15 | 0 | 0.0 | 761 ms | 0 |
| Thu 17 | 0 | 0.0 | 896 ms | 0 |
| Thu 19 | 0 | 0.0 | 699 ms | 0 |
| Thu 21 | 0 | 0.0 | 678 ms | 0 |
| Thu 23 | 0 | 0.0 | 593 ms | 0 |
| Fri 01 | 0 | 0.0 | 621 ms | 0 |
| Fri 03 | 0 | 0.0 | 698 ms | 0 |
| Fri 05 | 0 | 0.0 | 692 ms | 0 |
| Fri 07 | 0 | 0.0 | 614 ms | 0 |
| Fri 09 | 0 | 0.0 | 631 ms | 0 |
| Fri 11 | 0 | 0.0 | 561 ms | 0 |
| Fri 13 | 0 | 0.0 | 621 ms | 0 |
| Fri 15 | 0 | 0.0 | 669 ms | 0 |
| Fri 17 | 0 | 0.0 | 807 ms | 0 |
| Fri 19 | 0 | 0.0 | 756 ms | 0 |
| Fri 21 | 0 | 0.0 | 899 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 8 days of data so far, so the 90-day numbers fill in over time.
Entretien de bases de données (Amérique du Nord) / Database Maintenance (North America)
English follows Nous procéderons à la mise à jour de nos bases de données. L’opération devrait durer un maximum d'une heure. Le temps d'arrêt de la base de données devrait durer quelques minutes. Durant ce temps, la majorité de nos systèmes seront indisponibles. --- We will proceed with the maintenance of our databases. The operation should last a maximum of one hour. The downtime of the…
Planned maintenance is not an outage. Times and wording are the vendor’s own. Outage Weather →
No outages on record for Dialogue 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 Dialogue goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Dialogue alerts to Slack, Discord or a webhook — free.
Dialogue, at dialogue.co, is one of the Cloud & developer services we monitor. Build happier, healthier, more productive teams with Dialogue's tailored, measurable, high-quality virtual care programs.
Dialogue publishes an official status page at status.dialogue.co; 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: 676 ms average, 561–899 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 Dialogue incident since monitoring began 8 days ago.
From our own checks: 100% over 8 days of checks.
676 ms on average over the last 24 hours (561–899 ms).
Yes, at https://status.dialogue.co.
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 Dialogue here at once, the problem is on Dialogue'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 Dialogue. 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.