165 CloudFlare Nodes in 85 of totally 130 Countries
Visit this page regularly as it is updated daily. Last data update: 29-05-2026 13:59:06 UTC
Africa
Algeria (1|4)
Ethiopia (1|5)
Ivory Coast (1|5)
Kenya (2|7)
Mauritius (1|5)
Mozambique (1|2)
Reunion (1|3)
Rwanda (1|1)
South Africa (2|42)
Tanzania (1|6)
Zimbabwe (1|1)Asia
Armenia (1|5)
Azerbaijan (2|4)
Bahrain (1|1)
Bangladesh (1|33)
China (1|470)
Georgia (1|9)
India (4|111)
Indonesia (3|9)
Israel (2|19)
Japan (3|99)
Jordan (1|4)
Kuwait (1|3)
Laos (1|2)
Malaysia (1|35)
Mongolia (1|1)
Nepal (1|15)
Oman (1|9)
Pakistan (2|16)
Philippines (1|5)
Singapore (1|563)
South Korea (1|10)
Sri Lanka (1|1)
Taiwan (2|23)
Thailand (1|21)
Turkey (1|84)
United Arab Emirates (1|4)
Vietnam (2|4)Europe
Albania (1|1)
Austria (1|143)
Belgium (1|27)
Bulgaria (1|75)
Croatia (1|2)
Cyprus (1|9)
Czech Republic (1|45)
Denmark (1|72)
Estonia (1|18)
Finland (1|22)
France (3|546)
Germany (6|617)
Greece (1|38)
Hungary (1|9)
Iceland (1|2)
Ireland (1|18)
Italy (2|167)
Latvia (1|27)
Lithuania (1|7)
Luxembourg (1|2)
Moldova (1|1)
Netherlands (1|524)
Norway (1|29)
Poland (1|181)
Portugal (1|36)
Romania (1|77)
Russia (1|12)
Serbia (1|14)
Slovakia (1|12)
Spain (2|149)
Sweden (1|76)
Switzerland (2|49)
Ukraine (1|10)
United Kingdom (3|534)
Canada (4|110)
Costa Rica (1|3)
Guatemala (1|4)
Mexico (1|1)
United States (29|1726)
Australia (5|154)
French Polynesia (1|1)
New Caledonia (1|3)
New Zealand (1|10)
Argentina (1|24)
Brazil (5|270)
Chile (1|15)
Ecuador (2|9)United States: 29 Nodes with 1726 IP Addresses
| SEA | Seattle, WA | United States (US) | United States (US) | 172.71.151.72 |
| SEA | Seattle, WA | United States (US) | United States (US) | 172.71.151.81 |
| SEA | Seattle, WA | United States (US) | United States (US) | 172.71.151.82 |
| SEA | Seattle, WA | United States (US) | United States (US) | 172.71.151.85 |
| SJC | San Jose, CA | United States (US) | Australia (AU) | 104.22.17.134 |
| SJC | San Jose, CA | United States (US) | Taiwan (TW) | 104.22.17.135 |
| SJC | San Jose, CA | United States (US) | Philippines (PH) | 104.22.17.98 |
| SJC | San Jose, CA | United States (US) | United States (US) | 104.22.20.100 |
| SJC | San Jose, CA | United States (US) | Japan (JP) | 104.22.20.16 |
| SJC | San Jose, CA | United States (US) | United States (US) | 104.22.20.79 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.166.247 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.112 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.12 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.121 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.122 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.128 |
| SJC | San Jose, CA | United States (US) | Taiwan (TW) | 162.158.167.134 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.155 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.162 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.177 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.178 |
| SJC | San Jose, CA | United States (US) | Taiwan (TW) | 162.158.167.18 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.216 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.222 |
| SJC | San Jose, CA | United States (US) | United States (US) | 162.158.167.34 |
Parse Time: 88.817 ms
Can a CDN Replace Backend Efficiency?
Content delivery networks reduce latency and offload traffic, but they do not eliminate backend execution cost for uncached or dynamic requests.
What CDNs Do Well
They cache static assets and distribute them geographically.They absorb traffic spikes effectively.
What They Cannot Change
Dynamic checkout flows and personalized dashboards still require origin processing.If origin execution is slow, CDN presence does not solve that root problem.
Cache Miss Realities
Low cache hit ratios expose backend inefficiencies.Improving origin cost remains necessary.
Complementary Strategies
CDNs and structural backend improvements reinforce each other.Key Takeaways
- CDNs improve delivery, not core execution logic.
- Cache misses reveal backend architecture quality.
- Combine edge caching with origin optimization.
- Measure miss cost explicitly.