Someone from AWS/Amazon US Peering, get in touch please?
(Apologies to other list denizens) Hey there Amazon Peering, Dayjob (F-Root) have a pending peering session with you, and you’ve sent us a note into our ticket system: "[Order Reference: 9xzknz] Reminder:Pending peering request between Amazon and AS33080" (several times), from a noreply@ mail address. We try to set up the peering session (at telx atlanta) and get nothing back from you, not even a TCP Reset, but the peer (v4 and v6) is pingable. (Note: the sessions with your ./:251 routers are up okay, but both your ./:95 sessions are acting like this). Your note says to refer to https://peering.aws if we need to contact you, but on that page you list peering-amer@amazon.com, which we’ve mailed with no response. The peering portal you tell us to use at https://interconnect.amazon <https://interconnect.amazon/> (these corporate-vanity tld's are annoying, especially when you feel the need to use multiple), redirects me to peeringDB to log in, and then gives me: "Read timed out" (on a gray screen). Or: "custom:custom:networks: String attributes cannot have a length of more than 2048. “ We operate multiple ASes, and my peeringDB account also is tied to multiple orgs (including my own personal one), so that may be the cause of the errors? And I suspect whatever causes that error is also causing a filtering issue. Either way, Automation is cool and all, but in this case, I think just pointing peering@ at a human who could say “I see the problem, fixed!” would have caused less headache than this. Get in touch, Please and thanks! -Dan (noc at isc org, peering at isc org)
I’ve been getting these too.. I setup the session last night but still got a reminder email today. Wondering how long my inbox will be spammed… -Mike
On May 15, 2025, at 19:45, Dan Mahoney via NANOG <nanog@lists.nanog.org> wrote:
(Apologies to other list denizens)
Hey there Amazon Peering,
Dayjob (F-Root) have a pending peering session with you, and you’ve sent us a note into our ticket system: "[Order Reference: 9xzknz] Reminder:Pending peering request between Amazon and AS33080" (several times), from a noreply@ mail address.
We try to set up the peering session (at telx atlanta) and get nothing back from you, not even a TCP Reset, but the peer (v4 and v6) is pingable. (Note: the sessions with your ./:251 routers are up okay, but both your ./:95 sessions are acting like this).
Your note says to refer to https://peering.aws if we need to contact you, but on that page you list peering-amer@amazon.com, which we’ve mailed with no response.
The peering portal you tell us to use at https://interconnect.amazon <https://interconnect.amazon/> (these corporate-vanity tld's are annoying, especially when you feel the need to use multiple), redirects me to peeringDB to log in, and then gives me:
"Read timed out" (on a gray screen).
Or:
"custom:custom:networks: String attributes cannot have a length of more than 2048. “
We operate multiple ASes, and my peeringDB account also is tied to multiple orgs (including my own personal one), so that may be the cause of the errors? And I suspect whatever causes that error is also causing a filtering issue.
Either way, Automation is cool and all, but in this case, I think just pointing peering@ at a human who could say “I see the problem, fixed!” would have caused less headache than this.
Get in touch, Please and thanks!
-Dan (noc at isc org, peering at isc org) _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/VJODMDMT...
(I’m responding on-list since Mike and Dan mentioned issues) I’m in EC2 Networking now and can find the right people. If still having issues, mail me direct and I’ll get folks involved. John Excuse any typos - sent from mobile device
On May 15, 2025, at 7:52 PM, Mike Lyon via NANOG <nanog@lists.nanog.org> wrote:
I’ve been getting these too..
I setup the session last night but still got a reminder email today.
Wondering how long my inbox will be spammed…
-Mike
On May 15, 2025, at 19:45, Dan Mahoney via NANOG <nanog@lists.nanog.org> wrote:
(Apologies to other list denizens)
Hey there Amazon Peering,
Dayjob (F-Root) have a pending peering session with you, and you’ve sent us a note into our ticket system: "[Order Reference: 9xzknz] Reminder:Pending peering request between Amazon and AS33080" (several times), from a noreply@ mail address.
We try to set up the peering session (at telx atlanta) and get nothing back from you, not even a TCP Reset, but the peer (v4 and v6) is pingable. (Note: the sessions with your ./:251 routers are up okay, but both your ./:95 sessions are acting like this).
Your note says to refer to https://peering.aws if we need to contact you, but on that page you list peering-amer@amazon.com, which we’ve mailed with no response.
The peering portal you tell us to use at https://interconnect.amazon <https://interconnect.amazon/> (these corporate-vanity tld's are annoying, especially when you feel the need to use multiple), redirects me to peeringDB to log in, and then gives me:
"Read timed out" (on a gray screen).
Or:
"custom:custom:networks: String attributes cannot have a length of more than 2048. “
We operate multiple ASes, and my peeringDB account also is tied to multiple orgs (including my own personal one), so that may be the cause of the errors? And I suspect whatever causes that error is also causing a filtering issue.
Either way, Automation is cool and all, but in this case, I think just pointing peering@ at a human who could say “I see the problem, fixed!” would have caused less headache than this.
Get in touch, Please and thanks!
-Dan (noc at isc org, peering at isc org) _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/VJODMDMT...
NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/Q55DIF4P...
+ Tina for viz On Fri, May 16, 2025 at 8:44 PM John Kinsella via NANOG < nanog@lists.nanog.org> wrote:
(I’m responding on-list since Mike and Dan mentioned issues)
I’m in EC2 Networking now and can find the right people. If still having issues, mail me direct and I’ll get folks involved.
John
Excuse any typos - sent from mobile device
On May 15, 2025, at 7:52 PM, Mike Lyon via NANOG <nanog@lists.nanog.org> wrote:
I’ve been getting these too..
I setup the session last night but still got a reminder email today.
Wondering how long my inbox will be spammed…
-Mike
On May 15, 2025, at 19:45, Dan Mahoney via NANOG <nanog@lists.nanog.org> wrote:
(Apologies to other list denizens)
Hey there Amazon Peering,
Dayjob (F-Root) have a pending peering session with you, and you’ve sent us a note into our ticket system: "[Order Reference: 9xzknz] Reminder:Pending peering request between Amazon and AS33080" (several times), from a noreply@ mail address.
We try to set up the peering session (at telx atlanta) and get nothing back from you, not even a TCP Reset, but the peer (v4 and v6) is pingable. (Note: the sessions with your ./:251 routers are up okay, but both your ./:95 sessions are acting like this).
Your note says to refer to https://peering.aws if we need to contact you, but on that page you list peering-amer@amazon.com, which we’ve mailed with no response.
The peering portal you tell us to use at https://interconnect.amazon < https://interconnect.amazon/> (these corporate-vanity tld's are annoying, especially when you feel the need to use multiple), redirects me to peeringDB to log in, and then gives me:
"Read timed out" (on a gray screen).
Or:
"custom:custom:networks: String attributes cannot have a length of more than 2048. “
We operate multiple ASes, and my peeringDB account also is tied to multiple orgs (including my own personal one), so that may be the cause of the errors? And I suspect whatever causes that error is also causing a filtering issue.
Either way, Automation is cool and all, but in this case, I think just pointing peering@ at a human who could say “I see the problem, fixed!” would have caused less headache than this.
Get in touch, Please and thanks!
-Dan (noc at isc org, peering at isc org) _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/VJODMDMT... _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/Q55DIF4P... _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/URBRAW6U...
I’ve replied privately, thanks! -Dan
On May 16, 2025, at 17:49, Adam Blackington via NANOG <nanog@lists.nanog.org> wrote:
+ Tina for viz
On Fri, May 16, 2025 at 8:44 PM John Kinsella via NANOG < nanog@lists.nanog.org> wrote:
(I’m responding on-list since Mike and Dan mentioned issues)
I’m in EC2 Networking now and can find the right people. If still having issues, mail me direct and I’ll get folks involved.
John
Excuse any typos - sent from mobile device
On May 15, 2025, at 7:52 PM, Mike Lyon via NANOG <nanog@lists.nanog.org> wrote:
I’ve been getting these too..
I setup the session last night but still got a reminder email today.
Wondering how long my inbox will be spammed…
-Mike
On May 15, 2025, at 19:45, Dan Mahoney via NANOG <nanog@lists.nanog.org> wrote:
(Apologies to other list denizens)
Hey there Amazon Peering,
Dayjob (F-Root) have a pending peering session with you, and you’ve sent us a note into our ticket system: "[Order Reference: 9xzknz] Reminder:Pending peering request between Amazon and AS33080" (several times), from a noreply@ mail address.
We try to set up the peering session (at telx atlanta) and get nothing back from you, not even a TCP Reset, but the peer (v4 and v6) is pingable. (Note: the sessions with your ./:251 routers are up okay, but both your ./:95 sessions are acting like this).
Your note says to refer to https://peering.aws if we need to contact you, but on that page you list peering-amer@amazon.com, which we’ve mailed with no response.
The peering portal you tell us to use at https://interconnect.amazon < https://interconnect.amazon/> (these corporate-vanity tld's are annoying, especially when you feel the need to use multiple), redirects me to peeringDB to log in, and then gives me:
"Read timed out" (on a gray screen).
Or:
"custom:custom:networks: String attributes cannot have a length of more than 2048. “
We operate multiple ASes, and my peeringDB account also is tied to multiple orgs (including my own personal one), so that may be the cause of the errors? And I suspect whatever causes that error is also causing a filtering issue.
Either way, Automation is cool and all, but in this case, I think just pointing peering@ at a human who could say “I see the problem, fixed!” would have caused less headache than this.
Get in touch, Please and thanks!
-Dan (noc at isc org, peering at isc org) _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/VJODMDMT... _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/Q55DIF4P... _______________________________________________ NANOG mailing list
https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/URBRAW6U...
NANOG mailing list https://lists.nanog.org/archives/list/nanog@lists.nanog.org/message/TDOI5XDN...
participants (4)
-
Adam Blackington -
Dan Mahoney -
John Kinsella -
Mike Lyon