globaleaks.org and deb.globaleaks.org unreachable from multiple networks (No route to host) #4708
enriquegrx
started this conversation in
General
Replies: 5 comments 1 reply
|
Additional info: docs.globaleaks.org is reachable and resolves to readthedocs.io (Cloudflare), This suggests the issue is limited to GlobaLeaks own hosting / provider, |
0 replies
|
We are experiencing this as well in Asia. |
0 replies
|
Same thing in France. Following the ticket ! |
0 replies
0 replies
|
Hello! Thank you for your patience and for the love you’ve shown the project 💙 Tonight, we upgraded our firewall configuration to more powerful servers, which caused a temporary interruption to our infrastructure. Everything should now be fully operational. Please let us know if you notice any remaining issues. |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello,
we are experiencing connectivity failures to GlobaLeaks infrastructure that appear to be external to our deployment.
Both the main website and the Debian repository are currently unreachable from multiple, unrelated networks. As a consequence, internal GlobaLeaks jobs that depend on these endpoints fail and raise connection errors.
Error observed in GlobaLeaks:
**_
_**
Affected domains:
**Reproduction / Evidence:
From AWS EC2 (production environment):**
From University of Granada network (different ISP / ASN):
This behaviour is identical across networks, which suggests a server-side outage or upstream routing/BGP issue, rather than a local firewall or configuration problem. Other HTTPS destinations are reachable from the same hosts. IPv6 is unavailable from our networks, but IPv4 also fails
Can you confirm whether there is an ongoing outage, a routing / provider issue, or any planned changes affecting these endpoints?
Thanks in advance.
All reactions