It does not look specific to A&A. One of the network paths confirmed to be affected did not go through A&A.
It's confirmed which exchange the issue lies at. But it's unclear to me if the issue is with the destination network or the exchange itself. I do not have a presence at that exchange myself, so the only information I have to work from is output from traceroute and similar tools.
It looks to me like one aspect of the BGP implementation you are using is a contributing factor. But that may very well be standard behavior. For all I know it could be that all other BGP implementations would respond the same in this corner case.
kasperd /
npub1jh…xut5y
2024-08-25 12:46:40
in reply to nevent1q…ue7f
Author Public Key
npub1jhpgfu25y30c3h9xrrlxhrhge7669h3xwphjs99nau4k66ctsnyqjxut5yPublished at
2024-08-25 12:46:40Event JSON
{
"id": "2b347a570ebfa0561e46d6ccf39d25e074d03907ec6cb2ae39d8772cdeecdb06",
"pubkey": "95c284f154245f88dca618fe6b8ee8cfb5a2de26706f2814b3ef2b6d6b0b84c8",
"created_at": 1724590000,
"kind": 1,
"tags": [
[
"p",
"831f088c53bea5a2faa06f0123cc9c1d30b816c1c4b1dbf0100a2cff8f612bb6"
],
[
"p",
"712913b00ac899746988cf9496deb3992caff8f7cc36a78527aaf319ab4f24d0"
],
[
"p",
"da50c965cdff34b1c8bd03920adf447dd35fadbeb8c1b63b53da77e5284e43dc"
],
[
"p",
"95c284f154245f88dca618fe6b8ee8cfb5a2de26706f2814b3ef2b6d6b0b84c8"
],
[
"e",
"5e59309ba51a96042481ec7101fa2b0424d94f31d06cdcd918d9cb596212eb07",
"",
"reply",
"831f088c53bea5a2faa06f0123cc9c1d30b816c1c4b1dbf0100a2cff8f612bb6"
],
[
"e",
"fb89bd49960662422b8344475955a739973aae46574cd09ab776cde7840a7ede",
"",
"root",
"da50c965cdff34b1c8bd03920adf447dd35fadbeb8c1b63b53da77e5284e43dc"
],
[
"proxy",
"https://westergaard.social/objects/584f4836-bd56-4085-a1c0-a8ed5944535a",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://westergaard.social/objects/584f4836-bd56-4085-a1c0-a8ed5944535a",
"pink.momostr"
],
[
"-"
]
],
"content": "It does not look specific to A\u0026A. One of the network paths confirmed to be affected did not go through A\u0026A.\n\nIt's confirmed which exchange the issue lies at. But it's unclear to me if the issue is with the destination network or the exchange itself. I do not have a presence at that exchange myself, so the only information I have to work from is output from traceroute and similar tools.\n\nIt looks to me like one aspect of the BGP implementation you are using is a contributing factor. But that may very well be standard behavior. For all I know it could be that all other BGP implementations would respond the same in this corner case.",
"sig": "b4c56c8e220050cc99b5e4a1ccf9f6203bfa7ff570319d68f1dc46e5d67e48122a35ac3d5234b1a71168b08961e7309a8c850206aafacc0f53c500398cfac156"
}