Over the last 24hrs we’ve upgraded our back-end database to MariaDB from MySQL, This was done for speed improvements (there are a few), and for sticking with a better maintained package. The MariaDB package is maintained by the original creator of MySQL.
Tonight we brought our new data center online. This includes new hardware, and some small changes to the software to accommodate it. The system is much faster than before, and over the next few days we’ll be enabling more fault-tolerant systems.
In moving to this new data center, we found the SSL certificates were not working right, so we’ve disabled SSL access until we can fix this. This is not a security flaw, but simply a configuration issue that we hope to have solved very soon.
[Update] Mar 6, 2015 16:00 UTC: SSL encryption has been restored.
Thank you for you patience as we implemented a replicated, fault-tolerant database structure. Long overdue, this new structure allows:
- Increased performance on map refreshes
- Daily backups without downtime
- Data in a ‘hot copy’ format that will make it much faster to recover from a database failure.
[Update Mar 3, 2015] The database performance is not as good as we’d hoped. We’re working on improving it this week.
Our primary database failed today, and restoring it took longer than we expected – over 3 hours.
We apologize for any problems this may have caused, and assure you we are already investigating ways we can recover better from an outage like this.
We’ve seen a few instances where the same location is listed on IWM to different, but correct, ways. Such as Australia showing up a both “Australia” and “AU”, and California showing up as “California” and “CA”, and even “Calif”.
We’ve updated our code to start to phase these locations out, and standardize on two letter abbreviations when we can. It makes the text more readable, and certainly more consistent.
Our tools menu has changed, allowing IP lookups showing geographical data about the IP, as well as other known IPs in the same area. Future releases of our software will feature more tools, all based around IP information.
Information on this tools page is obtained from our API which is scheduled to be released in Q1 of 2015.
Today we’re rolling out new security for our users, centered around user/pass authentication. What we had in place before was very good, but our new system is even tougher with even larger password hashes.
We’ve also added security that will kick others out of your account if you change your password. While it’s never a good idea to give out your password, we’ve all done it before. With out new system, the moment you change your password, anyone else who is using your password will be forced out of your account, creating an easy way to lock down your account.
Because of this increased security, most users will have to change their passwords. We apologize for this inconvenience, but better security is always worth it.
The connection, from Adelaide, Australia to San Jose, US, owned by Internode Pty Ltd, continues to have latency issues. While connections from Australia to the States are know to be a little slow, this one seems to be consistently worst than the rest.
While the the Northeast US digs out from two feet of snow, the good news is that internet held up well during the storm. There were certainly thousands of home internets connections that went down completely, but commercial backbones remained mostly unaffected with normal latency times.
We’ve been noticing that sometimes a trace would be drawn from one location to the next but the names of the location didn’t match accurately to where the lines were drawn. Sometimes it was off by only a few miles, but sometimes worse.
We’ve spent the last week working on the problem, and have vastly improved the accuracy of our geolocation system, the engine that converts an IP address into a named location with latitude and longitude pairs.
While we’re confident in the improvement, it’s impossible for us to be 100% accurate. If you think you see a problem with anything on the map, please contact us at email@example.com.