Real Globalping measurements requested from Riyadh, Jeddah and Dammam. Exact-city gaps stay blank, and providers are not ranked until their endpoints are comparable.
A2 A2 Hosting (now hosting.com)Amsterdam, NetherlandsVerified data · unrankedOfficial A2/hosting.com test endpoint; not a hosting-plan result.Source ↗ | 82 ms | 70 ms | — | 99 ms | 253 ms | 0.0 % | 14 |
64 ms | 48 ms | — | 74 ms | 219 ms | 0.0 % | 12 | |
63 ms | 48 ms | — | 76 ms | 186 ms | 3.3 % | 11 | |
LW Liquid WebLansing, MichiganVerified data · unrankedOfficial Liquid Web test endpoint; not a hosting-plan result.Source ↗ | 174 ms | 160 ms | — | 175 ms | 602 ms | 0.0 % | 15 |
PH ProHost Company (Saudi Host)Jeddah, Saudi ArabiaVerified data · unrankedOfficial ProHost hostname; delivery passes through Cloudflare, so the value is the Saudi path to the edge, not to an origin server or hosting plan.Source ↗ | 9 ms | 48 ms | — | 76 ms | 829 ms | 0.0 % | 13 |
221 ms | 211 ms | — | 223 ms | 900 ms | 0.0 % | 18 | |
SN Sahara NetRiyadh, Saudi ArabiaVerified data · unrankedSahara Net public site on its own Saudi network; not a controlled hosting-plan endpoint.Source ↗ | 10 ms | 23 ms | — | 28 ms | 1436 ms | 0.0 % | 10 |
TR Tarana (Tarana Tech)Riyadh, Saudi ArabiaVerified data · unrankedOfficial Tarana hostname. Its TLS certificate is not publicly trusted when configured, so the HTTP check uses port 80. Not a controlled hosting-plan endpoint.Source ↗ | 83 ms | 71 ms | — | 118 ms | 166 ms | 0.0 % | 12 |
Only verified Globalping measurements are shown; no values are estimated or commercially adjusted.
Updated every 2 hours. The last successful sample time is shown above.
No verified latency candles are available for this city and period.
Each candle uses real collection-batch median ping latency: first value (open), highest, lowest and last value (close). The 7-day view groups four scheduled collections into 2-hour candles; the 30-day view uses daily candles. Missing runs stay blank.
Every number is traceable to a timestamped raw result. Published results are updated every 2 hours and reuse the same Saudi probes across providers. Ranking remains disabled until all six providers have controlled endpoints and each required city has at least 336 valid samples.
Explore GlobalpingSaudi Arabia → Riyadh, Jeddah and Dammam. Record network and ASN; publish a blank value when an exact-city probe is unavailable—never substitute another city.
Ping, HTTP, DNS, traceroute and MTR on a consistent schedule and controlled endpoint.
Save untouched timestamped JSON first, then generate normalized daily CSV snapshots.
Show every tracked provider, keep missing values blank, disclose endpoint type and aggregate every valid sample.
How measurements are collected, published and kept separate from commercial links.
The benchmark requests Globalping measurements from probes located in Riyadh, Jeddah and Dammam. Each scheduled run uses the same test profile for every enabled provider: ping, HTTPS, DNS, traceroute and MTR. Results are stored with timestamps, probe network details and measurement identifiers before seven-day and thirty-day aggregates are calculated. The public table reports medians, P95 latency, HTTP time to first byte, packet loss and route hops. Exact-city results are never replaced with another location. When a probe or controlled provider endpoint is unavailable, the corresponding value remains blank instead of being estimated.
A blank value means there is no valid, comparable measurement for that provider and city in the selected reporting window. This may happen because Globalping has no active probe in the exact city, the provider still needs a controlled benchmark endpoint, or a test did not finish successfully. The site does not copy results from nearby cities, use marketing claims or generate synthetic estimates. Pending providers remain visible so readers can distinguish missing coverage from poor performance. Once a documented endpoint is available and enough successful samples have accumulated, its results will appear automatically in the seven-day and thirty-day views.
Published benchmark data is updated every two hours based on Saudi Arabia time. Each update uses the fixed network test profile from the selected Saudi probes and preserves the returned raw evidence. The seven-day view uses two-hour latency candles to reveal intraday changes, while the thirty-day view uses daily candles for a steadier long-range picture. The table shows the most recent successful sample time and the number of tests included. A missed or invalid update is not filled with a guessed value; the next successful collection simply adds another verified sample.
Public ranking stays disabled until all six providers use comparable, documented endpoints and the required history has accumulated. The current publication gate requires Kinsta, Liquid Web, Cloudways, ScalaHosting, DigitalOcean and A2 Hosting or hosting.com to have suitable targets. Each provider must also have at least three hundred and thirty-six valid samples from both Riyadh and Jeddah, representing seven days at forty-eight scheduled runs per day. Plan, region, server size, IP address, cache or CDN state and deployment date must be recorded. Until those conditions are met, genuine measurements may be displayed as provisional evidence, but no score or ranking is published.
No. Provider links are kept separate from measurement collection, aggregation and publication rules. While affiliate applications are pending, the links lead to each provider's official website and include a source-tracking parameter. These outbound links are marked sponsored and nofollow, and approved affiliate URLs will retain the same disclosure attributes later. A commercial relationship cannot change a latency value, fill a missing result, qualify an endpoint or unlock a ranking. Scores remain unavailable until the same comparability and sample requirements are satisfied for all six providers. Readers should verify current pricing, product availability and contract terms directly with the provider before purchasing.