User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Productivity
Is Dynapps down?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft outage and your Odoo environment
Source: the vendor's status page · We are not affiliated with Dynapps.
What to try while Dynapps is having problems
Estimated fix: Not enough Dynapps history yet; similar Productivity outages lasted 45 min (median, typically 14 min–4 h; 27 outages).
- Desktop and mobile apps often keep working offline on files you opened recently.
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 → dynapps.be—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · 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 364 ms.
Official status
Minor incident
Microsoft outage and your Odoo environment Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 13 | 0 | 0.0 | 350 ms | 0 |
| Mon 15 | 0 | 0.0 | 361 ms | 0 |
| Mon 17 | 0 | 0.0 | 352 ms | 0 |
| Mon 20 | 0 | 0.0 | 536 ms | 0 |
| Mon 22 | 0 | 0.0 | 384 ms | 0 |
| Tue 00 | 0 | 0.0 | 363 ms | 0 |
| Tue 02 | 0 | 0.0 | 454 ms | 0 |
| Tue 04 | 0 | 0.0 | 538 ms | 0 |
| Tue 06 | 0 | 0.0 | 326 ms | 0 |
| Tue 08 | 0 | 0.0 | 357 ms | 0 |
| Tue 10 | 0 | 0.0 | 543 ms | 0 |
| Tue 12 | 0 | 0.0 | 507 ms | 0 |
| Tue 15 | 0 | 0.0 | 350 ms | 0 |
| Tue 17 | 0 | 0.0 | 563 ms | 0 |
| Tue 19 | 0 | 0.0 | 325 ms | 0 |
| Tue 21 | 0 | 0.0 | 388 ms | 0 |
| Wed 00 | 0 | 0.0 | 510 ms | 0 |
| Wed 02 | 0 | 0.0 | 537 ms | 0 |
| Wed 04 | 0 | 0.0 | 383 ms | 0 |
| Wed 05 | 0 | 0.0 | 349 ms | 0 |
| Wed 07 | 0 | 0.0 | 484 ms | 0 |
| Wed 10 | 0 | 0.0 | 342 ms | 0 |
| Wed 12 | 0 | 0.0 | 321 ms | 0 |
| Wed 14 | 0 | 0.0 | 307 ms | 0 |
| Wed 16 | 0 | 0.0 | 338 ms | 0 |
| Wed 18 | 0 | 0.0 | 374 ms | 0 |
| Wed 20 | 0 | 0.0 | 289 ms | 0 |
| Wed 23 | 0 | 0.0 | 360 ms | 0 |
| Thu 01 | 0 | 0.0 | 360 ms | 0 |
| Thu 03 | 0 | 0.0 | 395 ms | 0 |
| Thu 05 | 0 | 0.0 | 345 ms | 0 |
| Thu 07 | 0 | 0.0 | 543 ms | 0 |
| Thu 09 | 0 | 0.0 | 350 ms | 0 |
| Thu 11 | 0 | 0.0 | 348 ms | 0 |
| Thu 13 | 0 | 0.0 | 382 ms | 0 |
| Thu 15 | 0 | 0.0 | 354 ms | 0 |
| Thu 17 | 0 | 0.0 | 336 ms | 0 |
| Thu 19 | 0 | 0.0 | 357 ms | 0 |
| Thu 21 | 0 | 0.0 | 345 ms | 0 |
| Thu 23 | 0 | 0.0 | 403 ms | 0 |
| Fri 02 | 0 | 0.0 | 497 ms | 0 |
| Fri 04 | 0 | 0.0 | 385 ms | 0 |
| Fri 06 | 0 | 0.0 | 360 ms | 0 |
| Fri 08 | 0 | 0.0 | 363 ms | 0 |
| Fri 09 | 0 | 0.0 | 373 ms | 0 |
| Fri 11 | 0 | 0.0 | 527 ms | 0 |
| Fri 13 | 0 | 0.0 | 344 ms | 0 |
| Fri 15 | 0 | 0.0 | 364 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 6 days of data so far, so the 90-day numbers fill in over time.
Embed this status: free live Dynapps 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 Dynapps yet. Outages of 10 minutes or more get their own page here.
Having trouble with Dynapps?
One report per service every 10 minutes from this network. No account.
Follow Dynapps
Get an email when Dynapps goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Dynapps alerts to Slack, Discord or a webhook — free.
About Dynapps
We track Dynapps (dynapps.be) as part of the Productivity group. 280+ Odoo experts across 5 countries. Industry-first Odoo implementation, migration, integration and support.
Dynapps publishes an official status page at status.dynapps.be; when we can read it, its incident level is folded into the status shown here.
Typical issues with productivity services: files not syncing, editors not loading, and sign-in problems.
Measured uptime from our checks: 100% over 6 days of checks. No public incidents logged since monitoring began 6 days ago.
Response time over the last 24 hours: 388 ms average, 336–527 ms range across 12 successful checks.
Questions
Is Dynapps down right now?
The vendor's status page reports an issue. Our own checks and user reports have not confirmed a problem. Official status: Microsoft outage and your Odoo environment
When was Dynapps last down?
We have not recorded a public Dynapps incident since monitoring began 6 days ago.
What is Dynapps's uptime?
From our own checks: 100% over 6 days of checks.
How fast does Dynapps respond?
388 ms on average over the last 24 hours (336–527 ms).
Does Dynapps have an official status page?
Yes, at https://status.dynapps.be.
Dynapps 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 productivity services, watch for files not syncing, editors not loading, and sign-in problems. If many people report Dynapps here at once, the problem is on Dynapps'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 Dynapps. 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.