2 Answers
- Newest
- Most votes
- Most comments
0
-
Could you share any
curl
outputs with an error?curl -v http://app.montyagentes.com/MasterAgent.v.6.7.5.jnlp
hping3 -S -c 10 --fast -p <port-number> <NLB-IP>
mtr -rbzne -c10 <NLB-IP> -T -P <port-number>
-
Also share the output of
curl https://checkmyip.cloudfront.net
to see the client-ip that is having issue connecting to S3, NLB ? -
In the past weeks I did see degradation in availability from AWS Spain Region to DIGI availability. As of now I don't see any, I checked one of the IP from
194.55.169.0/24
AS | IP | BGP Prefix | CC | Registry | Allocated | AS Name
57269 | 194.55.169.0 | 194.55.169.0/24 | RO | ripencc | 2003-12-09 | DIGISPAINTELECOM, ES
Start: 2023-12-11T11:01:00+0000
HOST: 18-100-135-187 Loss% Snt Last Avg Best Wrst StDev
1. AS??? 244.5.0.1 0.0% 10 8.6 5.7 0.9 8.6 2.7
2. AS??? 240.1.120.6 0.0% 10 0.2 0.2 0.2 0.2 0.0
3. AS??? 242.3.227.135 0.0% 10 0.5 1.5 0.2 10.4 3.1
4. AS??? 240.1.176.12 0.0% 10 10.3 10.4 10.2 11.0 0.2
5. AS??? 242.4.92.5 0.0% 10 11.2 12.1 10.2 20.5 3.2
6. AS??? 99.83.119.248 0.0% 10 10.3 10.3 10.3 10.4 0.0
7. AS??? 99.83.119.249 0.0% 10 10.4 10.4 10.3 10.6 0.1
8. AS8708 86.120.71.51 0.0% 10 10.4 12.3 10.3 28.7 5.8
9. AS57269 194.55.169.1 0.0% 10 9.3 9.1 8.3 9.5 0.5
Best if you open a case with Premium Support.
answered 5 months ago
0
It was a routing problem from AWS and it was solved on last Saturday afternoon so everything is working fine now. The issue had effects in other platforms we manage on AWS and all of them are working right now.
Thanks for your help @bijay_k.
answered 5 months ago
Relevant content
- asked a year ago
- asked 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago