Next week we'll start rolling out a 2nd US region on the east coast to complement the existing one on the west coast.
With the new region rolled out, we'll have more processing capacity (in terms of recordings/minute) and more transcoding capacity. Users on the east coast will experience lower latency and faster streaming/uploading when using the Pipe recording client.
The rollout will start next week with users who have selected "US (N. California)" as their environment region.
The existing region option "US (N. California)" will be replaced by a new "Auto US" one that will automatically route users to one of the 2 regions in the US based on their location.
Rolling out the region in this way has the benefit of us being able to upgrade or perform maintenance on each US region individually (by routing users to the other one while we perform the upgrade) without crossing geographical and privacy boundaries and without impacting users (downtime).
We'll also be able to direct users to each of the two regions based on load, other factors or during unplanned downtime or issues.
When recording against the new region, the user will be streaming/uploading towards a media server in NY while the final storage (if handled by us) will be on an S3 bucket in N Virginia.
The storage and environment pages in the Pipe account area and the the documentation have now been updated with new information regarding the new US2 region.
After rolling it out to environments using the "US (N. California)" region, in the week starting May 11 we'll continue the rollout with the environments using the "Auto-detect" region. The Auto-detect region will then include all 3 regions (US1, US2 and EU).
Some important info for developers:
- the IP for the new region from which webhooks will be fired and files will be pushed to your storage is 188.8.131.52 . Make sure you add it to your whitelist/firewall if you have such protections in place.
video_copied_s3webhook fired - when we store the recordings for you- for recordings streamed/uploaded to the new region will contain the (updated) full URL to the recordings stored on the new region (e.g.
- the JS Events API's functions will send out the new value for the