My NTT rep has contacted me with a "checkup" email. Maybe this is a good time to complain about the issues we had some months ago with latency / peering (who was it with? comcast?) that their NOC didn't want to fix... comcast and vz and centurylink Anyone have any current mtr's, smokeping, etc... evidence I can throw at them? @smokeping https://smokeping.cobryce.com/ :P (don't have mtr's for those destinations though ) brycec++ https://smokeping.cobryce.com/?displaymode=n;start=2014-10-02%2007:13;end=now;target=Internet.HENet I have hit fastmails 4000 inbound email per day per account limit using rss2email yea, i just have graphs could maybe find some mtrs on the logger when we talked about it lol mnathani (host in1-smtp.messagingengine.com[66.111.4.70] said: 451 4.7.1 : Recipient address rejected: Already reached per-day limit for messages from "SENDING@ADDRESS" of 4000, try again later (in reply to RCPT TO command)) seems from arp to LAX stuff is nasty high. everywhere else it's ok http://i.imgur.com/uqmZK9v.png I want Google Reader to come back agreed. miss google reader. I like r2e + gmail :D forgotten: what ARP-LAX stuff are you talking about? ARP is in LAX, is it not? Depending on the definition of LAX, yes :P @iata LAX LAX: Los Angeles International Airport located in Los Angeles, California, United States ARP is not in the airport :P thats the one brycec: looking at your graphs everything LAX is like almost a full second. 800ms, 758ms. etc etc where everything else is 50ms, or whatever. forgotten: those are us not ms oh? lol microseconds vs milliseconds latency too low for you forgotten: forgotten: 1ms is 1000us, so 694.8us is less than 1ms well then, fuck me. lol I... I don't swing that way, forgotten just this once bro just no kissing No way man, you're going to end up staring me in the eye and making this awkwarsd the bro part makes it less creepy fwiw, ARP-LAX.HE doesn't hit transit, it's a direct cross-connect c/o coresite/any2ix just like BAM http://i.imgur.com/PReALxk.png there's a graph w/the ntt stuff in full swing every night up_the_irons: ^ dunno if that's useful at all m0unds: ARP -> where? comcast actually, comcast -> arp in that case i don't bother with the inverse because it looks almost exactly the same hm so I should see it in my smokeping too depends on the route this only shows up with arp > sjc > denver > albuquerque And yet Comcast->arpnetworks.com is clean since it changes a few times a week *my heh sometimes it's arp > lax.comcast > abq, which is less than 30ms round trip right now, it's hitting gtt instead of ntt and it's been a smooth 40ms for a week or more Mine: cc.sea -> cc.lax -> gtt -> mzima -> arp oh, that's right, it was the return path that hit ntt, not outbound arp -> comcast was ntt, comcast -> arp was gtt/nlayer and mzima it's been a while since i've looked So it is lawl