Livepeer.com API known ingest IPs

gistfile1.txt

IP Address	Location
	
89.187.177.134	NYC
89.187.177.138	NYC
89.187.177.196	NYC
89.187.178.130	NYC
89.187.179.35 	NYC
195.181.169.69  NYC
	
89.187.185.130	LAX
89.187.185.153	LAX
89.187.185.251	LAX
143.244.50.113  LAX

89.187.181.163	MDW
89.187.181.249	MDW
143.244.61.193	MDW
143.244.61.205	MDW
212.102.58.242	MDW

143.244.33.56   SIN
143.244.33.78	SIN
143.244.33.79	SIN
143.244.33.95	SIN
169.150.243.17  SIN
169.150.243.18  SIN
169.150.243.20  SIN

89.187.188.237  PRG
89.187.188.246  PRG
212.102.38.92   PRG
	
84.17.50.98       LON
84.17.50.99	  LON
89.187.88.237	  LON
185.59.221.179	  LON

89.187.169.65     FRA
138.199.36.76	  FRA
185.102.219.91    FRA
185.102.219.180   FRA
195.181.174.33    FRA
195.181.174.39	  FRA
195.181.174.186   FRA

138.199.4.161	SAO
138.199.4.162	SAO
138.199.4.163	SAO
138.199.4.164	SAO

Map
https://www.google.com/maps/d/viewer?mid=1XzxUxgd59Dr3RSzPewGKBD8mt3M77s9C&ll=29.407860546611722%2C-7.196805555555564&z=3

Added 185.102.219.180 FRA

Map of ingest nodes.
https://www.google.com/maps/d/viewer?mid=1XzxUxgd59Dr3RSzPewGKBD8mt3M77s9C&ll=29.407860546611722%2C-7.196805555555564&z=3

mvp

Added 89.187.169.65 FRA

89.187.188.237 PRG

@stronk-dev

Thanks. Added.

Added
195.181.169.69 NYC
185.102.219.91 FRA
195.181.174.186 FRA

Added
138.199.4.163 SAO

Added
143.244.50.113 LAX

An always up-to-date ingest IP list based off this gist is now available via DNS name ppb-lpt.4v1.in, courtesy Sundara.eth.
You can test it with: nslookup ppb-lpt.4v1.in

Useful when you want to use (nftables / iptables) this IP list but don't wish to add in each one manually.
Cloudflare does not allow multiple IPs on a single 'A' RR, their way of forcing Load Balancing on you so I can't use the on-chain domain name.

I noticed LAX and FRA never appear as score region, are they excluded for score testing, please ?
If we want to improve our round_trip_score, is it the best way to deploy our O and T close to NYC and MDW, but not LAX ? (we are in US)

I noticed LAX and FRA never appear as score region, are they excluded for score testing, please ? If we want to improve our round_trip_score, is it the best way to deploy our O and T close to NYC and MDW, but not LAX ? (we are in US)

There seems to be a bug in the Livepeer test streams right now so LAX and FRA aren't being included. In general yes the closer your O/T is to the Livepeer ingest nodes the better your performance score will be. Keep in mind that the test streams are just for O operators to make sure their setups are working properly and don't have a direct correlation to being selected for work. The actual selection is done on a per stream basis at the time a Broadcaster sends out a request for transcoding and is heavily stake weighted.

@papabear99 thanks for the info and tip

Added
143.244.33.56 SIN
169.150.243.18
169.150.243.20

Thanks @AuthorityNull

Added
89.187.181.163 MDW
169.150.243.17 SIN

Added
138.199.4.162 SAO
138.199.4.164 SAO

Added
138.199.4.161 SAO

@papabear99 thanks for maintaining this gist, very helpful to us.
Would you mind to also add the full city name in addition to the abbreviations, please ?

For example, we are not sure what SAO is, and it also took some time to figure out exactly what the other ones are.
Thank you very much!

ok, it's likely you are using the IATA airport code for cities, and SAO is Sao Paulo . Thanks.

Added
195.181.174.33 FRA

I just use the same naming convention Livepeer uses.