165 CloudFlare Nodes in 85 of totally 130 Countries
Visit this page regularly as it is updated daily. Last data update: 30-05-2026 02:11:16 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|564)
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|145)
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|111)
Costa Rica (1|3)
Guatemala (1|4)
Mexico (1|1)
United States (29|1727)
Australia (5|154)
French Polynesia (1|1)
New Caledonia (1|3)
New Zealand (1|10)
Argentina (1|24)
Brazil (5|273)
Chile (1|15)
Ecuador (2|9)United States: 29 Nodes with 1727 IP Addresses
| SEA | Seattle, WA | United States (US) | Canada (CA) | 162.158.41.189 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.41.19 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.41.204 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.41.243 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.41.34 |
| SEA | Seattle, WA | United States (US) | China (CN) | 162.158.41.40 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.41.41 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.41.51 |
| SEA | Seattle, WA | United States (US) | Canada (CA) | 162.158.41.57 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.117 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.127 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.137 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.138 |
| SEA | Seattle, WA | United States (US) | Canada (CA) | 162.158.42.147 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.148 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.175 |
| SEA | Seattle, WA | United States (US) | Philippines (PH) | 162.158.42.179 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.180 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.181 |
| SEA | Seattle, WA | United States (US) | South Korea (KR) | 162.158.42.21 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.211 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.212 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.43 |
| SEA | Seattle, WA | United States (US) | Canada (CA) | 162.158.42.44 |
| SEA | Seattle, WA | United States (US) | United States (US) | 162.158.42.94 |
Parse Time: 139.421 ms
Is Lazy Loading Always a Net Performance Win?
Lazy loading defers resource loading, but its overall benefit depends on context, rendering behavior, and server characteristics.
The Intended Benefit
Lazy loading reduces initial network payload by deferring offscreen images and assets.This can improve first paint and reduce bandwidth consumption.
Browser Scheduling Complexity
Modern browsers schedule requests dynamically.Aggressive deferral may delay resource discovery or introduce layout shifts.
The benefit is not purely additive; timing interactions matter.
Server-Side Considerations
Lazy loading affects client rendering more than backend generation.If server execution time dominates TTFB, deferring images does not address that root cause.
Edge Cases
Infinite scroll implementations and dynamic galleries sometimes create additional script overhead to manage loading states.That overhead can offset bandwidth savings.
Measuring Impact
Compare total transferred bytes, LCP, and backend latency independently.A holistic view prevents over-crediting a single technique.
Conclusion
Lazy loading is powerful when bandwidth and rendering cost dominate.It is neutral when backend execution is the primary constraint.
Key Takeaways
- Separate frontend gains from backend cost.
- Evaluate layout stability alongside network savings.
- Test under realistic network conditions.
- Use lazy loading selectively rather than universally.