Also down here from Houston AT&T ➜ ~ curl -v https://bgp.he.net/ * Trying 72.52.94.234:443... * TCP_NODELAY set * Connected to bgp.he.net (72.52.94.234) port 443 (#0) * ALPN, offering h2 * ALPN, offering http/1.1 * successfully set certificate verify locations: * CAfile: /etc/ssl/certs/ca-certificates.crt CApath: /etc/ssl/certs * TLSv1.3 (OUT), TLS handshake, Client hello (1): * TLSv1.3 (IN), TLS handshake, Server hello (2): * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): * TLSv1.3 (IN), TLS handshake, Certificate (11): * TLSv1.3 (IN), TLS handshake, CERT verify (15): * TLSv1.3 (IN), TLS handshake, Finished (20): * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): * TLSv1.3 (OUT), TLS handshake, Finished (20): * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 * ALPN, server accepted to use http/1.1 * Server certificate: * subject: CN=bgp.he.net * start date: Dec 13 11:50:10 2023 GMT * expire date: Mar 12 11:50:09 2024 GMT * subjectAltName: host "bgp.he.net" matched cert's "bgp.he.net" * issuer: C=US; O=Let's Encrypt; CN=R3 * SSL certificate verify ok.
GET / HTTP/1.1 Host: bgp.he.net User-Agent: curl/7.68.0 Accept: */*
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): * old SSL session ID is stale, removing * Mark bundle as not supporting multiuse < HTTP/1.1 403 Forbidden < Date: Tue, 16 Jan 2024 14:47:24 GMT < Server: Apache/2.4.41 (Ubuntu) < Content-Length: 276 < Content-Type: text/html; charset=iso-8859-1 < <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>403 Forbidden</title> </head><body> <h1>Forbidden</h1> <p>You don't have permission to access this resource.</p> <hr> <address>Apache/2.4.41 (Ubuntu) Server at bgp.he.net Port 443</address> </body></html> * Connection #0 to host bgp.he.net left intact On Tue, Jan 16, 2024 at 8:47 AM Jay Urish via Outages <outages@outages.org> wrote:
Check for a popup or script blocker.. I got the same think till I allowed the domain in my NoScript plugin
On 1/16/24 08:44, Mel Beckman via Outages wrote:
It works for me:
Welcome to the Hurricane Electric BGP Toolkit.
You are visiting from 47.157. <https://bgp.he.net/ip/47.157.190.78>xxx.xxx
[image: United States]
Announced as 47.157.0.0/16 <https://bgp.he.net/net/47.157.0.0/16> (Frontier Communications Corporation) [image: United States] Announced as 47.144.0.0/12 <https://bgp.he.net/net/47.144.0.0/12> (American Registry for Internet Numbers) [image: United States]
Your ISP is AS5650 <https://bgp.he.net/AS5650> (Frontier Communications of America, Inc.)
-mel beckman
On Jan 16, 2024, at 5:19 AM, Hank Nussbacher via Outages <outages@outages.org> <outages@outages.org> wrote:
Anyone know why bgp.he.net is down?
I get:
We're sorry, but something went wrong. We've been notified about this issue and we'll take a look at it shortly.
Thank,
Hank
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing listOutages@outages.orghttps://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
