@ChromeDevTools I recently noticed that the network timings don't quite add up (number in red is the actual sum). I wonder what's missing?pic.twitter.com/4Gs6YF9KCj
Official account. Follow for latest news, features, tips, handy extensions and more.
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Add this Tweet to your website by copying the code below. Learn more
Add this video to your website by copying the code below. Learn more
By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.
| Country | Code | For customers of |
|---|---|---|
| United States | 40404 | (any) |
| Canada | 21212 | (any) |
| United Kingdom | 86444 | Vodafone, Orange, 3, O2 |
| Brazil | 40404 | Nextel, TIM |
| Haiti | 40404 | Digicel, Voila |
| Ireland | 51210 | Vodafone, O2 |
| India | 53000 | Bharti Airtel, Videocon, Reliance |
| Indonesia | 89887 | AXIS, 3, Telkomsel, Indosat, XL Axiata |
| Italy | 4880804 | Wind |
| 3424486444 | Vodafone | |
| » See SMS short codes for other countries | ||
This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.
Hover over the profile pic and click the Following button to unfollow any account.
When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.
The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.
Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.
Get instant insight into what people are talking about now.
Follow more accounts to get instant updates about topics you care about.
See the latest conversations about any topic instantly.
Catch up instantly on the best stories happening as they unfold.
@ChromeDevTools I recently noticed that the network timings don't quite add up (number in red is the actual sum). I wonder what's missing?pic.twitter.com/4Gs6YF9KCj
Compared this to the corresponding resource timing entity and found time between connectEnd and requestStart seems to be the missing thing.pic.twitter.com/PmkcBVOHY5
I wonder what Chrome is doing here? Can you share some insights?
Hi! Have same issue. Did you solve it? In my situation I have about 160 seconds! of lag...
No, I didn't find what caused the time difference. But it also wasn't really an issue for me. It was just a 0.1ms difference between API and devtools. I was curious why.
I've got @Souders article about it http://www.stevesouders.com/blog/2014/08/21/resource-timing-practical-tips/ … could be helpfull. But still no idea why it is happaning in my environment. Thanks.
Probably just some other uncommon edge case that we're not accounting for. If you can reproduce it reliably, we can look into it.
Sure, I can. I have Real User Monitoring and it's happannig all the time in my environment. I've got several fronend servers, load balancer (nginx) and several backend servers. All it works in enterprice network. I appreciate your help, @ChromeDevTools.pic.twitter.com/S3OcRvIB5L
Can you open a ticket on http://crbug.com ? They'll need a URL and the steps to reproduce.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.