ARIN Public Incident Report – 4.10 Misissuance Error
1–10 of 41 posts
Re: ARIN Public Incident Report – 4.10 Misissuance Error
#2On a sidenote, what I appreciate in both RIPE and ARIN is that you can have at least a proper discussion when you have valid arguments with their support teams.
Re: ARIN Public Incident Report – 4.10 Misissuance Error
#3As ARIN block owner this situation is kinda scary but reading this actually makes me think it's less likely to happen again .
Re: ARIN Public Incident Report – 4.10 Misissuance Error
#4A couple of years ago ARIN increased their fees considerably - way higher than fees paid to RIPE for way less resources - and had a call with their management to express my frustration, not because I was paying from my pocket but because of the high discrepancy of the what they wanted to get and the quantity/quality of their services. Now I can see that their backbone services haven't really improved while their inco…
Re: ARIN Public Incident Report – 4.10 Misissuance Error
#5I'm entirely unsurprised that this mistake involved an excel spreadsheet. Out of all the databases and IP management software they could be using which would have prevented this the first thing the employee reached for was excel. Almost every company I've worked for has employees using excel for data that would be better managed/stored/presented outside of an office document.
Re: ARIN Public Incident Report – 4.10 Misissuance Error
#6I like how frank the report is, no sugarcoating. "We relied on manual error prone verification and made a mistake. We have to automate the process." As ARIN block owner this situation is kinda scary but reading this actually makes me think it's less likely to happen again .
> We have to automate the process.
to be ominous?
Re: ARIN Public Incident Report – 4.10 Misissuance Error
#7I like how frank the report is, no sugarcoating. "We relied on manual error prone verification and made a mistake. We have to automate the process." As ARIN block owner this situation is kinda scary but reading this actually makes me think it's less likely to happen again .
Re: ARIN Public Incident Report – 4.10 Misissuance Error
#8I like how frank the report is, no sugarcoating. "We relied on manual error prone verification and made a mistake. We have to automate the process." As ARIN block owner this situation is kinda scary but reading this actually makes me think it's less likely to happen again .
Re: ARIN Public Incident Report – 4.10 Misissuance Error
#9I just completed a fairly major reorganisation of resources with RIPE, and I’ve interacted with them for two decades, and my experience is they remain as steady and consistent as ever.
Sure, you may not like a particular policy at some moment, or may not agree with the charging structure at some point in time when it’s not advantageous to you, but they do at least do what they say and say what they do.