Thinking Machines Lab logo

Is Thinking Machines Lab Down?

SaaSLive status, outages, and incident history

Partly. Some of Thinking Machines Lab is down.

Thinking Machines Lab is in a partial outage as of August 11, 2026. Some components are down and others are still running, so check the list below to see whether your region or feature is affected.

Partial OutageChecked 24m agoLive, rechecked every 60s3 active incidents
How we know: the official Thinking Machines Lab status page, PulsAPI's own check every 60 seconds, and outage reports from engineers. How PulsAPI monitoring works

Thinking Machines Lab Component Status

1 of 1 Thinking Machines Lab components are impaired. Worst problems listed first.

1partial outage
Tinker API
Partial Outage

Component statuses may change independently during partial outages.

Recent Thinking Machines Lab Outages & Incidents

Incident history from the official Thinking Machines Lab status page, including resolution updates.

Uptime history4 days observed
Aug 80.00% average · 4 days with incidentsAug 11
All sampling was down 6:36PM PT - 7:01PM PT on 08/08Started Aug 9, 2026Investigating

There was a brief outage for sampling traffic and now fully recovered.

Training on Inkling could fail with variable-shape loss inputs — SDK 0.24.1 requiredStarted Aug 6, 2026Investigating

Training requests where `loss_fn_inputs` tensors have different shapes across datums in one batch (for example, per-datum target_tokens with a varying second dimension) are now fully supported on thinkingmachines/Inkling. Supporting this required a change to both the server and the SDK, so please upgrade to Tinker SDK 0.24.1 or later (pip install -U tinker). On SDK versions 0.24.0 and earlier, these requests are rejected at submission with: `loss_fn_inputs tensors have different shapes across datums (past the first dimension), which requires tinker SDK >= 0.24.1 to decode the response. Please upgrade your Tinker SDK.` Upgrading resolves this. All other workloads are unaffected and require no action.

Getting model info can fail for old modelsResolved Aug 5, 2026 · 48 minResolved

This is fully resolved now. --- [2026-08-05T21:03:51Z] (identified) `get_training_run` API on the `RestClient` may fail for old training runs.

Live Thinking Machines Lab Outage Reports

Problems reported by engineers using Thinking Machines Lab. 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

No Thinking Machines Lab problems reported yet.

Are you seeing Thinking Machines Lab problems too?

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

About Thinking Machines Lab

Thinking Machines Lab exposes 1 monitored component on its status page at status.thinkingmachines.ai — Tinker API among them. Follow Thinking Machines Lab downtime, degraded performance and resolved incidents here, with uptime history alongside your other SaaS services.

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

Thinking Machines Lab Status FAQ

Is Thinking Machines Lab down right now?

PulsAPI checks Thinking Machines Lab every 60 seconds. The verdict at the top of this page comes from the latest poll of the official Thinking Machines Lab status feed and refreshes automatically, so you are not looking at a stale cached answer.

What should I do if Thinking Machines Lab 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 Thinking Machines Lab recovers.

How do I check Thinking Machines Lab uptime history?

PulsAPI tracks Thinking Machines Lab uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is 25.00%. A free PulsAPI account unlocks the full 90-day SLA history and incident timeline for Thinking Machines Lab.

How fast does PulsAPI detect Thinking Machines Lab outages?

PulsAPI polls the official Thinking Machines Lab status page every 60 seconds and usually delivers alerts to Slack, Discord, Microsoft Teams, PagerDuty, or email in under 4 seconds after detection. That is often faster than someone on your team notices on their own.

Does PulsAPI track individual Thinking Machines Lab components?

Yes. PulsAPI monitors 1 individual Thinking Machines Lab component, so you can see which service or region is affected instead of a generic "service degraded" banner.

Can I get alerts when Thinking Machines Lab goes down?

Yes. Create a PulsAPI account and subscribe to Thinking Machines Lab. Email alerts are included on the free Starter plan. Paid plans add Slack, Discord, Microsoft Teams, PagerDuty, and webhooks whenever Thinking Machines Lab status changes.

How do I report an issue with Thinking Machines Lab 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 Thinking Machines Lab problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Thinking Machines Lab?

Yes. PulsAPI's Starter plan includes up to 10 monitored services with email alerts, and the 30-day free trial requires no credit card. You can monitor Thinking Machines Lab alongside up to 9 other services at pulsapi.com/signup.

Track Thinking Machines Lab with the rest of your stack

Monitor 2461+ cloud services from one dashboard and get alerts when Thinking Machines Lab status changes.

Start free trial