On Dec 9, 2011, at 1:37 PM, Franck Martin wrote:
I just had a personal email from a brand new ISP in the Asia-Pacific area
desperately looking for enough IPv4 to be able to run their business the way
they would like…
This is just a data point.
Franck -
Thanks for the data point -
On 11/12/2011, at 2:37 PM, valdis.kletni...@vt.edu wrote:
On Sat, 10 Dec 2011 20:48:45 EST, Barry Shein said:
I just had a personal email from a brand new ISP in the Asia-Pacific
area desperately looking for enough IPv4 to be able to run their
business the way they would like?
This
On 12/10/11, NetSecGuy netsec...@gmail.com wrote:
I have a Linode VPS in Japan that I can't access from Verizon FIOS,
but can access from other locations. I'm not sure who to blame.
I can't get to 106.187.34.33 or 106.187.34.1 using Verizon FIOS
C:\tracert 106.187.34.33
Tracing route to
I should have included reverse traces to begin with. No firewall on VPS.
Trace from the VPS to a router close to me.
traceroute to 130.81.199.4 (130.81.199.4), 64 hops max, 40 byte packets
1 106.187.33.2 (106.187.33.2) 1 ms 0 ms 0 ms
2 124.215.199.121 (124.215.199.121) 6 ms 1 ms 13 ms
I believe 130.81 is blocked. Traceroute to your gateway address.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
NetSecGuy netsec...@gmail.com wrote:
I should have included reverse traces to begin with. No firewall on VPS.
Trace from the VPS to a router close to me.
On Sat, Dec 10, 2011 at 11:49 AM, NetSecGuy netsec...@gmail.com wrote:
I have a Linode VPS in Japan that I can't access from Verizon FIOS,
but can access from other locations. I'm not sure who to blame.
The host, 106.187.34.33, is behind the gateway 106.187.34.1:
From FIOS to 106.187.34.1
From 90701 - Artesia, CA. FIOS
No Go here too!!!
C:\WINDOWS\system32tracert 106.187.34.1
Tracing route to gw-li377.linode.com [106.187.34.1]
over a maximum of 30 hops:
122 ms34 ms1 ms Tomato [192.168.100.1]
249 ms 1 ms 1 ms Verizon [192.168.1.1]
336 ms
Feel free to contact peering@netflixdotcom - we're happy to provide you with delivery statistics for
traffic terminating on your network.
Regards,
-Dave Temkin
Netflix
On 12/7/11 8:57 AM, Blake Hudson wrote:
Yeah, that's an interesting one. We currently utilize netflow for this, but you also
I hope it's not an outdated martian problem firewall or route filter. For the
Traceroute from linode to FiOS, Traceroute to the FiOS gateway address.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Network IP Dog network.ip...@gmail.com wrote:
From 90701 - Artesia, CA.
from home lan
% traceroute gw-li377.linode.com
traceroute to gw-li377.linode.com (106.187.34.1), 64 hops max, 52 byte packets
1 192.168.0.1 (192.168.0.1) 1.471 ms 0.725 ms 0.555 ms
2 tokyo10-f03.flets.2iij.net (210.149.34.72) 7.241 ms 6.651 ms 6.939 ms
3
I too am now experiencing issues. I cannot get to www.cisco.com and various
websites.
Some websites work lightning quick, some take a long time to load, and some
just don't load at all.
Date: Mon, 12 Dec 2011 09:55:40 +0900
From: ra...@psg.com
To: nanog@nanog.org
Subject: Re:
Which leads to a question to be asked...
Is netflix willing to peer directly with ISP / NSP's ?
Regards.
Faisal Imtiaz
Snappy Internet Telecom
On 12/11/2011 7:29 PM, Dave Temkin wrote:
Feel free to contact peering@netflixdotcom - we're happy to provide
you with delivery statistics for
Netflix uses CDNs for content delivery and the platform runs in EC2. What would
peering with them achieve?
Sent from my iPhone
On Dec 11, 2011, at 18:06, Faisal Imtiaz fai...@snappydsl.net wrote:
Which leads to a question to be asked...
Is netflix willing to peer directly with ISP / NSP's
I'm seeing the same thing from my home lan via fios. I've run a recursive dns
server for years and can't reach the roots. Had to switch to using verizon's
dns servers as forwarders.
Sent from my iPad
On Dec 11, 2011, at 8:07 PM, Brandon Kim brandon@brandontek.com wrote:
I too am now
On Sun, 11 Dec 2011 19:21:49 PST, Joel Jaeggli said:
Netflix uses CDNs for content delivery and the platform runs in EC2. What
would peering with them achieve?
I suspect Faisal's *real* question is Who at Netflix do I talk to in order to
discuss
mutually beneficial traffic engineering?
Simple, keep traffic off paid ip transit circuits
Faisal
On Dec 11, 2011, at 10:21 PM, Joel Jaeggli joe...@bogus.com wrote:
Netflix uses CDNs for content delivery and the platform runs in EC2. What
would peering with them achieve?
Sent from my iPhone
On Dec 11, 2011, at 18:06,
On Sun, Dec 11, 2011 at 3:11 PM, Joseph Snyder joseph.sny...@gmail.com wrote:
I believe 130.81 is blocked. Traceroute to your gateway address.
portions (at least) of that are 19262's loopback/ptp space, they
block/rate-limit toward that at their edge.
On Sun, Dec 11, 2011 at 10:28 PM, Matthew Huff mh...@ox.com wrote:
I'm seeing the same thing from my home lan via fios. I've run a recursive dns
server for years and can't reach the roots. Had to switch to using verizon's
dns servers as forwarders.
business or consumer fios?
3
On Sun, Dec 11, 2011 at 10:46 PM, Faisal Imtiaz fai...@snappydsl.net wrote:
Simple, keep traffic off paid ip transit circuits
(I think joel's point was: peer with amazon, done-and-done)
Faisal
On Dec 11, 2011, at 10:21 PM, Joel Jaeggli joe...@bogus.com wrote:
Netflix uses CDNs for
Consumer fios. Verizon forums are full of posts about it. Too tired this
evening to worry about it.
Sent from my iPad
On Dec 11, 2011, at 10:48 PM, Christopher Morrow morrowc.li...@gmail.com
wrote:
On Sun, Dec 11, 2011 at 10:28 PM, Matthew Huff mh...@ox.com wrote:
I'm seeing the same thing
Thanks for the explanation...did not consider that before...will investigate..,
any tips that can be shared will be welcome.
:)
Faisal
On Dec 11, 2011, at 10:49 PM, Christopher Morrow morrowc.li...@gmail.com
wrote:
On Sun, Dec 11, 2011 at 10:46 PM, Faisal Imtiaz fai...@snappydsl.net wrote:
On 12/11/11 19:49 , Christopher Morrow wrote:
On Sun, Dec 11, 2011 at 10:46 PM, Faisal Imtiaz fai...@snappydsl.net wrote:
Simple, keep traffic off paid ip transit circuits
(I think joel's point was: peer with amazon, done-and-done)
also probably your relationships to akamai and level3
On 12/12/2011, at 4:18 PM, Joel jaeggli wrote:
also probably your relationships to akamai and level3
Probably want to add Limelight to that list as well (do Netflix even use Akamai
these days?)
-Shaun
smime.p7s
Description: S/MIME cryptographic signature
On Sun, 11 Dec 2011, Christopher Morrow wrote:
On Sun, Dec 11, 2011 at 10:46 PM, Faisal Imtiaz fai...@snappydsl.net wrote:
Simple, keep traffic off paid ip transit circuits
(I think joel's point was: peer with amazon, done-and-done)
DirectConnect seems to be a good way to get a
On Sun, Dec 11, 2011 at 10:54 PM, Matthew Huff mh...@ox.com wrote:
Consumer fios. Verizon forums are full of posts about it. Too tired this
evening to worry about it.
:( I'll have to do some testing when I get near a consumer fios
then... So, they squash all DNS NOT to their complexes, that
We're having strange issues in NYC metropolitan area.
We can trace from Verizon FIOS to some IP addresses of our ASN 11579
block. Others don't work. The IP's that don't work seem to die at
130.81.107.228 on the Verizon network.
Something is rotten in Denmark. Or NY. You know what I mean.
On
On Mon, Dec 12, 2011 at 1:26 AM, Adam Greene maill...@webjogger.net wrote:
130.81.107.228
hrm... LCR == lata-core-router... something fairly close to you, like
2 router-hops from your first L3 hop... sounds like someone ought to
call the vz customer service line and ask for a fix :)
Yep, tried that. Connected with a lower level tech who would not escalate.
Anyone know a Verizon NOC direct contact #?
On 12/12/2011 2:17 AM, Christopher Morrow wrote:
On Mon, Dec 12, 2011 at 1:26 AM, Adam Greenemaill...@webjogger.net wrote:
130.81.107.228
hrm... LCR == lata-core-router...
28 matches
Mail list logo
