From: Zaven Karapetyan <zaven@fimetech.com>
To: gcc-help@gcc.gnu.org
Subject: Request for IP Troubleshooting
Date: Mon, 22 Apr 2024 15:26:16 +0400 [thread overview]
Message-ID: <BD71A9C8-3713-4AD4-8EC0-7B0BC8872D0D@fimetech.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 477 bytes --]
Dear GCC Support Team,
Fimetech is experiencing intermittent access issues with the gcc.gnu.org website from our IP 195.250.93.18, leading to significant disruptions in our workflow. We suspect potential blacklisting or rate limiting. We have checked with our internet provider, who found no issues on their end. Could you please verify if our IP is blacklisted or identify any other related concerns?
We appreciate your prompt assistance.
Best regards,
Fimetech Team
next reply other threads:[~2024-04-22 11:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 11:26 Zaven Karapetyan [this message]
2024-04-23 10:59 ` Florian Weimer
2024-04-23 11:09 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BD71A9C8-3713-4AD4-8EC0-7B0BC8872D0D@fimetech.com \
--to=zaven@fimetech.com \
--cc=gcc-help@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).