Afranet Tehran
DegradedDomestic datacenterTehran, IranAfranet
7-day reliability
Key metrics
Overall status
Degraded
30-day uptime
100.00%
30 days of data
Average latency
15 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.672%
Weakest path coverage: 98.8% · 5 of 5 reference paths ready
Minimum samples per path: 9,955 of 10,080
Route summary
Healthy
22
High latency
1
Packet loss
0
Flapping
0
Down
0
Monitoring
0
No data
0
- Lowest latency
- Asiatech Milad Tower1 ms
- Highest latency
- Hong Kong282 ms
- Most packet loss
- Asiatech Milad Tower0.00%
- Routes
- 23
Route quality from this site
- Healthy
To this siteICMP
- Average latency
- 1 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 2 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 15 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 1 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
- 12 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 1 ms
- Packet loss
- 0.00%
- Healthy
To this siteICMP
- Average latency
- 74 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 1 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 187 ms
- Packet loss
- 0.00%
- High latency
From this siteICMP
- Average latency
- 152 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 195 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 3 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 16 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 1 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 11 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 14 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 11 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 1 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 76 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 90 ms
- Packet loss
- 0.00%
- Healthy
From this siteICMP
- Average latency
- 282 ms
- Packet loss
- 0.00%
| Destination | Measured | Status | Average latency | Packet loss |
|---|---|---|---|---|
| Asiatech Milad TowerICMP | To this site | Healthy | 1 ms | 0.00% |
| MTN Irancell T3ICMP | To this site | Healthy | 2 ms | 0.00% |
| RashtICMP | To this site | Healthy | 15 ms | 0.00% |
| Shatel DC2ICMP | To this site | Healthy | 1 ms | 0.00% |
| Shahriar TabrizICMP | To this site | Healthy | 11 ms | 0.00% |
| Mashhad FerdowsiICMP | To this site | Healthy | 14 ms | 0.00% |
| Qasir AhvazICMP | To this site | Healthy | 12 ms | 0.00% |
| HiWeb TehranICMP | To this site | Healthy | 1 ms | 0.00% |
| Hetzner FalkensteinICMP | To this site | Healthy | 74 ms | 0.00% |
| Asiatech Milad TowerICMP | From this site | Healthy | 1 ms | 0.00% |
| US - ChicagoICMP | From this site | Healthy | 187 ms | 0.00% |
| IstanbulICMP | From this site | High latency | 152 ms | 0.00% |
| UAE - DubaiICMP | From this site | Healthy | 195 ms | 0.00% |
| MTN Irancell T3ICMP | From this site | Healthy | 3 ms | 0.00% |
| RashtICMP | From this site | Healthy | 16 ms | 0.00% |
| Shatel DC2ICMP | From this site | Healthy | 1 ms | 0.00% |
| Shahriar TabrizICMP | From this site | Healthy | 11 ms | 0.00% |
| Mashhad FerdowsiICMP | From this site | Healthy | 14 ms | 0.00% |
| Qasir AhvazICMP | From this site | Healthy | 11 ms | 0.00% |
| HiWeb TehranICMP | From this site | Healthy | 1 ms | 0.00% |
| Hetzner FalkensteinICMP | From this site | Healthy | 76 ms | 0.00% |
| Netherlands - HaarlemICMP | From this site | Healthy | 90 ms | 0.00% |
| Hong KongICMP | From this site | Healthy | 282 ms | 0.00% |
Connectivity view
Afranet Tehran
Asiatech Milad Tower
Healthy
MTN Irancell T3
Healthy
Rasht
Healthy
Shatel DC2
Healthy
Shahriar Tabriz
Healthy
Mashhad Ferdowsi
Healthy
Qasir Ahvaz
Healthy
HiWeb Tehran
Healthy
Hetzner Falkenstein
Healthy
US - Chicago
Healthy
Istanbul
High latency
UAE - Dubai
Healthy
Netherlands - Haarlem
Healthy
Hong Kong
Healthy
Recent incident history
- Covered route stale: Afranet Tehran -> Rasht-4 min13 Oct 2026, 01:26Resolved
- Covered route stale: Afranet Tehran -> HiWeb Tehran5 min13 Oct 2026, 01:17Resolved
- Covered route stale: Afranet Tehran -> Asiatech Milad Tower5 min13 Oct 2026, 01:16Resolved
- Covered route stale: Afranet Tehran -> Asiatech Milad Tower31 min12 Oct 2026, 23:37Resolved
- Covered route stale: Afranet Tehran -> Rasht39 min12 Oct 2026, 23:24Resolved
- Covered route stale: Afranet Tehran -> HiWeb Tehran51 min12 Oct 2026, 23:15Resolved
- Covered route stale: Afranet Tehran -> Rasht0 min12 Oct 2026, 21:33Resolved
- Covered route stale: Afranet Tehran -> Rasht8 min12 Oct 2026, 20:51Resolved
- Covered route stale: Afranet Tehran -> HiWeb Tehran51 min12 Oct 2026, 20:42Resolved
- Covered route stale: Afranet Tehran -> Asiatech Milad Tower18 min12 Oct 2026, 20:41Resolved
- Covered route stale: Afranet Tehran -> Rasht25 min12 Oct 2026, 19:40Resolved
- Covered route stale: Afranet Tehran -> Asiatech Milad Tower35 min12 Oct 2026, 19:31Resolved
- Covered route stale: Afranet Tehran -> HiWeb Tehran35 min12 Oct 2026, 19:31Resolved
- Covered route stale: Afranet Tehran -> Asiatech Milad Tower3 min12 Oct 2026, 18:56Resolved
- Covered route stale: Afranet Tehran -> HiWeb Tehran3 min12 Oct 2026, 18:56Resolved
- Covered route stale: Afranet Tehran -> Rasht11 min12 Oct 2026, 18:48Resolved
- Covered route stale: Afranet Tehran -> Rasht-4 min12 Oct 2026, 17:59Resolved
- Covered route stale: Afranet Tehran -> Asiatech Milad Tower30 min12 Oct 2026, 17:20Resolved
- Covered route stale: Afranet Tehran -> HiWeb Tehran9 min12 Oct 2026, 17:19Resolved
- Covered route stale: Afranet Tehran -> Rasht12 min12 Oct 2026, 17:15Resolved
- Covered route stale: Afranet Tehran -> Rasht-3 min12 Oct 2026, 16:48Resolved
- Covered route stale: Afranet Tehran -> Asiatech Milad Tower8 min12 Oct 2026, 16:38Resolved
- Covered route stale: Afranet Tehran -> Rasht-2 min12 Oct 2026, 16:11Resolved
- Covered route stale: Afranet Tehran -> Asiatech Milad Tower5 min12 Oct 2026, 16:01Resolved
- Covered route stale: Afranet Tehran -> HiWeb Tehran44 min12 Oct 2026, 16:01Resolved
- Complete outage28 min12 Oct 2026, 15:10Resolved
- Packet loss on route28 min12 Oct 2026, 15:10Resolved
- Covered route stale: Afranet Tehran -> Asiatech Milad Tower7 min9 Oct 2026, 00:57Resolved
- Covered route stale: Afranet Tehran -> HiWeb Tehran7 min9 Oct 2026, 00:57Resolved
- Covered route stale: Afranet Tehran -> Rasht14 min9 Oct 2026, 00:49Resolved
- Complete outage49 min6 Oct 2026, 22:30Resolved
- Packet loss on route49 min6 Oct 2026, 22:30Resolved
- Complete outage29 min5 Oct 2026, 03:26Resolved
- Packet loss on route29 min5 Oct 2026, 03:26Resolved
- Complete outage3 min3 Oct 2026, 11:56Resolved
- Packet loss on route3 min3 Oct 2026, 11:56Resolved
Site information
- Operator
- Afranet
- Location
- Tehran, Iran
- Site type
- Domestic datacenter
- Autonomous system (ASN)
- AS25184
Contact
- Website
- https://www.afranet.com
Last measured: 13 Oct 2026, 18:08
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.