At the end of last year we wrote a blog post “One year of measuring WebRTC quality”, reflecting on our first full year of operations. As the second full year of operations is coming to an end, we would like to share with you our progress and will start sharing some key WebRTC metrics from our service in the form of a new report series.

Callstats.io progress

In 2016, we grew our deployment from under 50 products using callstats.io to over 200. Between May and October 2016, our install-base increased 20% month on month and the traffic grew by 9x. Our active customers are located world-wide, lead by U.S and followed by Europe, China, and Russia.

In September we announced our series A funding round. The funding will help us grow our team, and serve our customers better with an enhanced product and wider range of supported platforms.

The callstats.io team is now 14 strong, grown from eight at the beginning of 2016. We will keep growing the team in 2017 to speed up our development cycle. We have great features planned for 2017. Sign up for our newsletter at www.callstats.io/newsletter-signup/ to get notified about major feature releases.

Key WebRTC insights

Through 2016, we spoke at various events, for example Enterprise Connect, and shared insights from across our deployments. In December, we published the WebRTC Metrics Report 2016/01. This report is the first one from the series, we will publish an update every quarter, with the next one planned for March 2017. Since this is the first report, we are going through the last six months of sessions, May-October 2016.

To give you an overview of the report we have put together a summary of the metrics presented in the report:

1. Microsoft Windows dominates the WebRTC desktop market share ≈ 40%.
2. Google Chrome dominates the WebRTC browser market share. a. Chrome 72% (includes variants, like Opera). b. Firefox 19%. c. Other 9% (includes native apps, like Electron and WebView).
3. About 50% of the sessions have two participants, and a growing number (up to 40%) have 3 participants`.
4. About 16% of the sessions are audio-only sessions.
5. About 4% of the sessions fail to set up due to NATs and firewall traversal. a. Since February, the failures improved from 12% to 4% because more services deployed variants of TURN relay servers, e.g., TURN/ TCP.
6. 3% of the sessions have disruptions.
7. 5% of the sessions fail to re-establish the connection.
8. 18% of sessions experience churn.
9. 2% of the sessions use IPv6. a. The gateways, TURN servers, and media servers are often on infrastructures where IPv6 support is poor or not preferred.
10. 23% of the sessions use a TURN server. Of the relayed sessions, 80% use TURN/UDP and rest uses either TURN/TCP or TURN/TLS.
11. Improvements to ICE pacing in Chrome, reduced the setup times to 100ms for 20% of the sessions.
12. 77% of the sessions have no packet loss.
13. 80% of the sessions have less than 240ms RTT.
14. 70% of the audio sessions have > 30 kbps.
15. 50% of the video sessions have > 1Mbps.