Skip to content
Business, Your Website Was Down and Nobody Told You: The ₹0 Fix (2026)
Business

Your Website Was Down and Nobody Told You: The ₹0 Fix (2026)

RRRavi Rai9 min read

₹0. That is what it costs to find out your website is down before a customer does, and most of the business owners I meet have never set it up. They find out the other way: a WhatsApp from a regular saying the site is not opening, or a quiet week on the enquiry form that turns out not to have been quiet at all.

I run a web development agency, so a fair share of my inbox is some version of "site nahi khul rahi". By the time the message reaches me the site has usually been down for hours, sometimes days. The outage itself is rarely the expensive part. The not knowing is. This post is about closing that gap for free, in about ten minutes, and about what to do in the first hour when the site really is down.

First, is it actually down? The two-minute check

Before you call anyone, make sure the problem is the website and not your own connection. Half the panicked messages I get are an office Wi-Fi issue or a browser that cached an old error.

  1. Open the site on your phone with Wi-Fi switched off, on mobile data. If it loads there, the site is fine and the problem is your office network.
  2. Try it in an incognito or private window. If it loads there, your normal browser is holding on to an old copy or a stale login.
  3. Type the address into a free third-party checker such as downforeveryoneorjustme.com. It fetches the site from another network and tells you whether the outage is real.
  4. Look at the exact error. A blank page with "This site can't be reached" is a domain or server problem. A page that loads but says "Error establishing a database connection" or shows a 500 or 503 number is the hosting or the application. A red "Not secure" warning is the SSL certificate, which we covered in the Not Secure fix guide.
  5. Check whether the domain is still yours. Search the domain on any WHOIS lookup site and read the expiry date. An expired domain looks exactly like a dead server, and it is the one you can lose for good.

Write down what you saw and at what time. Whoever fixes it will ask, and "it just doesn't open" is the least useful thing you can send them.

What an hour of downtime costs you, honestly

Nobody keeps this number, so let me give you the formula and a worked example. Put your own figures in; the maths is simple on purpose.

Daily visitors  x  enquiry or order rate  x  average order value
= what the site earns in a day

Divide by 24 for the cost of one hour down.

Example: a furniture showroom site in Jaipur
  300 visitors a day  x  2% enquiry rate  =  6 enquiries a day
  1 in 3 enquiries becomes an order worth about Rs 8,000
  = roughly Rs 16,000 of orders a day, or about Rs 670 an hour

A six-hour outage on a weekday: around Rs 4,000 in orders.
The same six hours during a festival sale you paid ads for: several times that,
because the ad clicks still cost money and land on a dead page.

Two things the formula misses. The first is the customer who tried once, got an error, and bought from the next result on Google. You never see that person again and they never tell you why. The second is the ad money. If you run Google or Meta ads to the site, every click during the outage is paid for and wasted, and the platforms do not refund it.

The point is not that downtime is a catastrophe. For most small businesses a few hours a year is survivable. The point is that an outage you do not know about can run for a whole weekend, and that a free alert turns it into a twenty-minute problem.

Why small business websites in India actually go down

In the rescue work we do, the causes are boringly consistent. Hardly any of them are hackers.

  • The hosting renewal was not paid. The reminder went to the developer's email, or to a Gmail nobody checks, and the host suspended the account. Our renewal charges guide lists what you should be paying and when.
  • The domain expired. Same story, worse outcome, because after the grace period someone else can register it. If the domain is in your developer's name, read who owns your website tonight.
  • The SSL certificate expired. Free certificates last 90 days and renew automatically until the day the automation silently breaks. Browsers then show a full-page warning and most visitors leave.
  • A WordPress plugin or theme update broke the site. Auto-updates are on, a plugin was abandoned by its author, and the next update took the site down with a white screen.
  • Shared hosting hit its limit. Cheap plans cap CPU and memory. A traffic spike from a festival offer, or a badly written plugin, pushes the account over and the host throttles or suspends it for the day.
  • Someone changed DNS. A new email provider, a new developer, a migration, and one wrong record sends the domain nowhere. DNS changes take hours to settle, so the site works for you and fails for your customers.
  • The developer's server bill went unpaid. The site was running on a VPS the developer rented for you, under their account. They stopped paying, or stopped answering, and the machine was deleted along with the site.

Notice how many of these are a reminder email that reached the wrong person. Fixing that is cheaper than any monitoring tool: make sure the registrar, the host and the certificate alerts all go to an address you read.

The ₹0 fix: free uptime monitoring in ten minutes

An uptime monitor is a service that loads your website every few minutes from its own servers and messages you the moment it fails. The two I set up for clients both have genuinely free plans with no card required, and either one is more than a small business needs.

  • UptimeRobot: the free plan gives you 50 monitors checked every 5 minutes, with alerts by email and through its phone app. SMS and WhatsApp alerts are paid extras; the app notification is free and arrives just as fast.
  • Better Stack (the old Better Uptime): the free plan gives 10 monitors checked every 3 minutes, email and app alerts, and a public status page if you want one.

The setup, which needs no developer:

  1. Create the account with an email address you actually read, not the developer's. Install the phone app and allow notifications.
  2. Add a monitor of type HTTP(S) for your homepage, with the full address including https://. Name it something you will recognise at 2 AM.
  3. Add a second monitor for the page that makes you money: the contact page, the enquiry form, or the checkout. Homepages sometimes stay up while the form behind them is broken.
  4. If the tool offers a keyword check, use it on the money page: tell it to look for a word that only appears when the page loads properly, such as your phone number. A page that returns an error message still "loads", and the keyword check catches that.
  5. Turn on SSL expiry alerts and, where offered, domain expiry alerts. Set them to warn you 14 days out.
  6. Add a second contact, such as a colleague or your developer, so an alert does not depend on one phone being charged.
  7. Test it. Change the homepage monitor to a wrong address for one check and confirm the alert arrives. Then put it back.

That is the whole job. From that moment on, an outage becomes a notification within five minutes instead of a customer complaint within five days. If your site is on a maintenance contract, the agency should already be doing this and showing you the monthly uptime; the AMC cost guide explains what a fair contract includes.

What "99.9% uptime" on a hosting plan actually means

Every hosting page promises a percentage. Translate it into minutes before you decide it sounds good.

Promised uptime    Allowed downtime per month    Per year
99%                about 7 hours 18 minutes      about 3.7 days
99.5%              about 3 hours 39 minutes      about 1.8 days
99.9%              about 44 minutes              about 8.8 hours
99.95%             about 22 minutes              about 4.4 hours
99.99%             about 4 minutes               about 53 minutes

Two honest notes. First, most shared hosts write 99.9% and quietly deliver less, and the only way you will know is your own monitor's monthly report. Second, the credit for a missed promise is usually a percentage of that month's hosting fee, which on a ₹3,000-a-year plan is pocket change. The number is a marketing claim, not insurance. Your monitor is the insurance.

What to send your developer or host when it is down

The fastest fixes I have seen started with a message that had everything in it. Copy this, fill the brackets, and send it to whoever looks after the site. If you do not know who that is, that is the first problem to fix after the site is back.

Site: [www.yourbusiness.in]
Since: [time you first noticed, and the time of the monitor alert if you have one]
What I see: [exact error text, or "blank page", or "Not secure warning"]
Where I checked: [phone on mobile data / incognito / downforeveryoneorjustme]
Recent changes: [new plugin, new email provider, renewal due, anything in the last week]
Domain expiry: [date from WHOIS]
Hosting: [company name, and whether the login is mine]
Please reply with: what broke, the fix, and the time it will be back.

Ask for the cause in writing once it is fixed. "Server issue" is not a cause. If the same cause comes back twice, it is time to change either the host or the arrangement.

Red flags in how your site is being looked after

  • You cannot name the hosting company, or you can but the login belongs to someone else.
  • Renewal reminders for the domain, hosting or certificate go to an address you do not read.
  • The site has gone down more than twice this year and nobody has told you why.
  • Your maintenance contract mentions "monitoring" but you have never seen an uptime figure.
  • The developer is the only person who gets alerts, and the developer is hard to reach.
  • Your site runs on a server rented under the developer's personal account rather than yours.

The short version

  • Check from mobile data, incognito and a third-party checker before you panic.
  • Downtime cost is daily visitors times enquiry rate times order value, divided by 24. Ad spend during an outage is pure waste.
  • Most outages are an unpaid renewal, an expired certificate, a broken update or a hosting limit. Point every reminder email at an address you read.
  • Set up UptimeRobot or Better Stack on their free plans: homepage, money page, keyword check, SSL expiry alert, a second contact. Ten minutes, ₹0.
  • A 99.9% promise means up to 44 minutes down a month, and the credit for missing it is tiny. Your own monitor is the only real record.
  • When it is down, send the template above and ask for the cause in writing.

Send us your website address. We will tell you, free, whether it is up, whether the certificate and domain are close to expiring, and how fast it loads on an Indian mobile connection. No pitch unless you ask for one.

Get a free website check

Frequently asked questions

How do I check if my website is down for everyone or just me?
Open it on your phone with Wi-Fi off, then in an incognito window, then on a third-party checker such as downforeveryoneorjustme.com, which loads the site from another network. If all three fail, it is really down. If only your office fails, the problem is your connection or your browser's cached copy.
Is uptime monitoring really free?
Yes, for what a small business needs. UptimeRobot's free plan checks up to 50 addresses every 5 minutes and alerts you by email and its phone app. Better Stack's free plan checks 10 addresses every 3 minutes. Neither asks for a card. SMS and WhatsApp alerts are paid extras on both, but the app notification is free and arrives just as quickly.
What does 99.9% uptime mean in hours?
About 44 minutes of downtime allowed per month, or roughly 8 hours 46 minutes a year. 99% allows about 7 hours 18 minutes a month, and 99.5% about 3 hours 39 minutes. The compensation for missing the figure is normally a small credit on that month's hosting fee, so treat the percentage as a claim to verify with your own monitor, not a guarantee.
My website shows 'Not secure' and will not open. Is that the same as being down?
Not quite. The server is usually fine; the SSL certificate has expired or was set up wrongly, and the browser is blocking the page to protect visitors. For most sites the certificate is free and renews automatically, so the fix is to have the host or developer renew it and then check why the automatic renewal failed. Our Not Secure guide walks through it.
Who should I call when my website is down?
The person or company that hosts it. If that is your developer, send them the message template in this post with the exact error, the time, and any recent changes. If you do not know who hosts the site, look up the domain on a WHOIS site for the registrar and ask them which nameservers it uses; that tells you where the site lives. Then fix the bigger problem: make sure the hosting, domain and certificate accounts are in your name with reminders going to you.
RR
Written by
Ravi Rai

Founder of buildbyravirai, a web development agency based in Noida, India. Building websites, web apps and mobile apps in Next.js, NestJS, Shopify and WordPress since 2021, for clients in India, the US, Canada and the UK.

The commercial side

Software decisions are budget decisions

Most of what goes wrong on a build is decided before anyone opens an editor: unclear scope, a price that moves, no written agreement about who owns what. We settle all three in writing first.