26.03.2026 05:00
Ich wurde gestern schon wieder den ganzen tag von total unfähgen Kollegen verarscht. Da ging es um eine ABM für gefeuerte Ex-Mitarbeiter /Sbaoteure der roten Armee. Ich hab ja bereits gesagt daß "peanuts - die Bank zahlt alles" Immo Schneider [Congstar Kronberg/Ts.] versuchte zusammen mit Bader Computer/CDC und GhostNET, dem Betreiber von KleyRex mich dazu zu erpssne mit AS15844 TGC in Oberursel/Ts. zu peeren, dem Verbrecher Thomas Giger "wird sind sobald CERFnet/GATEL gekappt ist dann die 'true gloab acess communication' anch darußen" und Hans-Werner Schilling, Lars Weber und seinen Komplizen die verantwortlich sind für meinen angeblichen Firmen-wage Autounfall 2003 und das gekidnappate Kind mit dem sich der gefeurte Verebcher Hans Werner Schilling sine Job zurückerpssen wollte sow wie sich Sekretärein Brigitta Schössler sich einen Job zu erpressen versucht hatte udn einen einstieg in meine Firma per DDOS/Spam /Viren und Hacker Attacken seitens der Gewerkschaft. Das ist banden udn gewerbsmäßig orgaiserte Kiminalität mit Millionenschäden unterstützt von "RAF Terroristen" also den Luet die versuchten Onlinebanking abzuhören. Jedenfalls ist es so daß "Immo Schneider" bei "myloc" investierte um die Metallgesellschaft AG so zu erpressen ihm Immbilienmaklerfaträge zu geben. Genau wie Rakita. Das BIGfax Debakel. Wo sie bei AS6939 he.net damals Geflüchtete unterbringen wollten aus dem Informatik Oberstufen Kurs der Humboldschule, Doppelagenten!
-------- Nachricht --------
Betreff: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS2***8 and one or more IXPs
Datum: Wed, 25 Mar 2026 06:36:21 +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/2***8 < https://www.peeringdb.com/asn/2***8> ) or work with the indicated IXPs to correct the data.
-----------------------------
Data supplied by your network Maximilian Baehring is in conflict with that provided by KleyReX. Please work with KleyReX to resolve this conflict or correct your data at https://www.peeringdb.com/asn/2***8 <https://www.peeringdb.com/asn/2***8> 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.
MODIFY AS2***8 - 1***2 - 2***1
- ix_side: None to 290
-----------------------------
-------- Nachricht --------
Betreff: Re: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS2***8 and one or more IXPs
Datum: Wed, 25 Mar 2026 14:10:20 +0100
Von: Maximilian Baehring <maximilian@baehring.at>
An: support@peeringdb.com
Kopie (CC): support@h***t, info@i***h
Hello
https://bgp.he.net/AS2***8#_irr
import: from AS6***9 action pref=100; accept AS-HURRICANE
export: to AS6***9 announce AS2***8
mp-import: afi ipv6 from AS6***9 accept ANY
mp-export: afi ipv6 to AS6***9 announce AS2***8
both sides of the records match and the peering is (according to
AS39389 looking gass lg.he.net Probe Digtalreliyt) up and running
and i have no info aof the KleyRex Reseller AS34927 IFOG taht ther
are any issues.
https://www.peeringdb.com/net/7***5
https://www.peeringdb.com/ix/1**3
first of all PEeeringDB ist not an official ITI/ICAN/Routing Registry like RIPE (or its backup RADB.net) so it is of less interest for the
functionality of the peerings what is written down there.
i know that AS6***9 h***t H***E has issues ("illegal" annoucmnets appearing at NEW YORK) becasue they try to prefer L***X Peerings over K**x and AS2***8 left L***X already months ago. But this is a local DeCIX New York problem not mine/ours.
Max
Am 25.03.2026 um 07:36 schrieb support@peeringdb.com:
[...]
-------- Nachricht --------
Betreff: [HE#7002949] Re: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS2***8 and one or more IXPs
Datum: Wed, 25 Mar 2026 11:15:25 -0700
Von: Ian Subasa <peering@***>
Antwort an: peering@***
An: Maximilian Baehring <maximilian@baehring.at>
Kopie (CC): support@peeringdb.com, info@i***h
Hi Maximilian,
I don't think this is related to HE/AS6***9 at all.
It looks like you're responding to an email from PeeringDB. It looks like they are receiving a JSON feed from *** that indicates what networks are assigned which IPs and they see a mismatch between that data and what's listed on your PeeringDB page for AS2***8.
This would not be data from or related to HE/AS6***9. For what it's worth the Participants page on the *** website appears to match the IP you have listed on PeeringDB: https://***/en/participants/.
I think we can be dropped from further discussion as it does not appear we should be involved.
Thank you,
Ian Subasa
Sr. Network Engineer
*** AS6***9
Provisioning Department
***
-------- Nachricht --------
Betreff: Re: [HE#7002949] / [PEERINGDB-202603MXRYV1] IFO / ticket #4893554 -9be8- / Re: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS2***8 and one or more IXPs
Datum: Wed, 25 Mar 2026 20:51:40 +0100
Von: Maximilian Baehring <maximilian@baehring.at>
An: peering@***
Kopie (CC): support@peeringdb.com
Hello
Ian Subasa! Im am listed on https://k****t/en/participants/ but I do not use the Route Servers since they started to mandatory implement RPKI which I do not wnat to us! AS6***9 h***t and I have a perring on the K***x Infrastrcutre using a direct BGP session without using any
of the route servers. in the meber list i have selected that i am in general "OPEN" to any new peering request like this, without using a
session to the rouet srevers to void rpki. be carefull, the website https://k***/en/participants/ list is outated, it prodces wrong links. http://www.ripe.net/perl/whois?searchtext=-r+-T+aut-num+AS6***9
which is sicte rie chengs ist websit no longer Calid, it shold instead read https://apps.db.ripe.net/db-web-ui/lookup?source=RIPE&type=aut-num&key=AS2***8 see tatchedscreenhots.
i only doe keep this eering open for a lawsuit against several compuetr companies in my birth and former hometown Bad homburg, where the
company GHOSTNET, founder of Kylerex ( i nkwon lasr weber very well) resided. Alos the company Bader Computer who helped labour unionist "hans werner shcillng" a former school/classmate eplyoe of me and one of te programmes off peeringbd to kidnap my children after bomb-balsting the bank limousine I was driving in. They tried to get jobs at european central bank, it's becaus my mother was wiking for baking securty employers organisiation and te tred to coerce meo to sell thyer network/sowfater shit lika fax servers to the banks. i try to reproduce the stup tehy oused to attack my network in 2003 for a lawsuit i am in.
i will write you a second email about this!
Max
-------- Nachricht --------
Betreff: [PEERINGDB-202603OS6FG1] RE: Re: PeeringDB: Action May Be Needed: IX-F Importer data mismatch between AS2***8 and one or more IXPs
Datum: Wed, 25 Mar 2026 20:20:25 +0000 (UTC)
Von: chriztoffer <support@peeringdb.com>
Antwort an: chriztoffer <support@peeringdb.com>
An: Maximilian Baehring <maximilian@baehring.at>
Kopie (CC): support <support@***>, Ruben Garbade <info@i***h>
?
Dear Maximilian Baehring (maximilian@baehring.at),
Some users received an email last night about an IX-F importer data mismatch. This was due to a recent importer update; no action is required. The review workflow may not reflect these changes yet. We’re improving this and apologize for the confusion.
https://www.facebook.com/peeringdb/posts/*** < https://www.facebook.com/peeringdb/posts/*** >
--
chriztoffer | PeeringDB Administrator | Admin Committee
PeeringDB | www.peeringdb.com <https://www.peeringdb.com/> | support [at] peeringdb [dot] com
o Join one of the PeeringDB mailing lists! | https://lists.peeringdb.com
o Want a feature or run into a bug? Tell us at PeeringDB Github | https://github.com/peeringdb/peeringdb/issues/new
o PeeringDB Administrators are unpaid volunteers. ? response times cannot always be guaranteed.
o PeeringDB specific terms. ? https://docs.peeringdb.com/glossary/
PeeringDB < https://www.peeringdb.com > ·
(#IBXATCG2Y9Y4N736SQT) ?
[0] "202603260500-0-1.jpg"
[1] "202603260500-0-2.jpg"
[2] "202603260500-0-3.jpg"
[3] "202603260500-0-4.jpg"
[4] "202603260500-0-5.jpg"
[5] "202603260500-0-6.jpg"
[6] "202603260500-0-7.jpg"
[7] "202603260500-0-8.jpg"
[8] "202603260500-0-9.jpg"
