Shahriar Tabriz
DegradedDomestic datacenterTabriz, IranNoyan Abr Arvan (ArvanCloud)
7-day reliability
Key metrics
Overall status
Degraded
30-day uptime
100.00%
30 days of data
Average latency
42 ms
Packet loss
0.00%
Incidents (30d)
36
Score evidence
Each sample sends 5 ICMP packets. The fixed reference group has 8 probes across Tehran, Mashhad, Tabriz and Ahvaz; self paths are excluded. Every reference path needs at least 95% coverage to rank. Invalid samples are excluded from both score and coverage. Missing data is never assumed healthy. This measures delivery to the monitored endpoint, rather than all datacenter services.
7-day packet loss: 1.571%
Weakest path coverage: 98.5% · 5 of 5 reference paths ready
Minimum samples per path: 9,933 of 10,080
Route summary
Healthy
23
High latency
2
Packet loss
0
Flapping
0
Down
0
Monitoring
0
No data
0
- Lowest latency
- HiWeb Tehran9 ms
- Highest latency
- Hong Kong267 ms
- Most packet loss
- Asiatech Milad Tower0.00%
- Routes
- 25
Route quality from this site
- Healthy
To this siteICMP
- Average latency
- 13 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 11 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 14 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 16 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 12 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 24 ms
- Packet loss
- 0.00%
- High latency
To this siteICMP
- Average latency
- 202 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 9 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 96 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 21 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 13 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 197 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 95 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 11 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 186 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 14 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 16 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 12 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 25 ms
- Packet loss
- 0.00%
- High latency
From this siteICMP
- Average latency
- 201 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 9 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 106 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 86 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 21 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 267 ms
- Packet loss
- 0.00%
| Destination | Measured | Status | Average latency | Packet loss |
|---|---|---|---|---|
| Asiatech Milad TowerICMP | To this site | Healthy | 13 ms | 0.00% |
| Afranet TehranICMP | To this site | Healthy | 11 ms | 0.00% |
| MTN Irancell T3ICMP | To this site | Healthy | 14 ms | 0.00% |
| RashtICMP | To this site | Healthy | 16 ms | 0.00% |
| Shatel DC2ICMP | To this site | Healthy | 12 ms | 0.00% |
| Mashhad FerdowsiICMP | To this site | Healthy | 24 ms | 0.00% |
| Qasir AhvazICMP | To this site | High latency | 202 ms | 0.00% |
| HiWeb TehranICMP | To this site | Healthy | 9 ms | 0.00% |
| Hetzner FalkensteinICMP | To this site | Healthy | 96 ms | 0.00% |
| MCI AhvazICMP | To this site | Healthy | 21 ms | 0.00% |
| Asiatech Milad TowerICMP | From this site | Healthy | 13 ms | 0.00% |
| US - ChicagoICMP | From this site | Healthy | 197 ms | 0.00% |
| IstanbulICMP | From this site | Healthy | 95 ms | 0.00% |
| Afranet TehranICMP | From this site | Healthy | 11 ms | 0.00% |
| UAE - DubaiICMP | From this site | Healthy | 186 ms | 0.00% |
| MTN Irancell T3ICMP | From this site | Healthy | 14 ms | 0.00% |
| RashtICMP | From this site | Healthy | 16 ms | 0.00% |
| Shatel DC2ICMP | From this site | Healthy | 12 ms | 0.00% |
| Mashhad FerdowsiICMP | From this site | Healthy | 25 ms | 0.00% |
| Qasir AhvazICMP | From this site | High latency | 201 ms | 0.00% |
| HiWeb TehranICMP | From this site | Healthy | 9 ms | 0.00% |
| Hetzner FalkensteinICMP | From this site | Healthy | 106 ms | 0.00% |
| Netherlands - HaarlemICMP | From this site | Healthy | 86 ms | 0.00% |
| MCI AhvazICMP | From this site | Healthy | 21 ms | 0.00% |
| Hong KongICMP | From this site | Healthy | 267 ms | 0.00% |
Connectivity view
Shahriar Tabriz
Asiatech Milad Tower
Healthy
Afranet Tehran
Healthy
MTN Irancell T3
Healthy
Rasht
Healthy
Shatel DC2
Healthy
Mashhad Ferdowsi
Healthy
Qasir Ahvaz
High latency
HiWeb Tehran
Healthy
Hetzner Falkenstein
Healthy
MCI Ahvaz
Healthy
US - Chicago
Healthy
Istanbul
Healthy
UAE - Dubai
Healthy
Netherlands - Haarlem
Healthy
Hong Kong
Healthy
Recent incident history
- Covered: Zarpay slow from shahriar-tabriz26 min15 Oct 2026, 17:03Resolved
- Covered: GitHub unavailable from shahriar-tabriz3 min14 Oct 2026, 19:17Resolved
- Covered: Alibaba unavailable from shahriar-tabriz3 min14 Oct 2026, 18:33Resolved
- Covered route stale: Shahriar Tabriz -> Rasht-8 min13 Oct 2026, 00:17Resolved
- Covered route stale: Shahriar Tabriz -> Asiatech Milad Tower34 min12 Oct 2026, 23:35Resolved
- Covered route stale: Shahriar Tabriz -> HiWeb Tehran35 min12 Oct 2026, 23:34Resolved
- Covered route stale: Shahriar Tabriz -> Rasht13 min12 Oct 2026, 23:29Resolved
- Covered route stale: Shahriar Tabriz -> Rasht-9 min12 Oct 2026, 21:57Resolved
- Covered route stale: Shahriar Tabriz -> Asiatech Milad Tower1 min12 Oct 2026, 21:47Resolved
- Covered route stale: Shahriar Tabriz -> HiWeb Tehran1 min12 Oct 2026, 21:47Resolved
- Covered route stale: Shahriar Tabriz -> Rasht-2 min12 Oct 2026, 21:08Resolved
- Covered route stale: Shahriar Tabriz -> Asiatech Milad Tower6 min12 Oct 2026, 20:59Resolved
- Covered route stale: Shahriar Tabriz -> HiWeb Tehran6 min12 Oct 2026, 20:59Resolved
- Covered route stale: Shahriar Tabriz -> Asiatech Milad Tower8 min12 Oct 2026, 19:58Resolved
- Covered route stale: Shahriar Tabriz -> HiWeb Tehran10 min12 Oct 2026, 19:57Resolved
- Covered route stale: Shahriar Tabriz -> Rasht24 min12 Oct 2026, 19:42Resolved
- Covered route stale: Shahriar Tabriz -> Rasht-4 min12 Oct 2026, 17:54Resolved
- Covered route stale: Shahriar Tabriz -> Asiatech Milad Tower5 min12 Oct 2026, 17:45Resolved
- Covered route stale: Shahriar Tabriz -> HiWeb Tehran5 min12 Oct 2026, 17:45Resolved
- Covered route stale: Shahriar Tabriz -> Rasht-6 min12 Oct 2026, 17:14Resolved
- Covered route stale: Shahriar Tabriz -> Asiatech Milad Tower2 min12 Oct 2026, 17:05Resolved
- Covered route stale: Shahriar Tabriz -> HiWeb Tehran4 min12 Oct 2026, 17:05Resolved
- Covered route stale: Shahriar Tabriz -> Rasht-5 min12 Oct 2026, 16:12Resolved
- Covered route stale: Shahriar Tabriz -> Asiatech Milad Tower4 min12 Oct 2026, 16:03Resolved
- Covered route stale: Shahriar Tabriz -> HiWeb Tehran5 min12 Oct 2026, 16:03Resolved
- Complete outage29 min12 Oct 2026, 15:09Resolved
- Packet loss on route29 min12 Oct 2026, 15:09Resolved
- Covered route stale: Shahriar Tabriz -> Asiatech Milad Tower7 min9 Oct 2026, 00:57Resolved
- Covered route stale: Shahriar Tabriz -> HiWeb Tehran8 min9 Oct 2026, 00:56Resolved
- Covered route stale: Shahriar Tabriz -> Rasht14 min9 Oct 2026, 00:49Resolved
- Complete outage52 min6 Oct 2026, 22:29Resolved
- Packet loss on route52 min6 Oct 2026, 22:29Resolved
- Complete outage29 min5 Oct 2026, 03:25Resolved
- Packet loss on route29 min5 Oct 2026, 03:25Resolved
- Packet loss on route3 min3 Oct 2026, 11:56Resolved
- Complete outage3 min3 Oct 2026, 11:56Resolved
Site information
- Operator
- Noyan Abr Arvan (ArvanCloud)
- Location
- Tabriz, Iran
- Site type
- Domestic datacenter
- Autonomous system (ASN)
- AS202468
Contact
- Website
- https://www.arvancloud.ir
Last measured: 16 Oct 2026, 00:41
Score = 100 − the equal-weight mean 7-day packet loss on inbound paths from fixed domestic reference probes. Complete timeouts count as 100% loss. Latency and commercial relationships do not affect the score. Rank uses full precision; displayed values are rounded. Uptime uses available data within the 30-day window. Reliability uses a separate 7-day window; no score or rank is shown until every reference path has at least 95% of its expected samples. Profile and contact details are supplied by the operator and have no effect on status, measurements or technical rank.