Blade logo

Is Blade Down?

AI & Machine LearningLive status, outages, and incident history

No. Blade is up right now.

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

OperationalChecked 4m agoLive · every 60s

Know the moment Blade breaks

Blade is healthy right now. We keep checking (every 60 seconds) and email you when that changes.

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

Official Blade status page
How we know: the official Blade status page, PulsAPI's own check (every 60 seconds), and outage reports from engineers. How PulsAPI monitoring works

Status report

Blade Status Summary

As of 12:35 UTC on 14 November 2026, Blade is operational. PulsAPI checked Blade's official status page and found 5 of 5 components operational, with no active incidents. The latest incident, "Blade.sh Models - Gateway Restarts leads to increased error rate and latency", was on Nov 13, 2026 and lasted 6h 10m.

Cite as: PulsAPI, “Blade status”, checked 14 November 2026, 12:35 UTC. https://www.pulsapi.com/services/blade

Blade Component Status

The main Blade systems on this page. All 5 are operational right now.

5operational
API
Operational
Authentication
Operational
Billing
Operational

2 more components tracked

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

Also tracking Console, Support.

See all of them free

Component statuses may change independently during partial outages.

Recent Blade Outages & Incidents

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

Blade.sh Models - Gateway Restarts leads to increased error rate and latencyResolved Nov 13, 2026 · 6h 10mResolved

Incident is considered resolved. --- [2026-11-13T22:28:07Z] (monitoring) This incident is now resolved, latency and errors has returned to baseline. --- [2026-11-13T17:17:39Z] (monitoring) The situation is back to normal and mitigation is implemented. --- [2026-11-13T16:20:22Z] (identified) Increased usage of the platform lead to Gateway restarts which triggered increased error rate and latencies.

[CAMTL01] Storage server disruptionResolved Oct 12, 2026 · 46 minResolved

Everything is working as expected. --- [2026-10-12T11:50:23Z] (identified) We've identified an issue affecting a subset of users (300+) who are unable to access their VMs due to an unresponsive storage server. Our team has identified the cause and is actively working on a fix. Other users are not affected. We'll post an update if the situation changes. We apologize for the inconvenience and appreciate your patience.

Degraded performance on APIsResolved Aug 27, 2026 · 19h 47mResolved

Everything should be back to normal sorry for the inconvenience. --- [2026-08-27T13:12:46Z] (investigating) We are seeing 5xx on some models, we are actively looking into it.

Blade Uptime History

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

Uptime history3 days observed
Nov 12100.00% average · 1 day with incidentsNov 14

Live Blade Outage Reports

Problems reported by engineers using Blade. 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 Blade problems reported yet.

Something wrong with Blade on your end?

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

About Blade

Blade's status page at status.blade.sh lists 5 components, such as API, Authentication and Billing. We read that page every few minutes and keep the incident history, so you can tell whether a problem is on Blade's side or yours.

Blade Status FAQ

Is Blade down right now?

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

What should I do if Blade 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 Blade recovers.

How do I check Blade uptime history?

PulsAPI tracks Blade uptime over 30, 60, and 90-day rolling windows. The current 30-day uptime is not published yet, because a 30-day figure needs 30 days of tracked history. The 90-day uptime strip on this page is public: no account needed. A free account adds alerts whenever Blade changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect Blade outages?

PulsAPI reads the official Blade status page. PulsAPI re-checks it every 60 seconds. Alerts reach Slack, Discord, Microsoft Teams, PagerDuty, or email once a change has held for 5 minutes, so a one-minute blip does not page you.

Does PulsAPI track individual Blade components?

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

Can I get alerts when Blade goes down?

Yes. Create a free account and subscribe to Blade: 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 Blade 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 Blade problems early. Official status pages often lag real incidents by 10 to 20 minutes.

Is there a free way to monitor Blade?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Blade 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 Blade with the rest of your stack

4372+ 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