Live Event Report: U2 Webcast (Oct 10th, 2001)
 
Stream URLs

"Camera 1"  rtsp://go.rbn.com/u2/u2_cams/band1/live/cam1.rm
"Camera 2"  rtsp://go.rbn.com/u2/u2_cams/band2/live/cam2.rm
"Camera 3"  rtsp://go.rbn.com/u2/u2_cams/band2/live/cam3.rm
"Camera 4"  rtsp://go.rbn.com/u2/u2_cams/band2/live/cam4.rm
"Concert"    rtsp://go.rbn.com/u2/u2_stage/live/concert.rm

Live Event Duration From [ 10-Oct-01 21:00:00 PM ] To [ 10-Oct-01 22:30:00 PM ] ( Duration: 1:30:0 )
Report Date13-Oct-01 1:42:06 PM
Time ZoneGMT-05:00
#3061-25
Introduction
On October 10th, Streamcheck monitored the live U2 concert webcast from Notre Dame, Indiana. The two hour event was hosted by Tiscali in Europe and RBN in the United States. 5 different streams were available to users who went to the concert website: 4 camera angles and a mixed feed.

Streamcheck used measurement computers (scanners) in 12 cities throughout the US, Canada and Europe. Each scanner is equipped with software that mimics the behavior of a regular streaming user. In this case, the streams were presented only in RealPlayer format but Streamcheck can also measure Windows Media streams.

The webcast was monitored from 9:00pm to 11:30pm EDT. Each stream was checked approximately 125 times during that period (i.e. a checking frequency of 50 checks per hour). Each check lasts 60 seconds during which the scanner attempts to connect to the streaming server and render the content.


This report, and all of its corresponding data, is copyrighted material belonging to Streamcheck. No reproduction or transmission is allowed without express written consent from Streamcheck. For more information, contact Streamcheck. "Streamcheck" and "StreamQ" are registered trademarks of Streamcheck.

Summary Graphs

Legend
Below is shown the locations of the scanners involved. More detail on the locations can be found in the "Location List" table in the "Summary Data" section. Also shown is a color scale calibrated to the quality range experienced during the event. (For this event, no StreamQ™ lower than B- was measured.) StreamQ™ is Streamcheck's proprietary metric that evaluates the end-user experience. It is based on start-up time and the number of interruptions in the first minute.
Quality Snapshots
Four time snapshots, separated by 30 minute intervals, are shown below. The StreamQ™ in each location is shown with a colored circle corresponding to the legend above. The quality was at its lowest during the 10:00pm snapshot.

Summary Data

Ability To Connect
- OverallLA- 1Dal-1 Alex- 1Hobo-1Balt- 1Kans-1Atla- 2Tor-4Chic- 1Bost-1Lon- 1Ger-1
Checks Performed776968668646258446056726644
Percentage of Overall Total Checks100.0%12.4%11.1%8.8%8.2%8.0%7.5%5.7%7.7%7.2%9.3%8.5%5.7%
Successful Connections754948668625856405654726642
Percentage of Total Checks97.2%97.9%100.0%100.0%96.9%93.5%96.6%90.9%93.3%96.4%100.0%100.0%95.5%
Failed Connections 22200242442002
Percentage of Total Checks 2.8%2.1%0.0%0.0%3.1%6.5%3.4%9.1%6.7%3.6%0.0%0.0%4.5%
Frustration Time & StreamQ™ (Successful Checks Only)
(Avg Per Check)OverallLA-1Dal-1 Alex-1Hobo-1Balt-1Kans-1Atla-2Tor-4Chic-1Bost-1Lon-1Ger- 1
-%- %-%-%-%-%-%-%-%-%-%-%-%
Frustration Time (sec)7.71006.71007.31007.51007.71008.71007.81007.91007.31007.61007.71008.41009.6100
Connection Time (sec)1.418.21.116.11.317.91.215.71.316.42.124.61.215.61.215.11.216.11.115.01.418.71.923.12.222.8
Buffer Time (sec)6.380.85.783.96.082.16.384.36.483.66.675.46.481.76.884.96.183.96.585.06.381.36.274.46.769.3
Rebuffer Time (sec)0.11.00.00.00.00.00.00.00.00.00.00.00.22.80.00.00.00.00.00.00.00.00.22.50.87.9
Bit Rate Achieved (Successful Checks Only)
-OverallLA-1Dal-1 Alex-1Hobo-1Balt-1Kans-1Atla-2Tor-4Chic-1Bost-1Lon-1Ger-1
Average Bit Rate (kbps)78.770.675.178.382.284.683.485.780.783.274.077.879.3
Lowest Bit Rate (kbps)26.026.026.026.033.064.040.081.033.029.026.027.035.0
Highest Bit Rate (kbps)100.092.094.090.093.096.093.094.088.091.0100.0100.0100.0
Location List
Location NameDescriptionLocation NameDescription
LA- 1Los Angeles CA (UUNet Sprint ...)Dal-1Dallas TX (Genuity Qwest ...)
Alex-1Alexandria VA (Verio)Hobo-1Hoboken NJ (Qwest)
Balt-1Baltimore MD (Level3 UUNet ...)Kans-1Kansas City MO (UUnet GlobalCrossing ...)
Atla-2Atlanta GA (UUNet Sprint ...)Tor-4Toronto ON (UUNet)
Chic-1Chicago IL (UUNet GlobalCrossing ...)Bost-1Boston MA (Genuity UUNet ...)
Lon-1London UK (Level 3)Ger-1Dusseldorf Germany (UUNet)

Detail Graphs

Connection Success Rate by Location
Below is shown the total success rate from each location, for all five streams monitored. Alexandria and Dallas had perfect connectivity which is typical, given that those two cities are major internet hubs for North America. Atlanta, Toronto and Baltimore had the worst connectivity.
Frustration Time by Location
Here you can see how the user experience varied across different locations. The stacked bar graph shows connection time (red), buffer time (green) and rebuffer time (cyan). The connect time from the Germany scanner to the servers was double the average time, possibly indicating DNS issues. Germany also had the most rebuffering (interruptions) which are very detrimental to user experience. Note that although the London scanner had 100% availability, it had longer-than-average connect times and some rebuffering.
Bitrate by Location
This graph shows the average bit rate experienced from each scanner across all five streams.
Bitrate Over Time
This graph shows how bitrate varied across time from all scanners and for all streams. The blue squares represent individual checks. The steep drop in bitrate at 10:45 reflects the end of the concert and the switch to a looping "Thanks for watching" message, encoded at 30k. That data isn't reflected in any of the numbers or graphs above because checks after 10:30pm were trimmed away.