Updated C# code example now supports our v2 API

Late last month just as we were shutting down for the holidays the developer of our C# example, hollow87 updated his proxycheck C# library to support our v2 API including all our latest features such as lat/long and city information.

You can check out the example here on our code examples page or here on the NuGet page for the project. Using this library you can build a very robust implementation of our API in your .net applications with very little effort.

Happy coding! 👩‍💻

Holiday Support Times

Hello everyone below are the dates where live support will not be available but email based support will still be available. We will of course be monitoring our site and the API throughout the holidays and you can still make purchases and cancel a plan during the stated time periods and everything will remain fully functional.

Email support only between:
Sunday, December 23rd to Wednesday, January 2nd.

To be clear, we will only be offering email based support beginning on Sunday, December 23rd until Wednesday, January 2nd at which point normal support services which includes our web based live support chat will resume. Thanks!

What a great year its been!

As we're now just a few weeks away from the new year we thought now is a good time to go through some of the milestones from this year.

If you would like to view the specific features we added or enhanced this year we recommend taking a look at our November 2018 newsletter. It's a great read and all of the changes listed within the newsletter link to blog post entries for more detail.

This year we saw impressive growth, at one point the volume of API queries we were receiving was doubling every month and we had to upgrade not just our API but our server hardware a few times to keep up with the projected demand. We also enhanced our network infrastructure significantly by using a world-wide Virtual Private Network (VPN) through our Content Delivery Network (CDN) provider which reduced latency for customers who are the furthest away from our servers.

As we mentioned above we upgraded our API several times. In-fact we launched our v2 API in January 2018 and since then the adoption rate has been incredible, we've updated you a few times on these numbers and today we're seeing 91% of all customers using the v2 API for their queries. This is up from 72% back in July.

In addition to launching the v2 API at the start of this year we also upgraded the API several times throughout the year reducing query latency by enormous amounts. You may remember when v2 launched its main feature was the ability to check multiple IP Addresses in a single query allowing efficient batch processing.

At the time the efficiency wasn't as high as it needed to be so we could only allow 100 IP's to be checked simultaneously and that could take up-to 90 seconds in some cases with all our checks enabled. In February we raised that limit to 1,000 and then in August we raised it again to 10,000. These kinds of improvements were made possible by redesigning core parts of the API to remove bottlenecks. Today you can check 10,000 IP's in around 25 seconds.

Even while we added more data to the API including improved provider, country and ASN information, the addition of IPv6 data and most recently, city, longitude and latitude data we've been able to increase performance. In-fact we now track more datacenter providers and more proxies than ever before and we spend more machine hours than ever processing incoming queries through our inference engine and yet the API is faster today than ever before.

Going into 2019 we intend to invest even more heavily in our unique technology. We recently did an infrastructure deep dive which resulted in a large influx of questions to our support staff from people wanting to know more and we intend to follow this up with an architecture overview breaking down some of our custom tools next year, stay tuned for that.

This year we also spent a lot of time improving the tools customers have to use on our website. We improved our Dashboard API's, we improved the web interface page several times and we introduced the new threats page. We also invested heavily in the customer dashboard making it more performative, improving the appearance, adding two-factor security and other enhancements. We'll keep improving this next year too.

So that's what happened with us this year, huge growth, lots of improvements to the site and our service. We want to thank all of the customers that took the time to try our service and we're especially thankful to those of you who took the time to write to us with ideas and suggestions, that input has often been invaluable, in-fact a lot of the features listed in our November newsletter were born from ideas pitched to us directly by customers.

We hope everyone has an enjoyable festive period and a great new year. We'll be making one last blog post directly after this one for our holiday support times so make sure to check that out, apart from that you should next hear from us in January 2019!

Updated Threats Page

When we added the Threats page in late August it was always our intention to create a home view where you could see live emerging threats. But we didn't quite know how we wanted it to look and what information we wanted to make available as we didn't want to give bad actors easy access to unique proxy data with which to launch malicious acts.

So we spent some time on it and decided that providing a map showing which countries the most attacks are coming from and a heavily shrunk down list of recent detections would be the best way to accomplish our goal. We'll keep working on adding more data as we feel it's appropriate but for now this is our starting point for our new threats home view.

Image description

If you've used the customer dashboard before then this view will be quite familiar to you. We've kept it simple, the map will show around 5,000 recent attacks by country with the addresses behind the attacks not displayed. Then below we will showcase 10 recent addresses that we've detected performing attacks and that also have active proxy servers running.

We hope you like the new home view, this is in addition to our specific address pages which will continue to be accessible. We've actually updated those pages with new city and specific location data which was also exposed through our v2 API update a few days ago.

Thanks for reading and we hope everyone is enjoying their weekend!

Issue with IPv6 VPN reporting

For around a 9 hour period between November 23rd and 24th all IPv6 addresses checked with our service with the VPN flag enabled were detected incorrectly as VPN's. IPv4 checks were not affected.

This was due to human error on our part when we accidentally entered in a VPN providers IPv6 range incorrectly. We have since corrected the problem and put a process in place to make sure this cannot happen again. We're very sorry to everyone affected by our mistake, we did not live up to our own expectations of high quality service in this instance.

ASN data improved with city and coordinate information

Today we've updated our v2 API endpoint to support the exposure of city and coordinate information alongside the previous country name and country isocode information. You'll find new examples featuring this data on our API Documentation page.

We have not changed our data formatting so any software you developed against our v2 API will remain fully functional but if you go back and make some changes you can now include the City (if applicable) and Latitude and Longitude in your software if you need it.

This has been an often requested feature and we're happy to be able to provide it to everyone today. Like all API changes this is accessible to all customers whether you're using a free or paid plan.

Thanks for reading and we hope everyone has a great weekend!