Uplynk Reviews

My main use case for Uplynk is live channels around the clock. Since we're in the television business, we're constantly showcasing shows, and it's a continuous operation.

Uplynk's best features are its stability and its capacity to handle high volumes of traffic. The stability that stands out most to me is the ability to handle traffic spikes, which I would say is the best feature.

Uplynk has positively impacted our organization by bringing us more viewership. It does not glitch and stays stable during spikes in viewership. We've seen approximately a 15 to 20 percent increase in viewership because there's no lag and nothing fails. It's constant, so viewership increased. It allowed our viewers to have trust in what we were providing due to the software.

To improve Uplynk, it should be made more user-friendly, as it takes a lot of moving pieces to make it work. Uplynk is very complex software with many moving pieces. If you're a big company, Uplynk is for you. If you're a small company, consider YouTube Stream and similar software because you're not at the scale yet to be using Uplynk.

I have been using Uplynk for a few years, but my company has been using it for probably ten years.

Uplynk is very stable. Uplynk's scalability is very high and very well scalable.

Uplynk's customer support is amazing, especially when you run into problems. They know everything about their product and they're always willing to support and stay on top of it with you to ensure that you're able to fix the issue at hand.

I wasn't a part of the pricing, setup cost, and licensing discussions, but from what I heard from my colleagues, they said it was really good and it was fair, so they went with that.

Uplynk is deployed in my organization on-premises and is fully on-site.

Uplynk supports our business continuity or disaster recovery plans because it's really well protected and it doesn't lag or crash when there's a spike in all areas. Uplynk helps us comply with regulatory requirements in our industry by keeping us live.

Uplynk integrates really well with other systems or tools we use. You need a whole team to really run Uplynk because there are so many moving pieces, the code, the app, and other components. My experience with Uplynk's analytics or reporting capabilities is that they are especially helpful to update the teams and our stakeholders.

I would describe Uplynk's flexibility or customization options as really easy, really customizable, and it integrates in many areas. Uplynk helps me deliver content to different devices or platforms by allowing us to upload on and stay live on tablets, computers, and televisions. It allows us to stay live to get those viewerships.

Uplynk is a software that saves time, but you need a solid team to run Uplynk to ensure viewership and everything is moving because there are many pieces to keep. I advise others looking into using Uplynk that it takes many different areas: coding, integration, APIs, and all that. It takes a team to run it, and you need to be a big company. If you're streaming and doing all that at a big scale, use it. If you're on a smaller scale, Uplynk is going to be really hard for you to manage. It's not something that's simple; just use the ones that are basic out there if you're an influencer and things like that. I would rate this product a nine overall.

I usually use the product for mobile development. At my last company, OmniTier, I worked as a senior principal software engineer, and one of my responsibilities was leading mobile app development. 

I utilized Expo for this purpose and focused on leveraging frameworks for our UI builds and mobile app development using Expo, which significantly enhances user engagement.

During my tenure, I implemented optimization techniques for API calls, which resulted in a smooth user experience and fast load times. I restructured our code base to enhance development workflow efficiency, leading to improvements in our team's overall development time. This allowed us to deliver features more rapidly and maintain higher quality standards.

The most valuable aspects include the optimization of application performance by optimizing API calls for a smoother user experience and faster load times. Furthermore, I restructured our code base to establish a more efficient development workflow. 

During my tenure, I integrated various security features for mobile applications, such as JWT tokens for secure authentication and data encryption using AES algorithms. I also focused on secure storage options, secure coding practices, and platform-specific security compliance, like Android's SafeNet and iOS Secure Enclave.

Regarding improvements, I focused on testing and compatibility to ensure reliability across various mobile devices. By writing comprehensive tests and leveraging Expo's capabilities, I ensured consistent performance across different platforms. I prioritized optimizing API calls, utilizing strategies such as lazy loading.

I have about five years of experience with Edgio Global CDN.

I rated the stability as a nine out of ten. I focused on stability, which is crucial for scalability. Fixing problems after the product application is essential for maintaining stability.

I rate the scalability as eight or nine out of ten. Approximately ten million to 20 million users were using it in our organization.

The customer support and service responsiveness were excellent. Their support team was advanced and responded very quickly.

Neutral

In my previous company, Lookouts, I used another global CDN, AWS CloudFront.

The initial setup was easy for me. However, for others, I would guide them and suggest following the documentation.

During my tenure at OmniTier, I was deeply involved in integrating and enhancing various security features.

The pricing was initially very expensive. However, after improving and restructuring the application, it became more affordable and now offers reasonable pricing.

My advice for others is to focus on reducing the cost when choosing a Global CDN provider. 

Overall, I rate Edgio Global CDN as eight out of ten.

We use the solution for high volume traffic. It is used across various e-commerce platforms to enhance loading times and streamline navigation, ultimately optimizing user experience.

The impact on customers' experience as soon you see the difference between using our network and CDN.

Edgio could improve their documentation.

I have been using Edgio Global CDN since 2022.

The product is stable.

I rate the solution’s stability a ten out of ten.

The solution’s scalability is good.

I rate the solution’s scalability an eight out of ten.

I have used Cloudflare as a content delivery network.

The initial setup is easy. It has been particularly beneficial for startups.

The product is affordable.

When one of the primary nodes spanning from North to South America, from the northern US to the southern US, became operational, it had a big impact.

It can be challenging to explain its advantages to clients. The technical nature of the marketing material is too technical for stakeholders.

Integrating the solution was straightforward, requiring no extra effort.

Edgio Global CDN operates, resembling familiar cloud services but offering elevated functionality. Unlike platforms such as Google Cloud Platform or RIN geared towards development teams, Edgio emphasizes client-facing services that are integral to our operations.

Overall, I rate the solution a nine out of ten.

We needed the solution for Layer 3, Layer 4, and Layer 7 DDoS protection and web application firewall.

The product is easy to use and easy to implement. It is a good product.

There were a few limitations in the product. While evaluating it, we found a couple of gaps. Rate Limiting features were not completely developed. The new feature requests used to take a little longer. The product was not mature, which is why it did not have a couple of features we needed. 

There were limitations and gaps in the product because it was new. Some of the WAF features were missing. Custom rules did not work. We could not create more than 15 custom rules. We had to raise new feature requests all the time. We could not see the logic behind the rules.

I have used the solution for one year.

The product is not stable because it is not mature. We used to give Verizon the code and logic for most of the features, and then they used to implement it.

The solution is scalable because it is a CDN. In my company, more than 25 people were using the solution.

We used to connect with support every day.

Neutral

We were using Akamai. It was quite expensive. So we switched to Verizon EdgeCast because it was quite cheaper. During the initial discussion with Verizon, we saw that the product was fulfilling all the requirements that Akamai fulfilled. However, later, we realized that there were improvements required in Verizon EdgeCast.

The initial setup was easy. I used to provide all the configuration details required from our end, and Verizon would configure the product. Then, we would verify or validate the configuration and push it to production.

The product is cheaper compared to other solutions.

I have worked on the solution from scratch. I have also evaluated and implemented it. The product is deployed on the cloud. Whether someone should choose the product would depend on the company’s requirements. We should evaluate the product based on our application and requirements before using it. If it fulfills our requirements, we should go ahead and use it. Overall, I rate the product a seven out of ten.

The tool's most valuable feature is the Uplynk platform for streaming purposes. 

The tool needs to resolve its lack of innovation. 

Edgio is stable. I rate it an eight out of ten. 

The solution is scalable.                                                           

Edgio's technical support is good. 

The tool's deployment is easy. 

With the rise of AI, people want products with AI-driven features. For instance, manipulating video in the cloud by pulling out exciting segments from a live stream. People want to see these advanced features integrated into their tools. Amazon has the resources, technology, and incentive to provide these features, and they are likely to deliver on them. The real question is whether their competitors can and will do the same.

The tool in question isn't just a single tool but a collection of features. It has been around for a while, so a business user with some experience can manage them.

I rate the overall product a seven out of ten. 

I manage CDN configurations for my customers.

We use this solution to ensure availability and performance for all of the websites we manage.

We are able to accelerate websites all around the world while they are hosted in a single location.

We are a partner of Verizon Edgecast and we resell Verizon Edgecast CDN to our customers. We plan the right configuration for their needs after we learn about their business, and we advise them of which features would be good for them to use. Following this, we do the complete CDN configuration, new releases, maintenance, etc.

Two years ago, Verizon Egdecast CDN introduced the last version of their Rules Engine (V4). It's a very powerful tool and it's a significant improvement from the previous system.

It allows you to write a complete ruleset in the XML language. You can export an entire caching ruleset, modify it using the tool you want, and after that, you can import the new ruleset into the system. It helps a lot for deploying many configurations quickly, and to adapt existing configurations from one customer to another with the same need.

The performance and stability of the Verizon Edgecast network are very appreciable for us because our customers don't experience issues frequently. For us as a partner, it's important.

The Rules Engine V4 is the most valuable feature. It's the system to write all of the rules that control the behavior of the website. You control the CDN caching configuration, but also rewrites, redirects, and all kinds of request transformations from the client to the origin server, as well as response transformation when the answer is sent from the origin server to the client.

The system allows you to deploy your ruleset in a "Staging" environment, so that you can test the behavior of the rules, using your real web resources. Essentially, you test your own website but without impacting production. Once your tests are done and OK, you can deploy the same ruleset in production.

The web interface of the Verizon Edgecast portal is very old. It's not user-friendly, slow, and it is missing some valuable features like the ability to make bulk changes. I really hope they are developing a new portal web interface.

A lot of reports are available but not always adapted to your needs.

Another thing is the number of options; a lot of features are available but most of them require users to subscribe to an option. So, it's powerful because you can address all kinds of needs, but it can be very expensive because of the options.

The deployment time of the rules is too long compared to other CDN providers. You need 45 minutes to have a new ruleset live-deployed in production, whereas it takes less than one minute for some other CDN providers. This is something that really needs to be improved.

We have been using Verizon EdgeCast for more than four years.

This product is very stable. In the last four years, we haven't experienced a lot of issues coming from Verizon CDN. There are less than 10 incident impacting us for more than 1,000 websites managed. We can observe fast and stable response times through our monitoring systems, with no degradation during the time, so for me, once correctly setup it's a very stable solution.

It's a cloud solution and it becomes bigger every day to absorb the increasing load, so scalability is not a problem for us.

The support is sometimes not very quick to answer, but generally, the answers are accurate. For me, the support is good.

We did not use another solution prior to this one.

The initial setup is complex, so you need to practice a lot to be able to do exactly what you want.

We are a partner of Verizon Edgecast CDN, so we install and deploy configurations for our customers.

Be careful about the options because to have all the features can be very expensive. Also, pay attention to the SSL cost because each SSL certificate deployed is billed individually.

We did not evaluate other options.

I recommend this solution because, for me, it's one of the most efficient and performant CDN operators. The web interface is old but the delivered service is very good.

Our web servers are leveraging it. We park our assets with Verizon EdgeCast, but the actual dynamic feature is on our site. People are still calling back to our sites, but our assets are cashed with the CDN.

Without EdgeCast, our website was taking 10 to 15 seconds to load. With EdgeCast, it loads under five seconds. It's a good product.

Verizon does a good job of cashing our assets and it integrates with our current web offering.

It's super easy to use and integrate with.

Verizon EdgeCast is great in the US and they have good coverage. Globally they do have endpoints, but compared to CloudFront with AWA or Cloudflare, they have less of a reach. 

The comparable features that we are looking at fits into Cloudflare's free version, as opposed to Verizon EdgeCast, which we are paying for.

In the next release, I would like to see more global endpoints for their CDN and a lower price.

We have been using Verizon EdgeCast for approximately ten years.

The stability is rock solid and we have not had any problems with it.

This solution is scalable. I would rate it an eight out of ten. In the US it's great in the network, but globally not as much. Overall, it's okay.

The entire company uses this solution. We have 100,000 users who pass through monthly, so we use it pretty heavily.

Technical support is great. The customer service is awesome.

EdgeCast is really easy to setup.

The most complex is CloudFront from AWS. Cloudflare is easy, as is EdgeCast.

The pricing needs to be reduced because it's expensive.

Cloudflare is super cheap; it's $300 a month for a website if you want all of its features.

AWS Cloudfront is paid per request.

When I modeled it out, we are spending somewhere between $600 to $800 a month with Verizon EdgeCast. If we go with AWS and have them do the exact same thing with Cloudfront, were looking at $30, and Cloudflare is free.

It's a phenomenal product, but it comes down to price. Cloudflare is substantially cheaper, which is one of the reasons that people chose it.

I would rate this solution an eight out of ten.