Astro logo

Is Astro Down?

SaaSLive status, outages, and incident history

Degraded. Astro is up but having problems.

Astro is reporting degraded performance as of October 7, 2026. Expect slower responses or more errors. The affected components are listed below.

DegradedChecked just nowLive · 60s while moving1 active incident

Don't find out like this next time

You searched to find out Astro was down. Next time we tell you, usually before your customers do, and always before you think to check.

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

Official Astro status page
How we know: the official Astro 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

Astro Component Status

1 of 9 Astro components are impaired. Worst problems listed first.

1degraded8operational
Scheduling and Running DAGs and Tasks
Degraded
Astro Observe
Operational
Cloud API
Operational

6 more components tracked

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

Also tracking Cloud Image Repository, Cloud UI, Cluster Management, Dashboards and Analytics, Deployment Access, Deployment Management.

See all of them free

Component statuses may change independently during partial outages.

Recent Astro Outages & Incidents

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

Capacity constraints in GCP us-central1 may delay or fail some task executionsStarted Oct 6, 2026Investigating

We are currently seeing a capacity shortage in the Google Cloud (GCP) `us-central1` region. As a result, some Deployments running in this region may experience delays when scaling up worker nodes and pods. Some tasks may remain in a queued state for longer than usual while waiting for compute capacity. In some cases, tasks that stay queued beyond their configured timeout may fail. **Recommended workaround:** Configuring automated task retries (for example, setting `retries` and a `retry_delay` on your tasks or in your DAG's `default_args`) will help tasks recover automatically once capacity becomes available. <https://www.astronomer.io/docs/learn/rerunning-dags#automatically-retry-tasks> We are working to address the issue and keep this page posted as we have more updates.

Dag success/failure Astro Alert emails missing deployment & workspace namesResolved Oct 3, 2026 · 56 minResolved

All Astro Alert emails for Dag Success/Failure now correctly include the deployment/workspace name. --- [2026-10-03T21:13:03Z] (monitoring) We have reverted the problematic email template changes and are continuing to monitor for full resolution. --- [2026-10-03T21:03:35Z] (identified) Correction: Deployment and Workspace _names_ are not populated, earlier update cited IDs incorrectly. --- [2026-10-03T20:42:50Z] (identified) We have identified a recent change that broke the templating of the deploymentId and workspaceId fields used in the Astro Alert emails for Dag Success and Failure emails. We are working on a fix and will provide updates shortly.

Tasks getting stuck in the queued state and failingResolved Oct 1, 2026 · 1h 7mResolved

Our development team has concluded that this was a false alert. It is not affecting multiple deployments. --- [2026-10-01T22:40:38Z] (investigating) We have identified several hosted deployments where tasks are getting stuck in the queued state and failing. This is happening the worker autoscaler is having issues with scaling up workers to run tasks. We are investigating the cause of this.

Astro Uptime History

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

Uptime history61 days observed
Aug 8100.00% average · 29 days with incidentsOct 7

Live Astro Outage Reports

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

Are you seeing Astro problems too?

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

About Astro

Is Astro down? Astro reports live availability for 15 components at status.astronomer.io, among them Scheduling and Running DAGs and Tasks, Cluster Management and Deployment Access. Track Astro outages, degradations and past incidents here, with uptime history and alerts across your SaaS stack.

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

Astro Status FAQ

Is Astro down right now?

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

How do I check Astro uptime history?

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

How fast does PulsAPI detect Astro outages?

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

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

Can I get alerts when Astro goes down?

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

Is there a free way to monitor Astro?

Yes. The free plan covers 3 monitored services with unlimited email alerts, permanently, so Astro 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 Astro 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