3 ms·
Backstory here: freegeoip.net has an hourly per-IP limit, so we distributed the load by doing the geolocation from client browsers. This borked freegeoip after
by mhashemi 13y ago
Backstory here: freegeoip.net has an hourly per-IP limit, so we distributed the load by doing the geolocation from client browsers. This borked freegeoip after many hours of Twitter/Ars Technica'ing.
It was a good thing Github got its storage servers back up; we're now running a local clone of freegeoip, as freegeoip.net smolders.
To freegeoip.net! May it rise again soon.
- mhashemi 13y ago(N.B. for returning visitors: The sooner you force-refresh, the sooner freegeoip.net rises again.)