29.05.2026 06:00
-------- Nachricht --------
Betreff: RE: (#FOT-405725) "bgp.he.net" detected route with as-path "^21158 8849 ..." altoght i only have a peering between "21158" and "56630" and not with "8849"
Datum: Thu, 28 May 2026 11:12:05 +0000
Von: Support <support-eu@melbicom.net>
Kopie (CC): peering@he.net, maximilian.baehring@googlemail.com

Ticket Details

*Ticket #:* FOT-405725
*Subject:* "bgp.he.net" detected route with as-path "^21158 8849 ..." altoght i only have a peering between "21158" and "56630" and not with "8849"
*Department:* Support
*Status:* Replied
*Priority:* Critical

*Maximilian Baehring*
User - 2026.05.26 22:33

Hello

the site https://bgp.he.net/AS21158#_peers <***> says that you redistribute my bgp announcment from AS21158 to AS56630 to AS6939 with an as path shortened to ^21158 AS8849" instead - like it should be - "^21158 56630 8849 ..." there is no peering form AS21158 with AS8849, look at

# whois -h whois.ripe.net -T aut-num AS21158 | grep "^\(im\|ex\)port:"
import: from AS29670 action pref=100; accept ANY
export: to AS29670 announce AS21158
import: from AS34568 action pref=100; accept ANY
export: to AS34568 announce AS21158
import: from AS34872 action pref=100; accept AS-SERVPERSO
export: to AS34872 announce AS21158
import: from AS34927 action pref=100; accept ANY
export: to AS34927 announce AS21158
import: from AS56630 action pref=100; accept ANY
export: to AS56630 announce AS21158
import: from AS6939 action pref=100; accept AS-HURRICANE
export: to AS6939 announce AS21158

(or https://apps.db.ripe.net/db-web-ui/lookup?source=ripe&key=AS21158&type=aut-num <***> )

i have my filters open for AS56630 but not for AS8849.

Max

--------------
IP Address: 193.109.132.25
Attachments
20260526-AS56630-AS8849.jpg < *** > (132.0 KB)

===
[...]
===


*Agent 44*
Staff - 2026.05.27 00:25

Hello,

We have forwarded your request to our network department. We will update you as soon as we receive a response. Thank you for your patience.

*Maximilian Baehring*
User - 2026.05.27 19:11

===
[...]
===

Hello

I emailed AS6939 and they said the info comes from the routeviews route table. none of the routeviews AS3582 University of Oregon Route Servers that I reached gave me a route with as-path "_8849_21158$" so I think the problem is somewer within AS6939 he.net


telnet://route-views.routeviews.org
telnet://route-views3.routeviews.org
telnet://route-views4.routeviews.org
telnet://route-views6.routeviews.org

===
[...]
===

*Agent 54*
Staff - 2026.05.28 10:36

Thank you for your patience.

AS8849 serves as our secondary Autonomous System (AS). Clients connected to AS8849 will observe your announcements through this AS rather than AS56630, which is the expected behavior.

It appears that one of the clients is likely connected to the AS6939 route collector servers, utilized for their looking glass service. This explains why the route is displayed in this manner in the looking glass.

Please be assured that this situation does not impact global routing.

===
[...]
===

*Maximilian Baehring*
User - 2026.05.28 14:11

I do not think that what you do is allowed by RIPE. i am sure shortening as-paths like this is only allowed witin ibgp https://www.rfc-editor.org/info/rfc6996/ <**> if you are not redistrubuting paths via an AS boundary to the global routing table but in that case you seem
to do so (AS6939 said a "_8849_21158$" AS Path this was visible to the global routing-table).

yor are disturbing an inetrpol and miltray police terrorism investigation (the #NAWALNY case and its german oil inustry counterpart) kidapped children of whitnesse of a acr bomb explosison - see http://neues.forum <**> (or http://zentral-bank/tumblr.com/ <***> )




[0] "202605290600-0-1.jpg"


[1] "202605290600-0-2.jpg"


[2] "202605290600-0-3.jpg"


[3] "202605290600-0-4.jpg"


[4] "202605290600-0-5.jpg"


[5] "202605290600-0-6.jpg"


[6] "202605290600-0-7.jpg"