# Akamai have their own Wowza servers but why use them over your own Wowza servers? **URL:** \ **Category:** Wowza Streaming Engine\ **Created:** [September 30, 2014, 11:17pm UTC](https://community.wowza.com/t/akamai-have-their-own-wowza-servers-but-why-use-them-over-your-own-wowza-servers/39475 "2014-09-30T23:17:48Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Johan\_Niemi](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@Johan\_Niemi](https://community.wowza.com/u/Johan_Niemi)\ **Post date:** [September 30, 2014, 11:17pm UTC](https://community.wowza.com/t/akamai-have-their-own-wowza-servers-but-why-use-them-over-your-own-wowza-servers/39475/1 "2014-09-30T23:17:48Z")
Is it correct that Akamai and other CDN’s have their own Wowza servers? I’m trying to understand the differences between two ways of reaching the Akamai CDN. **Wirecast** streaming to **my own EC2 Wowza server** Push Publishing to **Akamai CDN**. **Wirecast** streaming to **Akamai’s Wowza servers** that then feeds the **Akamai CDN**. Could you please elaborate on these two approaches? ---
**Author:** ![Johan\_Niemi](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@Johan\_Niemi](https://community.wowza.com/u/Johan_Niemi)\ **Post date:** [October 2, 2014, 4:37pm UTC](https://community.wowza.com/t/akamai-have-their-own-wowza-servers-but-why-use-them-over-your-own-wowza-servers/39475/2 "2014-10-02T16:37:03Z")
Anyone? ---
**Author:** ![Jason\_Hilton](https://sea2.discourse-cdn.com/flex002/user_avatar/community.wowza.com/jason_hilton/32/437_2.png) [@Jason\_Hilton](https://community.wowza.com/u/Jason_Hilton)\ **Post date:** [October 3, 2014, 5:46pm UTC](https://community.wowza.com/t/akamai-have-their-own-wowza-servers-but-why-use-them-over-your-own-wowza-servers/39475/3 "2014-10-03T17:46:07Z")
Hi, If you’re controlling the server which is ingesting the stream before pushing to Akamai then you can also push to other CDNs or have customers connect to that server directly if required. You will also be able to see the logs created on the server should something happen which is unexpected giving you some control over resetting the stream if needed. Regards, Jason ---
**Author:** ![Johan\_Niemi](https://avatars.discourse-cdn.com/v4/letter/j/a183cd/32.png) [@Johan\_Niemi](https://community.wowza.com/u/Johan_Niemi)\ **Post date:** [October 3, 2014, 8:26pm UTC](https://community.wowza.com/t/akamai-have-their-own-wowza-servers-but-why-use-them-over-your-own-wowza-servers/39475/4 "2014-10-03T20:26:51Z")
> If you’re controlling the server which is ingesting the stream before pushing to Akamai then you can also push to other CDNs or have customers connect to that server directly if required. You will also be able to see the logs created on the server should something happen which is unexpected giving you some control over resetting the stream if needed. Thank you Jason. So is this accurate? And are there more pros and cons to add to the lists? _ **Running and maintaining your own Wowza server set up to Push Publish to Akamai CDN** _ Advantages Ability to push to other CDNs Ability to consume stream directly from Wowza server (maybe in case of rare CDN downtime) Ability to view access and error log Ability to restart the server, service or the stream itself Disadvantages You are using the public internet twice: 1. From on premise encoder to your Wowza server 2. From your Wowza server to Akamai’s CDN. _ **Using Akamai’s Wowza server that feeds the Akamai CDN** _ Advantages There’s only one potentially risky internet route from on premise encoder to Akamai’s Wowza server. The Wowza server will feed the Akamai CDN over LAN, so this is one public internet route less. Disadvantages You can’t push to other CDNs You can’t consume stream directly from the Wowza server You can’t view access and error log You can’t restart the Akamai-managed Wowza server, service or the stream itself