Skip to main content

Is Pantheon Down?

No — Pantheon is up

Reachable from all 8 checked regions

Average response time: 224ms

Last checked · checks run every 6 hours

Official status page: https://status.pantheon.io

Pantheon uptime

100%
Last 7 days
—
Last 30 days
—
Last 90 days
—
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 4 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

4-day clean streak
Jul 26: no data
Jul 27: no data
Jul 28: no data
Jul 29: no data
Jul 30: no data
Jul 31: no data
Aug 1: no data
Aug 2: no data
Aug 3: no data
Aug 4: no data
Aug 5: no data
Aug 6: no data
Aug 7: no data
Aug 8: no data
Aug 9: no data
Aug 10: no data
Aug 11: no data
Aug 12: no data
Aug 13: no data
Aug 14: no data
Aug 15: no data
Aug 16: no data
Aug 17: no data
Aug 18: no data
Aug 19: no data
Aug 20: no data
Aug 21: 100.00% uptime, 16 checks
Aug 22: 100.00% uptime, 32 checks
Aug 23: 100.00% uptime, 32 checks
Aug 24: 100.00% uptime, 8 checks
Jul 26 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

cdg
254ms
DNS 195ms TCP 1ms TLS 6ms TTFB 250ms
dfw
253ms
DNS 165ms TCP 2ms TLS 10ms TTFB 249ms
ewr
359ms
DNS 103ms TCP 7ms TLS 12ms TTFB 342ms
fra
66ms
DNS 26ms TCP 1ms TLS 7ms TTFB 60ms
gru
97ms
DNS 25ms TCP 2ms TLS 7ms TTFB 90ms
iad
365ms
DNS 50ms TCP 7ms TLS 29ms TTFB 348ms
jnb
271ms
DNS 232ms TCP 0ms TLS 5ms TTFB 266ms
lax
179ms
DNS 125ms TCP 1ms TLS 5ms TTFB 173ms
lhr
207ms
DNS 18ms TCP 1ms TLS 6ms TTFB 200ms

What Pantheon does

Pantheon hosts WordPress and Drupal sites for agencies and in-house teams, adding a global CDN, Git-backed deployments and separate development, test and live environments. Agencies often run dozens of client sites on one account, so a platform incident is felt across many unrelated businesses at the same time rather than by a single site owner.

What an outage looks like

Live sites return errors or time out while the Pantheon dashboard itself still loads, or the reverse: sites serve fine from the CDN while the dashboard is unreachable. Deployments queue and never complete. Creating a new site or a multidev environment stalls partway. Terminus commands hang or fail against the API. New sites come up without HTTPS because certificate provisioning has not run.

What to do about it

status.pantheon.io tracks 14 components, and the distinction that matters is Customer Sites against Dashboard: visitor-facing failure and operator-facing failure are separate rows. Global CDN, Git, Workflow Operations, Spinup Operations, Terminus Operations and Site Certificate Provisioning each report on their own. If only Dashboard or Workflow Operations is affected, live traffic is usually unharmed and the sensible move is to postpone deployments rather than retry them.

Is it down for everyone, or just you?

If this page says Pantheon is up but it is not loading for you, the problem is between you and them. Run a check against any URL from all 18 regions to find out where it breaks.

Test it yourself

Related services

W
WP Engine
K
Kinsta
Cloudflare
Cloudflare
W
WordPress

Pantheon outage FAQ

My site is down but the Pantheon dashboard works. What does that tell me?
That the fault is more likely yours than the platform's. Pantheon reports Customer Sites separately from Dashboard, so a healthy Customer Sites row alongside a broken site points at your own code, a plugin, a database query or a recent deployment. Check the Global CDN row too, since an edge problem can break delivery while the origin is fine.
A deployment is stuck. Should I run it again?
Check Workflow Operations before retrying. Deployments, clones and cache clears run as queued workflows, and during an incident a backlog makes a normal delay look like a failure. Firing the same deployment repeatedly adds more work to the queue that is already behind. Wait for the component to recover and let the queued run finish on its own.
Does a Pantheon outage affect all my client sites at once?
It can, which is the risk agencies carry by consolidating. Every site on the platform shares the Global CDN and the same workflow infrastructure, so a platform-level incident is simultaneous rather than staggered. Component-level incidents are narrower: a Site Certificate Provisioning problem only affects sites being created or renewed, not established ones.
My new site has no HTTPS. Is that an outage?
Look at Site Certificate Provisioning, which Pantheon tracks as its own component. Certificates are issued by a separate pipeline from the one that brings the site up, so a site can be live and serving over plain HTTP while its certificate waits. Existing sites with valid certificates are unaffected while that component is degraded.
How long do Pantheon incidents usually last?
There is no fixed figure, and the honest answer is that it depends which component is affected. Pantheon publishes its own incident history on the status page, which is the only reliable guide to typical duration for the component you care about. Read the past incidents for that specific row rather than the platform average.

How we measure this

  • We request Pantheon's public endpoint every 6 hours from Fly.io regions across six continents — 8 of them answered the most recent check.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where Pantheon publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when Pantheon goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from the same 18 regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required