Loading…
🛡️ Suspected attacks
💬 Ask the platform
Recent events
Monitoring map and colour guide
How the Ministry sites reach visitors around the world
Each dot is a monitoring server in a different country. It opens the Ministry sites every 5 minutes, just like a real visitor. The colour of each line shows how the sites look from that country.
How does it work? We have monitoring servers in several countries. Every 5 minutes each one opens the Ministry sites the way a real visitor would and records: did the site open, and how long did it take? If a site fails from every country, the problem is the site itself. If it fails from only one country, the problem is most likely the internet route from that country.
📊 Status matrix — latest measurement from each vantage point
Healthy Warning Failure — click any cell to see the full path and details
📍 Measured from inside Saudi Arabia (RIPE Atlas)
The monitoring servers are outside the Kingdom. This check asks volunteer RIPE Atlas probes inside Saudi Arabia to open a secure connection (TCP + TLS) to each site, so you can tell whether visitors in the Kingdom can reach it. It tests the connection and the certificate, not the page content.
🔧 Planned maintenance
During a maintenance window the site's alerts are paused and any downtime is left out of the SLA. Windows you record after they have started are marked, so the exclusion can be reviewed.
🕓 Recent incidents (last 30 days)
🔐 SSL certificates
🔗 Network quality between vantage points (agent-to-agent)
Show
Latency, loss, jitter and MOS (voice quality, 1–5) on the links between your own locations.
🌐 Domains — expiry, name servers, DNSSEC
Every monitored site's domain is checked automatically. A domain that expires or loses its name servers takes all its sites down at once, so the platform warns you 60, 30, 14, 7, 3 and 1 day before it expires, and whenever something changes.
Loading…
⏱️ Availability
⏪ Time travel — replay the last 24 hours
Viewing: live back to live
⏱️ Where the time goes
🛣️ Route — how this monitor reaches the site
Hops are grouped by the network that owns them. Click a hop for its details.
Router names come from the recorded hostname. Registration country identifies the network's registration, not the router's physical location. RTT is the round-trip time from the monitor to that hop.
🕸️ All routes side by side
One row per country: the monitor's hosting network, the hand-over point, and where the site answers from.
🧭 Transaction test (user journey)
📈 Last 24 hours (response time, ms)
🌐 All vantage points compared
⚙️ Settings
Sites, alerts, users, the public status page, background jobs, storage and the audit log. Only administrators see this tab; everyone else uses the other tabs.
🩺 Monitoring readiness
Is monitoring really working right now? The page opening is not enough: this checks the monitoring servers, the freshness of the readings, the disk and the background jobs. An outside watcher can poll /readyz: it answers 200 while monitoring works and 503 when it is blind (/healthz only says the program is alive).
Loading…
＋ Add a website to monitor
Advanced: transaction test (multi-step user journey)
One step per line — URL | expected text. Example:
https://mt.gov.sa | وزارةhttps://mt.gov.sa/login | تسجيل الدخول
🔔 Telegram alerts
Delivery log — what was sent to Telegram
Current alert level
When is a message sent? (confidence matrix)
Real-visitor data from Cloudflare only lowers an alert when it covers the same minutes as the failure, so a fresh outage is never hidden by older "all fine" numbers.
🌐 Status page for the help desk
A simple read-only page that shows every site's state, the last 30 days and the open incidents, so the help desk can answer callers without logging in. It needs the secret link and shows no technical details.
⚙️ Background jobs
Each job reports after every round. A job that has not succeeded for three rounds is marked “Late” — it may have stopped, even though the web page still opens.
🗄️ Data & storage
Detail is kept for a short time and summarised every hour, so the database stays small while SLA history and incidents are kept for years. Nothing is deleted before it has been summarised.
👥 Users
🗂 Service registry
Who owns each site, how important it is, when it matters and who to escalate to. The importance sets how long an outage may wait for somebody to take it (critical 5 min · high 10 · medium 15 · low 60). Sites in the same group can be filtered on the overview and reported together.
Loading…
🧾 Audit log
🖧 Network — the Ministry's side and the visitors' side together
SolarWinds shows the Ministry's own devices and links; Cloudflare shows what the visitors get; the monitors show the site from four countries. Read together they say where a problem is.
🌐 Sites: visitors and the network
📈 Visitors and links over the last hour
🔗 Key links
Internet and WAN links, found by their name (WAN, ISP, Internet, STC, Mobily …) or chosen by an administrator.
🚨 Active SolarWinds alerts
🖥️ Devices with a problem
🔌 Interfaces with a problem
🧩 Applications and load balancers
💽 Nearly full disks
🕘 Latest SolarWinds events
🧠 Diagnosis Center — why is a site having trouble?
🌍 Live visitor traffic to the Ministry sites
📋 Incident reports
An automatic, plain-language report for every outage: what happened, in what order, who was affected and who should act.
🔄 Recent changes
Changes the platform noticed in certificates, site addresses, network routes, Cloudflare and domains. When a site breaks, the changes just before it are the first thing to check.
Loading…
🔬 Details from Cloudflare
☁️ Cloudflare — real visitor traffic (last 60 min)
Reports
🔖 Saved reports
A saved report runs again with one press. It keeps a fixed reference number (for example MT-RPT-0001) and every Excel export adds a revision (…-R03), so a printed page can always be traced back.
Loading…
No report generated
📅 SLA this month
Each site's SLA target, the downtime allowed this month, what has been used so far and the forecast. Press Why? for the outages behind the numbers.
🕒 When do problems repeat?
Looks back over the last weeks for outages and slowness that return at the same time — the same weekday and hour. Planned maintenance is left out.
Loading…
📑 Hosting evidence file
Compares what the platform measured with your hosting contract and lists the outages that belong to the hosting side — ready to print or to attach to a claim. Only the administrator sees it, because it holds the fees.
Loading…