The following dashboards showcase the most up-to-date insights from STL Partners’ Telco Cloud Deployment Tracker. Our tool is interactive and contains different high-level analysis and underlying data of what operators have done (and plan to do) globally in telco cloud. In-depth analysis can be found in our accompanying reports.
Any deployments with ‘Null’ as the deployment year below are ‘In progress’ or ‘Pending’ deployments. See explanatory notes and definitions at the bottom of the page.
Summary of total deployments
Deployments by operator
Deployments by vendor
Definitions and explanatory notes
Deployments and deployment numbers
- We define as a ‘deployment’ the implementation of a given VNF and any named sub-components, or of a whole NFV or SDN solution including several explicitly referenced VNFs and components.
- A deployment can also be the roll-out of a VNF and supporting infrastructure across multiple subsidiaries of an operator group, which are counted as a single deployment, even though there are multiple instances of it.
- In our dashboards, we show both the deployments and all of the components involved, including information on the vendor and vendor solutions where known.
- In our ‘Detailed dataset’ worksheet, we have numbered the deployments from 1 to 748 to make this distinction between deployments and deployed components clearer. The numbering is determined by alphabetical order of region where the operator is based, and then by operator names and chronological order of deployments.
- Dates are presented in the form ‘Jan-20, ‘Feb-20’, etc. Dates showing the month of December (e.g. Dec-19) mean ‘by the end of 2019’, unless we have added a comment stating explicitly that the month of December of that year was the deployment / go-live date. In all other cases, where we have shown a December date, this means that the precise date / month of the deployment is not known, but we have information or are confident that the deployment went live by the end of that year.
- The names of operators – shown in the dashboards and column C of the ‘Detailed dataset’ worksheet – are those of the operator group parent company, where applicable. If the local operating subsidiary carrying out the deployment has a different name from the parent company, this is shown in column H in the worksheet.
Country where operator based vs country where deployment is carried out
- In our dashboards, a deployment is assigned to a given region (e.g. Asia-Pacific (APAC)) if it occurred in that region or if it was carried out on a global basis by a telco based in that region. Consequently, the total deployments for Asia-Pacific also include those carried out by or at local subsidiaries of telco groups based outside Asia-Pacific.
- In column D of the ‘Detailed dataset’ worksheet, we show the country where the operator or operator group is based. If the country where the deployment has taken place differs from the location of the company’s head office or domestic market, we show the country where the deployment was carried out in column F.
- Deployments that have not yet been completed, or not been announced as completed, we categorise as either ‘in progress’, ‘planned’ or ‘retired’ (these are marked as ‘Null’ in our dashboards on the ‘Year implemented’).
- ‘In progress’ means that the deployment is ongoing; ‘planned’ means the deployment was announced but we are not sure how far it has progressed; and ‘retired’ means that the deployment was completed and went live, but the solution has now been taken out of commercial operation.
- We continue to show retired deployments for the purposes of historical trends analysis.
Our regional key:
APAC: Asia Pacific (including Central and Southern Asia)
NAM: North America (including the Caribbean)
ME: Middle East
LAM: Latin America (including Central America)