CASTAI logo

Is CASTAI Down?

Cloud InfrastructureLive status, outages, and incident history

No. CASTAI is up right now.

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

OperationalChecked just nowLive · every 60s

Know the moment CASTAI breaks

CASTAI 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.

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

Status report

CASTAI Status Summary

As of 17:42 UTC on 9 November 2026, CASTAI is operational. PulsAPI checked CASTAI's official status page and found 13 of 13 components operational, with no active incidents. Over the last 30 days PulsAPI measured 100.00% uptime for CASTAI, counting degraded performance as up. The latest incident, "AWS EKS – Oregon (us-west-2) Service Disruption", was on Nov 7, 2026 and lasted 4h 24m.

Cite as: PulsAPI, “CASTAI status”, checked 9 November 2026, 17:42 UTC. https://www.pulsapi.com/services/castai

CASTAI Component Status

The main CASTAI systems on this page. All 13 are operational right now.

13operational
Cloud Provider
Operational
EU Node Autoscaler
Operational
EU Workload Autoscaler
Operational

10 more components tracked

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

Also tracking India Node Autoscaler, India Workload Autoscaler, Node Autoscaler, Uptime of EU API: api.eu.cast.ai, Uptime of https://console.cast.ai, Uptime of https://console.eu.cast.ai, Uptime of https://console.india.cast.ai, Uptime of India API: api.india.cast.ai, Uptime of public API: api.cast.ai, Workload Autoscaler.

See all of them free

Component statuses may change independently during partial outages.

Recent CASTAI Outages & Incidents

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

AWS EKS – Oregon (us-west-2) Service DisruptionResolved Nov 7, 2026 · 4h 24mResolved

AWS confirmed full recovery at **4:21 PM PST**. The issue was caused by an EBS subsystem failure affecting EC2 instance launches across all AZs. **Impact:** EKS node provisioning and autoscaling may have failed between **2:35–4:21 PM PST**. Existing instances were unaffected. All services are operating normally. AWS Status: <https://health.aws.amazon.com/health/status> --- [2026-11-07T00:08:55Z] (identified) AWS is currently experiencing elevated EC2 instance launch failures in the Oregon region (us-west-2) due to an underlying EBS service issue. This may impact EKS clusters in the region, including node provisioning, autoscaling, rebalancing and workloads requiring new instances. AWS is actively working on mitigation. We'll continue monitoring the situation and share updates as they become available. AWS Status: https://health.aws.amazon.com/health/status

Scheduled maintenance: Console login (US region) Resolved Oct 2, 2026 · 1h 3mResolved

Maintenance has started --- [2026-09-30T21:45:07Z] (maintenance_scheduled) We’re performing planned maintenance on the US console login service. During this time, new logins, including `castctl login`, will be unavailable for approximately 10 to 15 minutes, and new login tokens cannot be issued for the India region. Existing sessions, cluster operations, and automation are not affected. Other regions will continue operating normally. We’ll update this notice once the maintenance is complete.

Scheduled maintenance: Console login (EU region)Resolved Oct 1, 2026 · 35 minResolved

Maintenance has started --- [2026-09-30T21:43:33Z] (maintenance_scheduled) We’re performing planned maintenance on the EU console login service. During this time, new logins, including `castctl login`, will be unavailable for approximately 10 to 15 minutes, and new login tokens cannot be issued for the India region. Existing sessions, cluster operations, and automation are not affected. Other regions will continue operating normally. We’ll update this notice once the maintenance is complete.

CASTAI Uptime History

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

Uptime history91 days observed
Aug 11100.00% average · 1 day with incidentsNov 9

Going further back: CASTAI uptime by month and every recorded CASTAI outage.

Live CASTAI Outage Reports

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

Something wrong with CASTAI on your end?

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

About CASTAI

CASTAI exposes 9 monitored components on its status page at status.cast.ai — Uptime of https://console.eu.cast.ai, Node Autoscaler and Uptime of https://console.cast.ai among them. Follow CASTAI downtime, degraded performance and resolved incidents here, with uptime history alongside your other cloud infrastructure services.

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

CASTAI Status FAQ

Is CASTAI down right now?

The verdict at the top of this page comes from the latest poll of the official CASTAI 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 CASTAI 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 CASTAI recovers.

How do I check CASTAI uptime history?

PulsAPI tracks CASTAI 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 CASTAI changes state, plus 15 days of incident detail; Pro extends that to 90 days and Business to 13 months.

How fast does PulsAPI detect CASTAI outages?

PulsAPI reads the official CASTAI 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 CASTAI components?

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

Can I get alerts when CASTAI goes down?

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

Is there a free way to monitor CASTAI?

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

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