You open your browser, type in your URL, and nothing loads. Or you see an error message you have never encountered before. Your first instinct is to call someone. That is understandable. But there are a few things worth checking first, because the answer might be simpler than you think.

For businesses in Singapore, a website outage during office hours means lost enquiries, missed sales, and a hit to credibility. The faster you can narrow down what is happening, the faster it gets resolved.


01

The most common reasons sites go down.

Hosting issues. Your web host is a server, and servers have downtime. Scheduled maintenance, hardware failures, or resource limits on shared hosting plans can all take your site offline without warning. In Singapore, many SMEs use shared hosting where one overloaded neighbour can affect your site.

DNS problems. Your domain name points to a specific server. If DNS records are misconfigured, recently changed, or if your domain registration has lapsed, browsers simply cannot find your site. The site is fine. The address pointing to it is not.

Expired SSL certificate. Modern browsers block access to sites with expired SSL certificates. Your site is not actually down, but visitors see a full-page security warning and most will leave immediately. For Singapore businesses running e-commerce, this is especially damaging.

Plugin or theme conflict. A recent update to a plugin, theme, or your CMS core can cause a fatal error. The result is often a white screen or a 500 Internal Server Error. Nothing looks broken from the backend because you cannot reach the backend either.

Server overload. A sudden spike in traffic, a runaway script, or a poorly optimised database query can overwhelm your server. This is common during product launches, media coverage, or sale events.

DDoS attack. Distributed denial-of-service attacks flood your server with fake traffic until it cannot respond to real visitors. While less common for small businesses, it does happen, particularly to sites without basic security headers or a CDN.

Database errors. Your site relies on a database to serve content. A corrupted table, a failed migration, or a full disk on the database server will bring everything to a halt. You will typically see "Error establishing a database connection" or similar.

What your visitors see
yourbusiness.com.sg

503

Service Temporarily Unavailable

The server is temporarily unable to service your request
due to maintenance downtime or capacity problems.

!

Server not responding

This page is not working. yourbusiness.com.sg is currently unable to handle this request. HTTP ERROR 503.

Potential causes: hosting outage, server resource limit reached, or a backend process has crashed.


02

What to check yourself first.

Is it just you? Visit downforeveryoneorjustme.com and enter your URL. If the site is up for everyone else, the issue is on your end. Try a different browser, clear your cache, or switch from Wi-Fi to mobile data.

Check your hosting provider's status page. Most hosts (SiteGround, Cloudways, AWS, DigitalOcean) publish real-time incident reports. If there is an ongoing outage, you will see it there. No action needed on your part except to wait.

Clear your browser cache. Sometimes you are seeing a cached version of an error that has already been resolved. Hard refresh with Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac).

Check your SSL certificate. Click the padlock icon in your browser's address bar. If the certificate has expired, that is your answer. Most hosting panels let you renew it in a few clicks.

Look at your recent changes. Did you update a plugin, edit a file, or change a setting in the last 24 hours? If yes, that is almost certainly the cause. Reverting that change, if you can access your hosting file manager or have a backup, is the fastest fix.


03

When it is time to call a professional.

If you have checked the basics and the site is still down, it is time to get help. Specifically:

Your hosting status page shows no issues, but your site is still unreachable. You see a white screen or a 500 error with no clear explanation. You cannot access your admin panel at all. The site loads but critical functionality (forms, checkout, login) is broken. You suspect a security breach or DDoS attack.

At this point, troubleshooting without server-level access or diagnostic tools will cost you more time than it saves. A developer can access your server logs, trace the error, and identify the root cause.

Every hour your site is down, you are losing enquiries, search ranking, and customer trust. The cost of a quick repair is almost always less than the cost of staying offline.
What to check before calling a developer
01 Test from another device. Use your phone on mobile data to confirm the site is truly down, not just a local cache or network issue.
02 Check your host's status page. Look for scheduled maintenance or active incidents. If the host is down, there is nothing a developer can do until it is resolved.
03 Note any recent changes. Write down anything you updated, installed, or edited in the past 48 hours. This saves your developer significant diagnostic time.
04 Screenshot the error. Capture exactly what you see. "Error establishing a database connection" tells a developer something very different from a blank white page.
05 Check your SSL certificate. Click the padlock in your address bar. If it says expired or not secure, your host's control panel can usually renew it directly.
04

Why speed matters.

Downtime is not just an inconvenience. For Singapore businesses, it has real costs. Every hour offline means potential customers hitting a dead end and going to a competitor instead. Google notices too. Extended downtime can cause your search rankings to drop, and recovering those positions takes weeks.

If your site handles transactions, the financial impact is immediate and measurable. Even for service-based businesses, a site that is down during business hours signals unreliability to prospects who were ready to enquire.

The best approach is a combination of monitoring and fast response. Set up a free uptime monitor (UptimeRobot or similar) so you know the moment your site goes down, not hours later when a customer tells you. And have a developer on call who knows your site and can respond quickly.

Site down right now?

Send us your URL and a screenshot of what you see. We will diagnose the issue and get you back online. No obligation.

Get in touch