memoQ logo

Is memoQ Down?

SaaSLive status, outages, and incident history

No. memoQ is up right now.

Every monitored memoQ system is operational as of September 25, 2026. PulsAPI did not find an outage in its latest check of the official status feed.

OperationalChecked 2m agoLive · 60s while moving

Know the moment memoQ breaks

memoQ is healthy right now. We keep checking (every 60 seconds once it starts moving) and email you the moment that changes.

Free, no password, no card. Unsubscribe in one click.

How we know: the official memoQ status page, PulsAPI's own check (every 60 seconds while one is moving, every 5 to 20 minutes while it is stable), and outage reports from engineers. How PulsAPI monitoring works

memoQ Component Status

The main memoQ systems on this page. All 32 are operational right now.

32operational
globalese by memoQ » Document translation
Operational
globalese by memoQ » Google Cloud Platform Google Cloud SQL
Operational
globalese by memoQ » Google Cloud Platform Google Cloud Storage
Operational

29 more components tracked

Their status is in the bar above. Free accounts see every component by name.

Also tracking globalese by memoQ » Google Cloud Platform Google Kubernetes Engine, globalese by memoQ » Text translation, globalese by memoQ » Training, memoQ AGT, memoQ TMS cloud » antares.memoq.com, memoQ TMS cloud » arion.memoq.com, memoQ TMS cloud » fuji.memoq.com, memoQ TMS cloud » himawari.memoq.com, memoQ TMS cloud » lonestar.memoq.com, memoQ TMS cloud » longhorn.memoq.com, memoQ TMS cloud » malibu.memoq.com, memoQ TMS cloud » maple.memoq.com, and 17 more.

See all of them free

Component statuses may change independently during partial outages.

Recent memoQ Outages & Incidents

Incident history from the official memoQ status page, including resolution updates.

Urgent maintenance in memoQ public cloudScheduled for Sep 20, 2026 · 1h 0mScheduled

The scheduled maintenance has been completed. --- [2026-09-20T08:00:08.502Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-20T07:00:23.457Z] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-09-18T14:13:38.977Z] (scheduled) We will be undergoing a quick urgent maintenance in our memoQ public cloud. The downtime for the individual services is expected to be a couple of minutes within the maintenance window. Apologies for the inconvenience.

memoQ TMS cloud release - version 12.5.20Scheduled for Sep 16, 2026 · 96h 0mScheduled

The scheduled maintenance has been completed. --- [2026-09-16T13:00:10.835Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-16T12:00:11.623Z] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-09-15T14:23:50.604Z] (scheduled) A new memoQ TMS version 12.5.20 is being released to memoQ TMS cloud. The release does not affect the overall operation of memoQ TMS cloud. Upgrade takes place during the daily maintenance slots within this release timeframe.

Monthly maintenance - memoQ TMS cloud (except ziggurat.memoq.com)Scheduled for Sep 6, 2026 · 6h 0mScheduled

The scheduled maintenance has been completed. --- [2026-09-06T08:01:10.972Z] (in_progress) Scheduled maintenance is currently in progress. We will provide updates as necessary. --- [2026-09-06T07:00:12.809Z] (scheduled) Maintenance will begin as scheduled in 60 minutes. --- [2026-08-26T06:35:50.057Z] (scheduled) We will be undergoing scheduled maintenance during this time.

memoQ Uptime History

Daily uptime recorded by PulsAPI over the last 90 days, with the days that carried a memoQ incident marked. Each day is measured from our own checks, so the record continues even when the vendor publishes nothing.

Uptime history49 days observed
Aug 8100.00% average · 9 days with incidentsSep 25

Live memoQ Outage Reports

Problems reported by engineers using memoQ. Reports often appear 10 to 20 minutes before the official status page moves, and stay on this page for 90 days.

Reports, last 24 hours0 total
24h agoNothing reportednow
Most recent report
Service DownSevereKaunas, Lithuaniaabout 7 days ago

Something wrong with memoQ on your end?

Reports are anonymous, take about ten seconds, and help the next engineer who checks.

About memoQ

memoQ publishes a public status page at status.memoq.com covering 36 components, including memoQ TMS cloud, antares.memoq.com and www.memoq.com. PulsAPI tracks memoQ outages, degraded performance and incident history in real time, alongside the rest of your SaaS stack.

Over the past 30 days, PulsAPI has measured memoQ uptime at 100.00%. Response times, incident history, and SLA tracking for memoQ are available on the PulsAPI dashboard.

memoQ Status FAQ

Is memoQ down right now?

The verdict at the top of this page comes from the latest poll of the official memoQ status feed and refreshes automatically, so you are not looking at a stale cached answer. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead.

What should I do if memoQ is not working?

Check the component list on this page first to see if your failure matches a known outage. If it does, you can report the issue for other engineers, follow the incident timeline for vendor updates, and run any fallback your app supports until memoQ recovers.

How do I check memoQ uptime history?

PulsAPI tracks memoQ uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 100.00%. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever memoQ changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect memoQ outages?

PulsAPI reads the official memoQ status page. PulsAPI re-checks a vendor every 60 seconds whenever it is not fully operational, or has changed status in the last 30 minutes, so an incident is always on the fastest cadence. Vendors that are stable and rarely watched are re-checked every 5 to 20 minutes instead. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email within seconds of detection.

Does PulsAPI track individual memoQ components?

Yes. PulsAPI monitors 32 individual memoQ components, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when memoQ goes down?

Yes. Create a free account and subscribe to memoQ: the free plan covers three services with unlimited email alerts and no monthly notification cap. Paid plans lift the monitor limit entirely (Pro and above do not meter how many vendors you watch) and route the same alerts into Slack, Discord, Microsoft Teams, PagerDuty and webhooks.

How do I report an issue with memoQ to the community?

Click "Report an issue" at the top of this page, pick the issue type and severity, and optionally add your region and a short note. Reports are anonymous and help other engineers spot memoQ problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor memoQ?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so memoQ plus two more costs nothing. Every new account also opens with a 30-day Business trial (unlimited monitors, Slack alerts, SLA reporting) with no credit card.

Track memoQ with the rest of your stack

2463+ vendors in one dashboard, and an email the moment any of them changes state. Three free, and no monitor limit at all from $29/mo, unlike the alternatives, which keep charging by the monitor.

Start free, 3 services