CenturyLink/Qwest/Layer3 blocks Kiwi Farms

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
MoonState said:
I think in general it would be better if those who file complaints to say that they are unable to connect to AS397702 or 1776 Solutions LLC, if only to give that complaint a little more oomph, especially when talking to anything above call center retards.
Complaining that a single IP address or website is being blocked - as bad as that is - can be easily shrugged off. As already seen in this thread, customer support tried to explain that away by saying that the IP/site must be doing something shady and that's it's probably blocked for safety reasons yada yada.
An entire Autonomous System being cut from large parts of the Internet is a completely different story and should raise some eyebrows.
Click to expand...
That is what I did, only dropped AS397702 or 1776 Solutions LLC and ip range, when they really want a domain badattheinternet.com is better than KF because some people got hung up on when dropping KF.
 
As of a few minutes ago, I'm able to route to and hit the ip of kiwifarms through GTT from the US (Cox), however, I'm getting an SSL error where Firefox reports receiving a record that was too long. (SSL_ERROR_RX_RECORD_TOO_LONG)
 
I can understand why powerful people can still bend to the threat of being denigrated by trannies on Twitter, but I don't see how would they not counteract regular terrorist threats against their wives. I pray the blackholing is just a temporary appeasement of troons while the execs are leaving for Christmas before making a move against those eunuchs.
 
  • Agree
Reactions: not william stenchever and Hannibalistique
Ocumux said:
As of a few minutes ago, I'm able to route to and hit the ip of kiwifarms through GTT from the US (Cox), however, I'm getting an SSL error where Firefox reports receiving a record that was too long. (SSL_ERROR_RX_RECORD_TOO_LONG)
Click to expand...
That sounds like they're doing some fucky wucky trying to intercept your connection (SSL errors means encrypting/verifying the connection to the site is failing).

That's even worse...
 
  • Thunk-Provoking
  • Like
Reactions: Hubelublub and Absurdist Laughter
Screenshot_20221222_213313_Brave.jpg

Network shit like this is sorcery to me, but it should look like this, yes?

https://ping.pe/kiwifarms.net also shows COMPLETE. GLOBAL. SATURATION.
 
  • Informative
  • Like
Reactions: The Ghost of Kviv, Tealeaf, MoonState and 2 others
I have conectivity to the IP but firefox says this, Brave fails with a shorter Error descripton:

Secure Connection Failed

An error occurred during a connection to kiwifarms.net. SSL received a record that exceeded the maximum permissible length.

Error code: SSL_ERROR_RX_RECORD_TOO_LONG


IT WORKS OVER TOR THOUGH

This is so fucking weird, some hours ago I couldn't connect to the IP at all, now this.

Why does it work over TOR, what does TOR have to do with SSL?
 
JoshPlz said:
Just adding a screenshot from @Slav Power:
View attachment 4132590
Click to expand...

I wonder if the idiots causing this understand the true magnitude of All Out Autist War? This would be something of which the world has never seen before. I doubt anyone except a nation-state could contain it. I honestly have a hard time comprehending the scope of such a situation.

Also, for anyone attempting to contact their ISP/service provider, I wouldn't bother with front line support. Attempt to contact "Executive Customer Service" or "Business/Investor Relations". This is usually a dedicated team inside of large companies that are meant to resolve complaints promptly for "important" individuals. You don't actually have to be an important individual to use it, it's just that the "important" people tend to know about it. The people on these teams usually have enough pull to actually get real solutions, if not real answers if it is beyond even their power to solve directly. However, I have rarely seen these teams not find a way to solve problems before.
 
Whatever people are doing, it seems to be working. I can route in clearnet on Virgin now, but I get an SSL error. (SSL_ERROR_RX_RECORD_TOO_LONG)

1671741431776.png
 
  • Like
Reactions: MoonState
Also getting SSL errors in chrome:
ERR_SSL_PROTOCOL_ERROR

Managing to connect to the site through GTT, but nothing is loading with a hard refresh.
 
Meat Target said:
I have no direct proof of this, but could the minions of Taylor Lorenz and Ben Collins be involved? Both of them just got their shit pushed in by Musk.
Click to expand...
And, allegedly, one of them is technically savy or have access to PIs that are.

Edit:
In addition, I just tried to ping the network again, I'm getting a response. However, trying to access clearnet page could not be loaded error persists on Spectrum.
 
DrNow said:
For any phoneposters, ‘Secure VPN’ is free and you can connect from India. No Kiwi should be denied the right to sneed.
Click to expand...
TBH they have Anti VPN laws there since june 2022 by forcing VPN companies to keep logs even tho they do not care about troon complaints as well as ISPs there are not blocking any VPN . But i would seriously advice to use a VPN there then use a free oracle instance there and run a wireguard or openVPN server there.
 
ComStar said:
COMPLETE. GLOBAL. SATURATION.
Click to expand...
I see it too. This is actually a sight to behold because I have never seen it like this for Kiwi Farms. No signs of it working on CW yet. But hey, I can ping it and get responses!


Code: 
➜  ~ ping kiwifarms.net
PING kiwifarms.net (103.114.191.1) 56(84) bytes of data.
64 bytes from 103.114.191.1: icmp_seq=1 ttl=58 time=35.0 ms
64 bytes from 103.114.191.1: icmp_seq=2 ttl=58 time=37.4 ms
64 bytes from 103.114.191.1: icmp_seq=3 ttl=58 time=35.2 ms
64 bytes from 103.114.191.1: icmp_seq=4 ttl=58 time=83.3 ms
64 bytes from 103.114.191.1: icmp_seq=5 ttl=58 time=36.6 ms
64 bytes from 103.114.191.1: icmp_seq=6 ttl=58 time=37.6 ms
64 bytes from 103.114.191.1: icmp_seq=7 ttl=58 time=36.8 ms
64 bytes from 103.114.191.1: icmp_seq=8 ttl=58 time=37.5 ms
64 bytes from 103.114.191.1: icmp_seq=9 ttl=58 time=33.7 ms
64 bytes from 103.114.191.1: icmp_seq=10 ttl=58 time=35.5 ms
64 bytes from 103.114.191.1: icmp_seq=11 ttl=58 time=36.5 ms
 
  • Informative
Reactions: Absurdist Laughter and Meat Target
kiwifarms is returning packets now:

Code: 
 ping 103.114.191.1
PING 103.114.191.1 (103.114.191.1) 56(84) bytes of data.
64 bytes from 103.114.191.1: icmp_seq=1 ttl=58 time=33.4 ms
64 bytes from 103.114.191.1: icmp_seq=2 ttl=58 time=35.8 ms
^C
--- 103.114.191.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 33.358/34.563/35.769/1.205 ms


But it's also serving plain http on port 443, so who knows what's going on right now:
Code: 
$ curl -v http://kiwifarms.net:443
*   Trying 103.114.191.1:443...
* Connected to kiwifarms.net (103.114.191.1) port 443 (#0)
> GET / HTTP/1.1
> Host: kiwifarms.net:443
> User-Agent: curl/7.82.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 502 Bad Gateway
< content-length: 107
< cache-control: no-cache
< content-type: text/html
<
<html><body><h1>502 Bad Gateway</h1>
The server returned an invalid or incomplete response.
</body></html>
* Connection #0 to host kiwifarms.net left intact

Still, I am encouraged!
 
  • Optimistic
Reactions: Absurdist Laughter
I checked early this morning and it didn't work at all, it would just timeout. Now I just tried again and it's connecting on clearnet just fine.

I'm not sure what fuckery is involved but it seems odd and illegitimate. I keep getting the feeling that there's just like one person in these companies that has access to the backroom who's running interference for the trannies until everyone else notices they're sabotaging the company's operations for personal/political reasons.
 
  • Agree
  • Thunk-Provoking
Reactions: Xiphias, Lokenstien and unexpected onions
Rat Runner said:
kiwifarms is returning packets now:

Code: 
 ping 103.114.191.1
PING 103.114.191.1 (103.114.191.1) 56(84) bytes of data.
64 bytes from 103.114.191.1: icmp_seq=1 ttl=58 time=33.4 ms
64 bytes from 103.114.191.1: icmp_seq=2 ttl=58 time=35.8 ms
^C
--- 103.114.191.1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 33.358/34.563/35.769/1.205 ms


But it's also serving plain http on port 443, so who knows what's going on right now:
Code: 
$ curl -v http://kiwifarms.net:443
*   Trying 103.114.191.1:443...
* Connected to kiwifarms.net (103.114.191.1) port 443 (#0)
> GET / HTTP/1.1
> Host: kiwifarms.net:443
> User-Agent: curl/7.82.0
> Accept: */*
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 502 Bad Gateway
< content-length: 107
< cache-control: no-cache
< content-type: text/html
<
<html><body><h1>502 Bad Gateway</h1>
The server returned an invalid or incomplete response.
</body></html>
* Connection #0 to host kiwifarms.net left intact

Still, I am encouraged!
Click to expand...
It looks like it might be getting intercepted?

thebigjoel said:
I see it too. This is actually a sight to behold because I have never seen it like this for Kiwi Farms. No signs of it working on CW yet. But hey, I can ping it and get responses!


Code: 
➜  ~ ping kiwifarms.net
PING kiwifarms.net (103.114.191.1) 56(84) bytes of data.
64 bytes from 103.114.191.1: icmp_seq=1 ttl=58 time=35.0 ms
64 bytes from 103.114.191.1: icmp_seq=2 ttl=58 time=37.4 ms
64 bytes from 103.114.191.1: icmp_seq=3 ttl=58 time=35.2 ms
64 bytes from 103.114.191.1: icmp_seq=4 ttl=58 time=83.3 ms
64 bytes from 103.114.191.1: icmp_seq=5 ttl=58 time=36.6 ms
64 bytes from 103.114.191.1: icmp_seq=6 ttl=58 time=37.6 ms
64 bytes from 103.114.191.1: icmp_seq=7 ttl=58 time=36.8 ms
64 bytes from 103.114.191.1: icmp_seq=8 ttl=58 time=37.5 ms
64 bytes from 103.114.191.1: icmp_seq=9 ttl=58 time=33.7 ms
64 bytes from 103.114.191.1: icmp_seq=10 ttl=58 time=35.5 ms
64 bytes from 103.114.191.1: icmp_seq=11 ttl=58 time=36.5 ms
Click to expand...
If it is getting intercepted, what you're seeing is responses not from the actual kiwifarms site. Can you do a tracepath and see if it goes through terrahost?
 
Still can't connect over clearnet without TOR or a VPN, but traceroute is getting a lot farther than it was this morning.
 
You must log in or register to reply here.
Back