DreamHost Outage History

DreamHost experienced network connectivity issues affecting their main website (dreamhost.com) for 40 minutes. System administrators identified the root cause and implemented a fix to restore access. The team monitored the situation to ensure stability was fully restored.

DreamHost experienced MySQL connectivity issues affecting the phpMyAdmin service for databases hosted in their PDX1 data center. The incident lasted 2.1 hours and was classified as minor severity. The Technical Operations team investigated and resolved the connectivity problems.

DreamHost experienced a major service disruption affecting their web panel for 16 minutes on March 25, 2026. The outage prevented users from accessing the web panel interface used for account management and hosting controls. The technical team investigated the root cause and successfully restored service.

DreamHost experienced a major service disruption affecting their web panel for 12 minutes on March 24, 2026. The outage prevented users from accessing the web panel interface used for account and service management. The technical team investigated the root cause and successfully restored service.

DreamHost experienced degraded performance affecting some shared servers in their PDX1/IAD1 network locations, causing slowdowns for hosted websites and services. The Technical Operations team investigated the root cause and worked to restore normal functionality on the affected machines. The incident lasted 8.2 hours with ongoing remediation efforts throughout the duration.

DreamHost experienced degraded performance on some shared servers in their PDX1/IAD1 network locations, causing slowdowns for affected customers. The Technical Operations team identified the root cause and actively worked to restore normal functionality. The incident was resolved after 2.2 hours.

DreamHost experienced connectivity issues affecting VPS servers hosted on the iad1-vpshost-e1-13 host machine for 2.4 hours. The technical operations team identified the root cause and implemented a resolution. Service recovery was actively monitored following the fix.