sch-einesystem | Blog
| ||
|
|
|
|
|
|
 | |
| [0] |
20241226-1000-0-1.jpg |
 | |
| [1] |
20241226-1000-0-2.jpg |
 | |
| [2] |
20241226-1000-0-3.jpg |
| -------- Nachricht --------
Betreff: Re: [PEERINGDB-202412NVUQU1] RE: Re: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS21158 and one or more IXPs Datum: Thu, 26 Dec 2024 10:01:00 +0100 Von: webmaster@zentral-bank.eu <webmaster@zentral-bank.eu> An: PeeringDB Helpdesk System <support@peeringdb.com> Kopie (CC): chriztoffer <support@peeringdb.com>, noc@moedove.com, ruben@ifog.ch, LOCIX NOC <noc@locix.online>, maximilian.baehring@zentral-bank.eu, maximilian.baehring@googlemail.com P.S.: I laos habe an cuuertyl inactive peering at former Interxion (now Digital Reality) in Hanauer-Land- 30X Frankfurt a.M. based uponan old contract that i was promised taht i can take up whenever i want again that is also inactive in Ripe-DB but still (correctly) listed at PeeringDB dn a peerin gwith anotehr very huge Provider that operates globally. I am connected at several Peering-Points inside and outside the EU but within RIPE-Area. you can refer to Ripe-DB aut-num object And there are also emergency case offers that i have "in petto" that i am prepared to peer with but that are not listed there to avoid hackesr to see my "desater strategy". Max O.P.S: Throw "Moedove LLC" at arsits networks twards AS6969 out! -------- Weitergeleitete Nachricht -------- Betreff: Re: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS21158 and one or more IXPs Datum: Thu, 26 Dec 2024 09:45:30 +0100 Von: Maximilian Baehring <maximilian@baehring.at> An: support@peeringdb.com Hello! Please see my emails from December 06th, 2024 on regarding the issue. There was an incident with "AS44323 Moedove LLC" which made a transit form my network tzwarda "AS6939 he.net" withot my permission by ignorgingbgp large communities. Terofe the peerings are suspende for four weeks, I already have upddted the RIPE-DB aut-num Object accordingly. After this period I think I will copletely discontinue the LocIX peering but this will be decided then. I do not need LocIX werhe i Olny echnage a samll part of my traffic as I have enough other Upsterams. I dven exrimentally took up another perring for testing. So there is no hurry at all! I have fowfarded you the emails that show LocIX "Suspende" the port. I don't like this kind of unprofossional management by them becouse it was one of thyrcliens AS4434 Modeove tahtmade themisatke. I think that in januray i will possibly "leave LocIX". Max -------- Nachricht -------- Betreff: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS21158 and one or more IXPs Datum: Thu, 26 Dec 2024 04:02:49 +0000 Von: support@peeringdb.com An: maximilian@baehring.at This email details 1 new data mismatch[es] discovered by the PeeringDB IX-F Importer. Please review and correct these mismatches at your PeeringDB network page ( https://www.peeringdb.com/asn/21158 < https://www.peeringdb.com/asn/21158 >) or work with the indicated IXPs to correct the data. ----------------------------- Data supplied by your network Maximilian Baehring is in conflict with that provided by LOCIX FRANKFURT. Please work with LOCIX FRANKFURT to resolve this conflict or correct your data at https://www.peeringdb.com/asn/21158 < https://www.peeringdb.com/asn/21158 > as appropriate. Your network page will contain hints to assist with this. The PeeringDB Admin Committee may assist with this conflict if it is not resolved in a timely manner. REMOVE AS21158 - 185.1.167.5 - 2001:7f8:f2:e1:0:2:1158:1 The combination of ASN, IPv4 and IPv6 do not exist in the IX-F data under one member connection. | |