An Om Sai Technology company Infrastructure expertise. Hosting made accessible.
Skip to content
Service status

All 3 published components are responding.

What you see here is measured by our own monitors, on the interval shown under each component, and published as recorded. Nothing on this page is typed in by hand except incident notes, which are signed by the person who wrote them.

Responding · last check 5 hours ago
Components

Last 90 days, one cell per day

Green: every check that day passed. Amber: at least one check was degraded. Red: at least one check failed. Grey: no check was recorded that day.

Client portal

Responding
Checked every 5 min · last 5 hours ago Last response 581 ms 53 of 90 days have data Up to 20 min down (failed checks × interval) 4 public incidents

Ordering & checkout

Responding
Checked every 5 min · last 5 hours ago Last response 707 ms 53 of 90 days have data Up to 10 min down (failed checks × interval) 2 public incidents

Website

Responding
Checked every 5 min · last 5 hours ago Last response 1637 ms 53 of 90 days have data Up to 10 min down (failed checks × interval) 2 public incidents
A green day means our checks passed from where we run them. It does not mean every customer saw the same thing, and it is not an uptime guarantee — the commitment we make, if any, is on the service level agreement page.
Incidents

Public incidents, last 90 days

Website is DOWN

Resolved

Critical · started 08 Oct 2026, 06:04 · resolved 08 Oct 2026, 06:10 (5 minutes) · Website

Monitor Website (billme.omlinux.in) failed its health check.

  1. Resolved · 08 Oct 2026, 06:10
    Auto-resolved: host is responding again
  2. Investigating · 08 Oct 2026, 06:04
    Auto-detected: host unreachable

Client portal is DOWN

Resolved

Critical · started 05 Oct 2026, 09:49 · resolved 05 Oct 2026, 09:55 (5 minutes) · Client portal

cURL error 28: Failed to connect to billme.omlinux.in port 443 after 7606 ms: Connection timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://billme.omlinux.in/client/login

  1. Resolved · 05 Oct 2026, 09:55
    Auto-resolved: host is responding again
  2. Investigating · 05 Oct 2026, 09:49
    Auto-detected: cURL error 28: Failed to connect to billme.omlinux.in port 443 after 7606 ms: Connection timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://billme.omlinux.in/client/login

Client portal is DOWN

Resolved

Critical · started 24 Sep 2026, 10:01 · resolved 24 Sep 2026, 10:07 (5 minutes) · Client portal

cURL error 28: Operation timed out after 15001 milliseconds with 6368 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://billme.omlinux.in/client/login

  1. Resolved · 24 Sep 2026, 10:07
    Auto-resolved: host is responding again
  2. Investigating · 24 Sep 2026, 10:01
    Auto-detected: cURL error 28: Operation timed out after 15001 milliseconds with 6368 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://billme.omlinux.in/client/login

Pricing page is DOWN

Resolved

Critical · started 24 Sep 2026, 09:26 · resolved 24 Sep 2026, 09:31 (5 minutes) · Pricing page

cURL error 28: Operation timed out after 15001 milliseconds with 6368 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://billme.omlinux.in/pricing/1

  1. Resolved · 24 Sep 2026, 09:31
    Auto-resolved: host is responding again
  2. Investigating · 24 Sep 2026, 09:26
    Auto-detected: cURL error 28: Operation timed out after 15001 milliseconds with 6368 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://billme.omlinux.in/pricing/1

Client portal is DOWN

Resolved

Critical · started 24 Sep 2026, 09:19 · resolved 24 Sep 2026, 09:25 (5 minutes) · Client portal

cURL error 28: Operation timed out after 15000 milliseconds with 6368 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://billme.omlinux.in/client/login

  1. Resolved · 24 Sep 2026, 09:25
    Auto-resolved: host is responding again
  2. Investigating · 24 Sep 2026, 09:19
    Auto-detected: cURL error 28: Operation timed out after 15000 milliseconds with 6368 bytes received (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://billme.omlinux.in/client/login

Pricing page is DOWN

Resolved

Critical · started 22 Sep 2026, 09:39 · resolved 22 Sep 2026, 09:45 (5 minutes) · Pricing page

That host name does not resolve to a public address.

  1. Resolved · 22 Sep 2026, 09:45
    Auto-resolved: host is responding again
  2. Investigating · 22 Sep 2026, 09:39
    Auto-detected: That host name does not resolve to a public address.

Client portal is DOWN

Resolved

Critical · started 22 Sep 2026, 09:38 · resolved 22 Sep 2026, 09:44 (5 minutes) · Client portal

That host name does not resolve to a public address.

  1. Resolved · 22 Sep 2026, 09:44
    Auto-resolved: host is responding again
  2. Investigating · 22 Sep 2026, 09:38
    Auto-detected: That host name does not resolve to a public address.

Website is DOWN

Resolved

Critical · started 22 Sep 2026, 09:36 · resolved 22 Sep 2026, 09:42 (5 minutes) · Website

That host name does not resolve to a public address.

  1. Resolved · 22 Sep 2026, 09:42
    Auto-resolved: host is responding again
  2. Investigating · 22 Sep 2026, 09:36
    Auto-detected: That host name does not resolve to a public address.
One caveat. This page is served by the same platform it reports on. If it will not load, that is itself a signal — the WhatsApp line on this site runs independently of our servers.

Machine-readable copy: /status.json · Commitments, if any: service level agreement

Something looks wrong on your service?

Open a ticket from the client portal, or message us. A real person reads it.

Client portal → WhatsApp
OMLINUX

The hosting-sales subsidiary of Om Sai Technology.

Meet our infrastructure parent
Chat with us