Closed
Bug 1311714
Opened 8 years ago
Closed 7 years ago
Taipei Bandwidth Issues - Lagging AirMo Stream
Categories
(Infrastructure & Operations Graveyard :: NetOps: Other, task)
Infrastructure & Operations Graveyard
NetOps: Other
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: trecendez, Assigned: dcurado, NeedInfo)
Details
**Created from INC0021547** The loading speed of the AirMo is slow. The video playback is really slow as well (i.e. waiting the circling for seconds, and then playback for less than half a second, and then waiting the circling again and again). ref: https://air.mozilla.org/monthly-speaker-series-metadata-with-harlo-holmes-2016-10-12/ ref: https://air.mozilla.org/diversity-inclusion-roadshow-asia-australia-newzealand-2016-10-12/ " Ni-Ya Li (Linear, 李霓雅) Reply/Additional comments 2016-10-18 23:39:50 a day ago I encountered the same issue here. Looks like the cdn doesn't work well. I took 938 seconds to complete loading one single airmo page. (url: https://air.mozilla.org/monthly-speaker-series-metadata-with-harlo-holmes-2016-10-12/) " "Ni-Ya Li (Linear, 李霓雅) Reply/Additional comments 2016-10-18 23:49:00 a day ago During that delay, I pinged air.cdn.mozilla.net, which seems to be where the file is located according the network monitor on Firefox, I got average ping time around 45ms. Linears-MacBook-Pro-3:~ linear$ ping air.cdn.mozilla.net PING d160v71r9ipv9i.cloudfront.net (54.192.127.13): 56 data bytes 64 bytes from 54.192.127.13: icmp_seq=0 ttl=242 time=44.583 ms 64 bytes from 54.192.127.13: icmp_seq=1 ttl=242 time=45.975 ms It looks reasonable to me to a cloudfront Japan node, though I don't know why it directed us to Japan node while there actually has nodes at Taipei."
Assignee | ||
Comment 1•8 years ago
|
||
Here's the thing about this problem: - Is the problem with your ISP connection in Taipei? Like, is all connectivity to systems outside the office slow and problematic? or - Is it that the content from CloudFront is the problem? If it is the latter of these two, and I believe it is, then this is a problem with AWS, and not something Netops can control.
Assignee: network-operations → dcurado
Status: NEW → ASSIGNED
Flags: needinfo?(trecendez)
Comment 2•7 years ago
|
||
I'm going to close this bug. We're looking at new carriers but I expect latency to continue to be troublesome due to the overall distance. Any issues
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•2 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•