public-api.adsbexchange.com/VirtualRadar/AircraftList.json

Is https://public-api.adsbexchange.com/VirtualRadar/AircraftList.json still working ?

I think it stopped working yesterday.

 

I noticed this as well, the ADSB app on android also stopped working but that is now fixed. I assume they have changed the url but i have no idea what it is now. Hopefully someone can shed some light on this matter on here.

 

Mine quit too (at about 00:43:00 2019-04-24). All I receive in response now is "403 Forbidden".

 

The public-api was deprecated this week, well ahead of the planned slow phase out, due to a few factors. I've been in contact with the app developers that were using it to make sure there was minimal downtime.

• Discovered multiple commercial businesses using the public-api for for-profit commercial operations.
• Someone tried to take the service down, likely just due to incompetence spamming calls to it.
• Multiple github repositories noting the way to get data without hosting a feeder was to use the public-api.

The current way going forward will be the REST API as noted at https://adsbexchange.com/data/.

There are only 2 requirements, host a feeder and non-commercial use.

One of the reasons that people should setup feeders is it makes the data better for everyone at ADSBx, as well as creating a sustainable and redundant network. In addition, the process of setting up a feeder helps the new user learn about the data that is available through ADS-B. I think it's a win-win but comments from the community are welcome.

The API supports caching and does not rely on VRS having to fill the requests. VRS has very limited concurrency performance as a web server / API server.

A nice feature of having an API with authorization keys is we can shut off abusers of the API instantly without having to find their IP or chasing them around as they change IPs. It also let's us monitor the number of requests and where they are coming from.

With the old public-api, a few users would send hundreds of requests a second. Yes, hundreds, from a single IP. Due to how VRS fills requests, it made limiting the concurrency automatically very difficult. The end result was a few users were causing a lot of usage at ADSBx for no good reason.

ADSBx data is still freely available to everyone, unfiltered, and unblocked. However, to control costs associated with a select few abusers, ADSBx needed to move to a more sustainable API for data.


Some cool things feeding ADSBx is contributing to!

Feeder detection!
https://adsbexchange.com/myip/

Data stream agnostic merger!
https://github.com/adsbxchange/feedmerge

Feeder data at work!
https://data.info.graphics/flight-patterns/
https://github.com/infographicsgroup/flightdata-client

EDIT: typos

 

Mystery solved. Thanks. This means I need to get going with the REST API for my feed. The only thing that has been holding me back was not wanting to re-code my application. And needing an API key, but I'll request one today.

Thanks too for the peek inside and look into the future of ADSB-X. Yikes -- hundreds of requests per second for a single IP! (I felt bad for making 3 a minute myself Exciting developments along with good utility to throttle the abusers. Appreciate your hard and continuous work.

 

I was working on an announcement but by the time I got things in place yesterday it was 11pm my time.

 

OK, so jdubner said "And needing an API key, but I'll request one today." So how/where does one do that? I couldn't find a place on the website.
Currently I make a call and, as expected I suppose, get this:
{ "ERR" : "NO API KEY" }

 

https://adsbexchange.com/data/


Querying Live Position Data
Live position data can be queried with various parameters are results returned in a JSON format.

Requirements for REST API data access:

1. Hosting a feeder sending data to ADSBx. [ instructions ] [ ADSBx Pi image ] [ FlightAware + ADSBx ]
2. You are a non-commercial personal or enthusiast user.
3. REST API requires authorization key. Contact ADSBexchange to get a key.

 

I understand the reasons behind this, but it'd be nice if there had been some warning ahead (e.g. by emailing all users you donate every month) ?

I have a website that has been running for more than 2 years with fragile code that hasn't been touched since. Changing that to a REST API is a major hassle.

Is there a way to whitelist some IP addresses such that the old request still go through?

If IP whitelisting doesn't work, how about adding an authorization field (similar to an API authentication token) to the old URL? I'd be willing to pay for having that implemented rather than reworking my old code.

Thanks,
Tom

 

Unfortunately a great number of businesses and people think that ADSBx is a charity, that the tens of thousands of dollars a month it takes to make all of this work is somehow pulled out of the air. Socialism sucks when you run out of other people's money.

 

I understand that. That's why I made monthly contributions and asked users of my website to do so as well.

Tom

 

Donations in total are sub $1,000 it barely makes a dent in the $10k to $15k a month it takes to make all this work.

There are some business 'donors' that are covering another $10k+ a month in addition to the above costs.

It's roughly $250k a year just in direct infrastructure to make this all work. We do it on the cheap, we shop around at data centers, etc. But with amount of bandwidth and CPU we need there aren't many places willing to let you saturate a 10 gig link 24/7 for the price of hosting.

 

The public-api was being abused by multiple commercial operations and users. Dan and I have been talking about it for months, trying to chase IP blocks down, send emails, and we rarely get anywhere. We decided there is no other way than to shut it down now and create a more controlled data end point in it's place going forward.

The most frustrating enthusiast users are the ones that feed FA or FR24, use ADSBx daily, but won't even send data from their receiver to ADSBx. It's mind boggling. <face plam>

 

Since today no results returned from the api-call. Any thoughts ?

 

Are you a feeder?

 

Yes, using receiver 'AirplaneDB'.

Request is using 'https://global.adsbexchange.com/Virtu...', worked till the day before yesterday.

 

Email and request API key.

 

I'm having the same or similar trouble Starting at 2019-09-26 12:21:15 (Pacific) my parser reported Error 403 (Forbidden) on API calls. *

That apparently cleared up at 2019-09-28 07:16:02 (Pacific) but something has changed in the returned JSON and my parser no longer works <sigh>.

* Edit: Apparently http://global.adsbexchange.com/Virt....json?lat=44.8643&lng=-123.1923&fCallQ=N227JD is down and redirects to https://www.adsbexchange.com/ That's what my parser no longer works (duh!).

 

Email and request API key.

 

I'm buried.

So many people without feeders to ADSBx but sending to FR24 , FA etc all .. demanding API keys ...

Everyone one of them wants some special treatment for their use case. I'm 1% from not dealing with this and everyone must use the REST PI or piss off.