User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
Damn, is it down?
All services / 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 662 ms.
All clear
All Systems Operational Official status page
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| Mon 21 | 0 | 0.0 | 584 ms | 0 |
| Mon 23 | 0 | 0.0 | 691 ms | 0 |
| Tue 01 | 0 | 0.0 | 604 ms | 0 |
| Tue 03 | 0 | 0.0 | 617 ms | 0 |
| Tue 05 | 0 | 0.0 | 633 ms | 0 |
| Tue 07 | 0 | 0.0 | 658 ms | 0 |
| Tue 10 | 0 | 0.0 | 719 ms | 0 |
| Tue 12 | 0 | 0.0 | 710 ms | 0 |
| Tue 14 | 0 | 0.0 | 545 ms | 0 |
| Tue 16 | 0 | 0.0 | 678 ms | 0 |
| Tue 18 | 0 | 0.0 | 752 ms | 0 |
| Tue 21 | 0 | 0.0 | 723 ms | 0 |
| Tue 23 | 0 | 0.0 | 626 ms | 0 |
| Wed 01 | 0 | 0.0 | 603 ms | 0 |
| Wed 03 | 0 | 0.0 | 466 ms | 0 |
| Wed 06 | 0 | 0.0 | 595 ms | 0 |
| Wed 08 | 0 | 0.0 | 516 ms | 0 |
| Wed 10 | 0 | 0.0 | 2686 ms | 0 |
| Wed 12 | 0 | 0.0 | 648 ms | 0 |
| Wed 14 | 0 | 0.0 | 652 ms | 0 |
| Wed 17 | 0 | 0.0 | 716 ms | 0 |
| Wed 19 | 0 | 0.0 | 523 ms | 0 |
| Wed 21 | 0 | 0.0 | 690 ms | 0 |
| Wed 23 | 0 | 0.0 | 656 ms | 0 |
| Thu 01 | 0 | 0.0 | 680 ms | 0 |
| Thu 03 | 0 | 0.0 | 708 ms | 0 |
| Thu 05 | 0 | 0.0 | 634 ms | 0 |
| Thu 07 | 0 | 0.0 | 625 ms | 0 |
| Thu 10 | 0 | 0.0 | 686 ms | 0 |
| Thu 12 | 0 | 0.0 | 743 ms | 0 |
| Thu 14 | 0 | 0.0 | 711 ms | 0 |
| Thu 16 | 0 | 0.0 | 580 ms | 0 |
| Thu 18 | 0 | 0.0 | 509 ms | 0 |
| Thu 20 | 0 | 0.0 | 649 ms | 0 |
| Thu 22 | 0 | 0.0 | 610 ms | 0 |
| Fri 00 | 0 | 0.0 | 692 ms | 0 |
| Fri 02 | 0 | 0.0 | 636 ms | 0 |
| Fri 04 | 0 | 0.0 | 599 ms | 0 |
| Fri 06 | 0 | 0.0 | 506 ms | 0 |
| Fri 08 | 0 | 0.0 | 483 ms | 0 |
| Fri 10 | 0 | 0.0 | 582 ms | 0 |
| Fri 12 | 0 | 0.0 | 649 ms | 0 |
| Fri 14 | 0 | 0.0 | 600 ms | 0 |
| Fri 16 | 0 | 0.0 | 591 ms | 0 |
| Fri 18 | 0 | 0.0 | 676 ms | 0 |
| Fri 20 | 0 | 0.0 | 629 ms | 0 |
| Fri 21 | 0 | 0.0 | 673 ms | 0 |
| Fri 23 | 0 | 0.0 | 662 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 memoQ 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 memoQ goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send memoQ alerts to Slack, Discord or a webhook — free.
memoQ, at memoq.com, is one of the Cloud & developer services we monitor. memoQ offers flexible translation and localization management solutions tailored to enterprises, language service providers, and translators.
memoQ publishes an official status page at status.memoq.com; 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 7 days of checks. No public incidents logged since monitoring began 7 days ago.
Response time over the last 24 hours: 611 ms average, 483–677 ms range across 14 successful checks.
Checks are succeeding, user reports are near the baseline, and the vendor status page is clear.
We have not recorded a public memoQ incident since monitoring began 7 days ago.
From our own checks: 100% over 7 days of checks.
611 ms on average over the last 24 hours (483–677 ms).
Yes, at https://status.memoq.com.
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 memoQ here at once, the problem is on memoQ'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 memoQ. 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.