Re: transit and peering costs projections

On Sun, Oct 15, 2023 at 9:47 AM Dave Taht wrote: > [...] > The three forms of traffic I care most about are voip, gaming, and > videoconferencing, which are rewarding to have at lower latencies. > When I was a kid, we had switched phone networks, and while the sound > quality was poorer than toda

Re: Add communities on direct routes in Juniper

I believe you need to add the communities either on the import policy which pulls in the direct route or the export policy to the neighbor(s) you want to feed the communities to. Owen > On Oct 15, 2023, at 05:51, Jason R. Rokeach via NANOG wrote: > > Hi Stanislav, > I believe this is what

Re: transit and peering costs projections

I agree, but there are fortunately several large content networks that have had the forethought to put their stuff in Houston - Meta, Fastly, Akamai, AWS just to name a few… There is enough of a need to warrant those other networks having a presence, so hopefully it’s just a matter of time befor

Re: ARIN whois contact abuse from ipv4depot aka Silicon Desert International Inc

I’d vote for whoever promises to perma ban Cogent and all of these other clowns from access WHOIS data. Someone get on that! > On Oct 13, 2023, at 19:33, Randy Bush wrote: > > i received an arin board electioneering "vote for me" today. i guess > now i have to go vote against then. > > randy

Re: transit and peering costs projections

For starters I would like to apologize for cc-ing both nanog and my new nn list. (I will add sender filters) A bit more below. On Sun, Oct 15, 2023 at 9:32 AM Tom Beecher wrote: >> >> So for now, we'll keep paying for transit to get to the others (since it’s >> about as much as transporting IXP

Re: transit and peering costs projections

> > So for now, we'll keep paying for transit to get to the others (since it’s > about as much as transporting IXP from Dallas), and hoping someone at > Google finally sees Houston as more than a third rate city hanging off of > Dallas. Or… someone finally brings a worthwhile IX to Houston that get

Re: transit and peering costs projections

On Sat, 14 Oct 2023 16:01:54 -0700 Dave Taht wrote: > This set of trendlines was very interesting. Unfortunately the data > stops in 2015. Does anyone have more recent data? This may be of interest: Peering Costs and Fees John

Re: transit and peering costs projections

I’ve found that most of the CDNs that matter are in one facility in Houston, the Databank West (formerly Cyrus One) campus. We are about to light up a POP there so we’ll at least be able to get PNIs to them. There is even an IX in the facility, but it’s relatively small (likely because the opera

Re: [LibreQoS] transit and peering costs projections

Man, I wanna know where you’re getting 100g transit for $4500 a month! Even someone as fly by night as Cogent wants almost double that, unfortunately. On Oct 15, 2023, at 07:43, Jim Troutman wrote:  Transit 1G wholesale in the right DCs is below $500 per port. 10gigE full port can be had aro

Re: transit and peering costs projections

Houston is tricky as due to it's geographic scope, it's quite expensive to build an IX that goes into enough facilities to achieve meaningful scale. CDN 1 is in facility A. CDN 2 in facility B. CDN 3 is in facility C. When I last looked, it was about 80 driving miles to have a dark fiber ring th

Re: transit and peering costs projections

I've seen some attempts to put an IX at every corner, but I don't think those efforts will be overly successful. It's still difficult to gain sufficient scale in NFL-sized cities. Big content won't join without big eyeballs (well, not the national-level guys because they almost never will). Bi

Re: Add communities on direct routes in Juniper

Hi Stanislav, I believe this is what you are looking for: [edit] jcluser@Lothlorien-MX1# show | compare [edit interfaces lo0 unit 0 family inet] address 10.0.0.0/32 { ... } + address 5.5.5.5/32; [edit protocols bgp] - export IPV4-STATIC; + export [ IPV4-STATIC TAG-DIRECT ]; [edi

Re: [LibreQoS] transit and peering costs projections

Transit 1G wholesale in the right DCs is below $500 per port. 10gigE full port can be had around $1k-1.5k month on long term deals from multiple sources. 100g IP transit ports start around $4k. The cost of transport (dark or wavelength) is generally at least as much as the IP transit cost, and

Re: Add communities on direct routes in Juniper

Unfortunately not yet, as far as I know. Long time ago I gave this to my account team Title: Direct routes must support tag and or community Platform: Trio, priority MX80, MPC2 JunOS: 12.4Rx Command: 'set interfaxe ge-4/2.0 family inet address 10.42.42.1/24 tag|community X' JTAC: n

Add communities on direct routes in Juniper

Dear all, Is there a way to add BGP communities on direct (interface) routes in Junipers? The task looks to be simple but the solution eludes me. In Cisco/Arista, for example, I could use "network 192.0.2.0/24 route-map ". In Juniper it seems to be impossible. I even tried putting interface-ro

Re: transit and peering costs projections

Exactly. Speed x distance = cost. This is _exactly_ why IXPs get set up. To avoid backhauling bandwidth from Dallas, or wherever. Loss, latency, out-of-order delivery, and jitter. All lower when you source your bandwidth closer. -Bill > On Oct 15, 2023, a

Re: transit and peering costs projections

> On Oct 15, 2023, at 01:01, Dave Taht wrote: > I am under the impression that many IXPs remain very successful, I know of 760 active IXPs, out of 1,148 total, so, over 31 years, two-thirds are still successful now. Obviously they didn’t all start 31 years ago, they started on a gradually-acce