sch-einesystem | Blog
| ||
|
|
|
|
|
|
 | |
| [0] |
20241206-0845-0-1.jpg |
 | |
| [1] |
20241206-0845-0-2.jpg |
 | |
| [2] |
20241206-0845-0-3.jpg |
 | |
| [3] |
20241206-0845-0-4.jpg |
| -------- Nachricht --------
Betreff: Re: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS21158 and one or more IXPs Datum: Fri, 6 Dec 2024 08:46:04 +0100 Von: Maximilian Baehring <maximilian@baehring.at> An: support@peeringdb.com Hello waht is this PeeringDB IX-F importer? the data in the DataBase is 100% accurate, https://www.peeringdb.com/ix/2084 lists the locix perring you mention and that is exatcly the same data I gave you from my side. Maximilian Baehring 21158 1G Selective 185.1.167.5 2001:7f8:f2:e1:0:2:1158:1 -------- Nachricht -------- Betreff: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS21158 and one or more IXPs Datum: Fri, 6 Dec 2024 03:57:47 +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. ----------------------------- | |