Operational Pantheon status
pantheon.io · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
No sign of a widespread Pantheon problem right now; every source we read is quiet.
confidence: medium Vendor: operational · users: normal · routing: no data.
- Vendor status page Operational · 2 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: Customer Sites
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 38 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | not seen | n/a |
Evidence
- Official page: Operational (“All Systems Operational”). evidence confidence: high
- Vendor stage: resolved on “Drupal core critical security update (CVE-2026-108097)”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Pantheon's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: operational · users: normal · routing: no data. Vendor status and outside signals roughly agree.
Who depends on whom
We don't map other services that depend on Pantheon. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Nothing points to a broad problem. If it's broken for you, try “Is it just me?” and check your own network first.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Pantheon, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
Any new vendor incident, a jump in user reports above baseline, or trouble at the providers Pantheon may depend on.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Pantheon. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Drupal core critical security update (CVE-2026-108097)
none resolved · started · resolved
5 updates
- monitoring
A <a href="https://www.drupal.org/sa-core-2026-014">Drupal core security release</a> is now available for <strong>CVE-2026-108097</strong> (risk 19/25). It fixes a critical remote code execution vulnerability in the Field UI module.<br>Drupal core alone is not directly exploitable, but several exploit paths exist through contributed modules, including at least one path that does not require authentication. Custom code can also expose the vulnerable functionality. <h5>Action required</h5> Update your Drupal sites to a patched release as soon as possible: <strong>Drupal 11.4.10</strong> <strong>Drupal 11.3.19</strong> <strong>Drupal 10.6.19</strong> Drupal 12.0.0-alpha1 through 12.0.0-beta1 are also affected. See the <a href="https://www.drupal.org/sa-core-2026-014">Drupal security advisory</a> for Drupal 12 remediation details. Drupal 11.2.x and earlier, Drupal 10.5.x and earlier, Drupal
- monitoring
We are aware of the Drupal 7 release and will update this incident when it is available as an upstream update.
- monitoring
Drupal 7.107 is now available as an upstream update. Customers running Drupal 7 applications should update to Drupal 7.107 as soon as possible. To apply the update, use the Drupal core update workflow in the Pantheon Dashboard.
- monitoring
Drupal 10 and 11 security updates are available through Integrated Composer, and the Drupal 7.107 upstream security update has been released. Release notes are available for both update paths: <a href="https://docs.pantheon.io/release-notes/2026/10/drupal-core-security-update">Drupal core security update</a> and <a href="https://docs.pantheon.io/release-notes/2026/10/drupal-7-107-security-update">Drupal 7.107 security update</a>.
- resolved
<b>Drupal Steward</b> protection is in place for some known attack vectors related to <b>CVE-2026-108097</b>. This reduces exposure, but does not cover every possible exploit path or replace applying the security update. No customer impact is currently reported, and we continue to monitor. Patched Drupal 10 and 11 releases are available through Integrated Composer, and Drupal 7.107 is available as an upstream update. Please update affected sites as soon as possible. If you cannot update immediately, uninstall the core Field UI module (field_ui) as a temporary mitigation. See the <a href="https://docs.pantheon.io/release-notes/2026/10/drupal-core-security-update">Drupal core security update</a> and <a href=-"https://docs.pantheon.io/release-notes/2026/10/drupal-7-107-security-update">Drupal 7.107 security update</a> for details.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.