Regional reroute
Affected region? A VPN exit node in a healthy region usually restores access.
Site web · mobily.com.sa
Mobily est-il en panne ?
mobily.com.sa
isp
SA
DÉGRADÉ
Checked 1s ago
4/4 regions returned data
every 5 min · HTTP probe
direct probe, not crowd-reported
Résultats par région
US East
EN PANNE
—
ETIMEDOUT
US West
EN PANNE
—
ETIMEDOUT
Europe
OPÉRATIONNEL
1210 ms
HTTP 302
Asia
EN PANNE
—
ETIMEDOUT
Détails HTTP
- HTTP status
- 302
- Response time
- 1210 ms
- Region consensus
- 1/4 reachable
- 24h success rate
- 0% (0/1 probes)
Décomposition des temps
- DNS lookup
- 181 ms
- TCP connect
- 254 ms
- TLS handshake
- 526 ms
- First byte
- 249 ms
- Total
- 1210 ms
Réseau
- Host
- mobily.com.sa
- Port
- 443
- Transport
- HTTPS
Que signifie ce résultat
3/4 regions reported issues (US East, US West, Asia).
The outage appears partial — users in healthy regions are unaffected. If you're in an affected region, try a VPN exit in a healthy one.
Que faire ensuite
Wait and retry
Partial outages often resolve within 10-15 minutes. Reload to re-check.
Report
If you're seeing the issue, you're not alone — others can find this page via search.
FAQ
Why is Mobily down right now?
Outages typically come from CDN/DNS issues, failed deploys, regional routing problems, or DDoS. We can't see Mobily's internal cause — we only confirm reachability from each monitoring region. If all 4 regions failed, it's a confirmed outage on Mobily's side. If only some failed, the impact is regional.
Is Mobily down for everyone or just me?
Look at the per-region grid above. If every region succeeded, the issue is local to your network — flush DNS, switch networks, or disable your VPN. If two or more regions failed, the outage is on Mobily's side.
How often does isitdown.io re-check Mobily?
Every 5 minutes via background HTTP probes from US East, US West, Europe, and Asia. You can also re-run on demand by reloading — the verdict above reflects the latest probe.
Status badge
Embed a live status badge on your site, README, or status page. Updates automatically — same status-aware SVG the rest of isitdown.io uses.
<a href="https://isitdown.io/website/mobily.com.sa"><img src="https://isitdown.io/badge/mobily.com.sa.svg" alt="Mobily status"></a>
Voir aussi · isp
Méthodologie
- Sonde
- We send a GET request to the target URL from each region and time the full response.
- Compté comme EN PANNE si
- Every region fails the request (connect refused, DNS error, timeout, or HTTP 5xx).
- Compté comme DÉGRADÉ si
- At least one region succeeds but at least one fails — the outage is partial or regional.
- Détail
- Per-region 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 monitoring regions (US East Virginia, US West Oregon, Europe London, Asia Singapore).
- Cibles limitées en débit
- 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.
- Source des données
- Direct probes from our monitoring infrastructure. We do not aggregate crowd reports, Twitter mentions, or DownDetector signals — every result on this page is a live network request.