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: Next.js, Customer Sites
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 8 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 “Next.js site creation unavailable”. 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
Next.js site creation unavailable
major resolved · started · resolved
10 updates
- investigating
We are investigating an issue that prevents the creation of new Next.js sites. Existing Next.js sites are still available. WordPress and Drupal sites are unaffected. We will post an update as soon as we have more information.
- investigating
We are continuing to investigate an issue that prevents the creation of new Next.js sites. Existing Next.js sites are still available. WordPress and Drupal sites are unaffected. Our engineering team has narrowed down where the problem is and is working on getting site creation back online. If you need immediate assistance, please open a support chat with us or email [email protected]. Thank you for your patience. We will post another update in 1 hour, or sooner if there is a change.
- investigating
We are continuing to investigate an issue that prevents the creation of new Next.js sites. Existing Next.js sites are still available. WordPress and Drupal sites are unaffected. Our engineering team is actively working on getting site creation back online. If you need immediate assistance, please open a support chat with us or email [email protected]. Thank you for your patience. We will post another update in 1 hour, or sooner if there is a change.
- identified
We have identified the cause of the issue that prevents the creation of new Next.js sites, and our engineering team is working on a fix. Site creation is still unavailable. Existing Next.js sites are still available. WordPress and Drupal sites are unaffected. If you need immediate assistance, please open a support chat with us or email [email protected]. Thank you for your patience. We will post another update in 1 hour, or sooner if there is a change.
- identified
We continue to work on a fix for the issue that prevents the creation of new Next.js sites. Site creation is still unavailable. Existing Next.js sites are still available. WordPress and Drupal sites are unaffected. If you need immediate assistance, please open a support chat with us or email [email protected]. Thank you for your patience. We will post another update in 1 to 2 hours, or sooner if there is a change.
- identified
We are continuing work on a fix for the issue preventing the creation of new Next.js sites. New Next.js site creation remains unavailable. Existing Next.js sites are available, and WordPress and Drupal sites are unaffected. If you need immediate assistance, please open a support chat with us or email [email protected]. We’ll post another update in 1 to 2 hours, or sooner if there is a change. Thank you for your patience.
- identified
The issue affecting the creation of new Next.js sites is ongoing, we are working on a fix. Existing Next.js sites remain available, and WordPress and Drupal sites are unaffected. If you need immediate assistance, please open a support chat with us or email [email protected]. We’ll post another update within 1 to 2 hours, or sooner if there is a change. Thank you for your patience.
- monitoring
The fix has been deployed to production, and a new Next.js site was created successfully during verification. We are monitoring the service to confirm continued stability before resolving the incident. Existing Next.js sites remain available, and WordPress and Drupal are unaffected. If you need immediate assistance, please open a support chat with us or email [email protected]. We’ll post another update as verification continues. Thank you for your patience.
- monitoring
Production verification confirmed a successful new Next.js site creation after the fix was deployed. We are keeping the incident in Monitoring while we check that the fix remains stable. Existing Next.js sites remain available, and WordPress and Drupal are unaffected. We’ll post another update when monitoring is complete, or sooner if the status changes. If you need immediate assistance, please open a support chat with us or email [email protected]. Thank you for your patience.
- resolved
This incident has been resolved.
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.