[members-discuss] Our AS is in a macro that we don't authorize.
- Previous message (by thread): [members-discuss] Our AS is in a macro that we don't authorize.
- Next message (by thread): [members-discuss] Our AS is in a macro that we don't authorize.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cedric R
ml at servperso.com
Thu Nov 1 12:49:34 CET 2018
Le 30-10-18 à 15:27, José Manuel Giner a écrit : > Hi, we checked that our AS is present in the macro: AS24748:AS-THINX > (they have thousands of AS in their macro) > > After contacting atman.pl who is responsible for this macro, they tell > me: > > > It appears that AS59432 is contained in one of our customers AS-SETs > and > > it is automatically added to our AS-SET AS24748:AS-THINX > > > > As soon as they remove AS59432, it will disappear from AS24748:AS-THINX > > We have asked him how we can find out who that customer is. But their > answer doesn't give us any information. > > > Please be kindly informed that our macros are being built automatically > > according to our customers` macros. If your AS happens to be removed > > from whichever of our customer`s macros, ours is to be changed > accordingly. > > We are concerned about this situation and do not know how to proceed. > > Thank you for your help! > Hello, If someone put you in theyr as-macro, it's maybe because they give you transit. Maybe the first search step is search all your transit as who are in this list and check theyr as-macro (get them over peering-db) Just an idea, but maybe it can help Cedric Rossius
- Previous message (by thread): [members-discuss] Our AS is in a macro that we don't authorize.
- Next message (by thread): [members-discuss] Our AS is in a macro that we don't authorize.
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]