based on user reports and queries over the last 24 hours
U1 HOST outage statistics
If the hosting control panel won''t open, start with the basics: clear your browser cache, try a different browser or device. Sometimes the issue is a stale DNS record — flush the local DNS cache with ipconfig /flushdns on Windows or sudo dscacheutil -flushcache on macOS. If you recently updated your domain''s nameservers, allow up to 24 hours for full propagation.
Unstable FTP sessions are usually caused by a firewall blocking passive mode ports. Switch your FTP client (FileZilla, WinSCP) from passive to active mode, or ask your network admin to open the port range specified in U1 HOST documentation. Also check that you''re using the correct FTP hostname — not the domain name, but the server address from your hosting account details.
- Make sure the certificate is issued for the exact domain variant you''re accessing (with or without www)
- Check the expiry date in your browser''s certificate viewer
- If you just installed the cert, wait 10–15 minutes and do a hard refresh (Ctrl+Shift+R)
- Mixed content warnings appear when some page resources still load over HTTP — fix asset URLs in your CMS settings
First verify that MX records point to the correct mail server listed in your U1 HOST account. If outbound mail is failing, check whether port 25 is blocked by your local ISP — use port 587 with STARTTLS instead. Incoming mail delays are often caused by overly aggressive spam filters; whitelist the sender''s domain in your mailbox settings.
- Confirm the DB hostname, username, and password in your CMS config file match what''s shown in the hosting panel
- Check if the database is listed as active — a suspended account will drop all connections
- If the site was recently migrated, the DB host field may still contain the old server address
Run a traceroute (tracert on Windows, traceroute on Linux/macOS) to the server IP to identify where the delay occurs. If the bottleneck is on your local network or ISP side, there''s nothing the hosting provider can fix remotely. Latency spikes during peak hours sometimes indicate shared resource contention — consider upgrading to a plan with dedicated resources.
U1 HOST
Your message will be published in about
5 minutes
Service administration will see your message