Re: DOs and DONTs for small ISP

On 6/3/19 9:56 AM, Jon Lewis wrote: 3) Don't advertise one transit provider's routes to another.  Each should    be filtering your routes, but you never know.  Come up with, and use    BGP communities to control route propagation.  As you grow, it sucks    having to update prefix-list filters 

Re: HE.NET Contact / Outage

We go through waves. Stable for months, then rocky for a month, then stable, then rocky. We buy full transit from them, so have contemplated switching to peering only to reduce the issues. On Mon, Jun 3, 2019 at 2:22 PM TJ Trout wrote: > We use HE transit here in California from multiple pops fo

Re: HE.NET Contact / Outage

We use HE transit here in California from multiple pops for the last 7+ years and I can only think of one outage ever On Mon, Jun 3, 2019 at 11:16 AM Dovid Bender wrote: > We had an issue in NY as well and they blamed a router in ASH as well. Our > solution was to route away. > > > On Mon, Jun 3

Re: DOs and DONTs for small ISP

On Mon, Jun 3, 2019 at 2:55 PM Fletcher Kittredge wrote: > > > I would respectfully point out that my point about the importance of finding > the right partners. For you, sounds like it was good to have opportunity to > get out of this venture. Oh, goodness yes -- however, I *still* have barel

Re: DOs and DONTs for small ISP

I would respectfully point out that my point about the importance of finding the right partners. For you, sounds like it was good to have opportunity to get out of this venture. On Mon, Jun 3, 2019 at 2:40 PM Warren Kumari wrote: > On Mon, Jun 3, 2019 at 1:09 PM Fletcher Kittredge > wrote: > >

Re: Google Post Master experiences

This is probably best asked on the mailop list (where some Google personnel hang out): subscribe via mailop-requ...@mailop.org. ---rsk

Google Post Master experiences

Folks, I had a domain get blacklisted from too much spam on April 22nd of this year. Long story short my mom clicked on something she shouldn’t have and compromised her e-mail. Spam was stopped within a day of noticing. Since then I have implemented Domain Keys, feedback loop, DMARC, etc. T

Re: DOs and DONTs for small ISP

We have a fledgling web-site with information at http://startawisp.info/ Justin Wilson j...@mtin.net https://j2sw.com https://blog.j2sw.com > On Jun 3, 2019, at 10:35 AM, Mehmet Akcin wrote: > > https://startyourownisp.com/ this is al

Re: DOs and DONTs for small ISP

On Mon, Jun 3, 2019 at 1:09 PM Fletcher Kittredge wrote: > > > Here is your checklist in descending order of importance: > > market opportunity > finding the right partners (see below) > financial > sales and marketing > organizational capacity and HR > legal, regulatory > capital acquisition > se

Re: HE.NET Contact / Outage

We had an issue in NY as well and they blamed a router in ASH as well. Our solution was to route away. On Mon, Jun 3, 2019 at 2:11 PM Jared Geiger wrote: > We had a similar issue at 5AM Pacific time in Ashburn VA. They blamed it > on a software bug and disabled that feature. > > We had another

Re: HE.NET Contact / Outage

We had a similar issue at 5AM Pacific time in Ashburn VA. They blamed it on a software bug and disabled that feature. We had another outage at the same time a week before also. They blamed it on a route table corruption that time. On Mon, Jun 3, 2019 at 10:06 AM David Deutsch wrote: > Hi Everyo

Re: DOs and DONTs for small ISP

On Mon, Jun 03, 2019 at 01:48:33PM +, Mel Beckman wrote: > I’m constantly amazed at the number of even medium-sized ISPs that have no > network monitoring. An NMS should go in as the first software component — > before billing starts and the provider is on the hook to deliver. often

Re: DOs and DONTs for small ISP

Here is your checklist in descending order of importance: 1. market opportunity 2. finding the right partners (see below) 3. financial 4. sales and marketing 5. organizational capacity and HR 6. legal, regulatory 7. capital acquisition 8. security 9. ... 10. ... 11

HE.NET Contact / Outage

Hi Everyone, We experienced a pretty bad HE.NET outage on Friday, May 31st where fiber/BGP were up on our side out of LAX and our route advertisements where forwarded to public ASs; however packets stalled midway in the HE network. Urgent calls to their NOC escalating in the morn

Re: DOs and DONTs for small ISP

https://startyourownisp.com/ this is also pretty good, just thought i would share.. On Mon, Jun 3, 2019 at 7:19 AM Mikael Abrahamsson wrote: > On Mon, 3 Jun 2019, Mehmet Akcin wrote: > > > I am putting together a public DOs and DONTs blog post and would love to > > hear from those who have built

Re: DOs and DONTs for small ISP

On Mon, 3 Jun 2019, Mehmet Akcin wrote: I am putting together a public DOs and DONTs blog post and would love to hear from those who have built ISPs and have recommendations from Billing to Interconnection, Routing policy to Out of the band & console setup, Software recommendations, etc. Botto

Re: DOs and DONTs for small ISP

On Mon, 3 Jun 2019, Mehmet Akcin wrote: hi there, I know there are folks from lots of small ISPs here and I wanted to check-in on asking few advice points as I am involved building an ISP from green-field. Usually, it's pretty straight forward to cover high-level important things, filters, r

Re: DOs and DONTs for small ISP

thank you, great start, just want to jump start to technical part AFTER deciding to start the ISP, and focus on operational, technical, and administrative things though. Question is no longer whether starting ISP is a good idea or not (but i agree this is needed and was already completed) thanks ag

Re: DOs and DONTs for small ISP

I’m constantly amazed at the number of even medium-sized ISPs that have no network monitoring. An NMS should go in as the first software component — before billing starts and the provider is on the hook to deliver. The second lacking component is a ticket system, which is silly because turnkey

Re: DOs and DONTs for small ISP

Mehmet, I think this is a cool idea, perhaps a good format for the documentation would be something along the lines of an “awesome list”? (https://github.com/sindresorhus/awesome) Chris From: NANOG on behalf of Mehmet Akcin Date: Monday, June 3, 2019 at 07:06 To: nanog Subject: DOs and DONT

DOs and DONTs for small ISP

hi there, I know there are folks from lots of small ISPs here and I wanted to check-in on asking few advice points as I am involved building an ISP from green-field. Usually, it's pretty straight forward to cover high-level important things, filters, routing policies, etc.but we all know the devi

Contact with AS3216 VEON

Hi, somebody knows a valid contact for VEON AS3216 ? The contacts written on PeeringDB are invalid, nobody answer at direct email. Thanks for your help. Regards, -- Marco Paesani Skype: mpaesani Mobile: +39 348 6019349 Success depends on the right choice ! Email: ma...@paesani.it

spam and GDPR (was something else)

On 2019-06-02 00:51, Mark Rousell wrote: > On 31/05/2019 16:02, Niels Bakker wrote: >> Which is why we now have GDPR.  Care, or get fined. > > Not quite so simple, though, is it. If you want to make a complaint then > you have to get your EU national data protection regulator interested. What s