By country

Qatar, live service status

QA 11 services
Operational
0
Degraded
0
Down
0
Pending
11
What this is

Most-used services in Qatar, banks, telecoms, broadcasters, e-commerce, streaming. Each card is probed every 5 minutes using 4 independent probe methods. Click any card to see the full multi-method check.

Banking4
Commercial Bank Qatar
cbq.qa
-
Qatar Islamic Bank
qib.com.qa
-
Doha Bank
dohabank.qa
-
Qatar National Bank
qnb.com
-
Shopping2
Snoonu
snoonu.com
-
Rafeeq
rafeeq.qa
-
Telecom2
Ooredoo Qatar
ooredoo.qa
-
Vodafone Qatar
vodafone.qa
-
Streaming1
beIN Sports
bein.com
-
Email & Web1
Hukoomi
hukoomi.gov.qa
-
Travel1
Qatar Airways
qatarairways.com
-

Methodology

Probe
We send a GET request to the target URL with each probe method and time the full response.
Counts as DOWN
Every probe method fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
Counts as DEGRADED
At least one probe method succeeds but at least one fails, the site is up but blocking or mishandling a specific request type.
Detail
Per-method results include HTTP status code, response time, and best-effort DNS / connect / TLS / first-byte phase timings when the Node HTTP client exposes them.
Cadence
Every 5 minutes, in parallel across 4 independent probe methods (HTTP/1.1 with strict TLS, HTTP/2, a browser User-Agent GET, and a curl-style HEAD) from our edge network. We check probe diversity, not geography — if a site blocks a non-browser User-Agent or only speaks HTTP/1.1, the four cards show it.
Rate-limited targets
If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status, we do not flood the target to confirm the outage.
Data source
Our verdict is based on direct multi-method probes, every result above is a live network request, never a Twitter mention or DownDetector aggregate. User reports, when shown, appear separately below as a supplementary signal and are never used to determine the up/down verdict.