# India server latency report

> Measured round trips from 28 home and office internet connections in 20 Indian towns and cities to servers in seven regions, on 25 September 2026 (06:03–06:04 IST). Published by FasterHost under CC BY 4.0: reuse with a link to the source.

Source: https://www.fasterhost.in/india-latency-report.php

- A server in Mumbai answered in a median 35 ms; Singapore 73 ms; Europe 152 ms; the United States 247 ms.
- For 28 of 28 connections the nearest region was in India (Mumbai or Hyderabad).
- Singapore added a median 40 ms per round trip over the nearer Indian region.

## Median round trip by region

| Region | Country | Median (ms) | Middle half (ms) |
|---|---|---|---|
| Mumbai | India | 35 | 24–45 |
| Hyderabad | India | 37 | 24–47 |
| Singapore | Singapore | 73 | 54–82 |
| Frankfurt | Germany | 155 | 146–166 |
| London | United Kingdom | 152 | 142–162 |
| Virginia | United States | 247 | 234–273 |
| California | United States | 255 | 238–264 |

## By city (median ms)

| From | Mumbai | Hyderabad | Singapore | Frankfurt | London | Virginia | California |
|---|---|---|---|---|---|---|---|
| Agra | 29 | 38 | 80 | 160 | 153 | 275 | 261 |
| Aizawl, Mizoram (3 probes) | 54 | 59 | 82 | 184 | 177 | 279 | 252 |
| Barddhaman, West Bengal (3 probes) | 43 | 36 | 73 | 155 | 156 | 243 | 271 |
| Bengaluru (2 probes) | 25 | 23 | 46 | 154 | 156 | 247 | 225 |
| Bishnupur | 30 | 46 | 80 | 163 | 155 | 273 | 258 |
| Chennai | 24 | 15 | 35 | 146 | 140 | 234 | 234 |
| Delhi (2 probes) | 25 | 31 | 68 | 143 | 138 | 227 | 266 |
| Edattala, Kerala | 47 | 38 | 53 | 194 | 167 | 281 | 234 |
| Guwahati | 51 | 42 | 94 | 184 | 180 | 255 | 267 |
| Hyderabad | 20 | 18 | 48 | 137 | 135 | 215 | 229 |
| Jaipur | 34 | 54 | 84 | 159 | 150 | 274 | 249 |
| Jammu | 44 | 51 | 104 | 174 | 169 | 288 | 277 |
| Kanayannur, Kerala | 45 | 36 | 51 | 164 | 144 | 246 | 244 |
| Kolkata | 36 | 37 | 73 | 155 | 153 | 241 | 275 |
| Mumbai (2 probes) | 5 | 19 | 59 | 135 | 128 | 230 | 248 |
| New Delhi | 17 | 24 | 45 | 149 | 147 | 249 | 225 |
| Prayagraj, Uttar Pradesh (2 probes) | 35 | 46 | 84 | 155 | 152 | 233 | 263 |
| Pune | 4 | 16 | 61 | 136 | 130 | 245 | 239 |
| Shillong, Meghalaya | 50 | 51 | 94 | 184 | 175 | 260 | 265 |
| Thane | 9 | 24 | 70 | 135 | 137 | 212 | 255 |

## Method

- Probes: Globalping (globalping.io) probes in India on consumer or business ISP networks. 7 on cloud or hosting networks (Oracle Cloud, HostDzire, Good Domain Registry, HostStack) and 3 that did not answer for every region were left out, leaving 28 connections on 14 networks.
- Targets: one public endpoint per region, AWS regional DynamoDB hosts (dynamodb.ap-south-1.amazonaws.com, dynamodb.ap-south-2.amazonaws.com, dynamodb.ap-southeast-1.amazonaws.com, dynamodb.eu-central-1.amazonaws.com, dynamodb.eu-west-2.amazonaws.com, dynamodb.us-east-1.amazonaws.com, dynamodb.us-west-1.amazonaws.com). A test of distance, not of any provider.
- Measurement: 16 TCP connections to port 443 per probe and region; each probe's median, then the median across probes.
- Limits: one early-morning snapshot; fixed-line probes (mobile and Wi-Fi add latency); uneven coverage across states.
- FasterHost's own per-city figures elsewhere on the site come from its monitoring of its own servers and are measured separately.

## Data

- CSV: https://www.fasterhost.in/assets/data/india-latency.csv
- JSON: https://www.fasterhost.in/assets/data/india-latency.json