BLACKOUT! Numerous conspiracy sites offline in organized attack.

reply to post by Mr Tranny


Or worse, they might have inserted a deeply hidden communication program, which can send a useage log of a particular site or system every so many days or weeks, to keep track of things that others would wish they didnt have access to at all.

If the capabilities of this group are anything like as advanced as some have suggested, and as the hype would suggest, then its possible we could be seeing a new kind of system penetration, masked as a blunt force attack.

Originally posted by Jay Electronica
Maybe its someone affiliated with one of the major conspiracy sites that wasn't taken down?

Why go to those other conspiracy sites when _______________.com is bigger, better, and protected.

edit on 6-3-2013 by Jay Electronica because: (no reason given)

It’s bigger than conspiracy sites. Large groups of servers and entire networking centers are cutting connectivity.

The problem I have with getting to GLP is not the server it’s self getting overloaded. When I tracert GLP, the path ends at a gateway router. That means that SBC/ATT has severed connectivity with the network that host GLP. They did it to protect the SBC/ATT network from attack traffic coming from that network.

That means any site hosted on the same network as GLP will be unreachable by me. It will remain that way until they push the button to reconnect.

I could possibly get onto GLP by looking for a proxy on another network that hasn’t severed connectivity with the network supporting the GLP server if I wanted to.

reply to post by Mr Tranny


About every other post I have made today here gets lost. I use Tor and get a gateway lost message. We have AT&T as our provider.

reply to post by endats01


The first item on the list for the "internet traffic report" that shows 100% packet loss is Router: anhm7204.exo.com (67.215.65.132)

I just pinged 67.215.65.132
Ping 67.215.65.132
[hit-nxdomain.opendns.com]
Round trip time to 67.215.65.132: 1 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Average time over 10 pings: 0.1 ms

Pretty strange for something showing 100% packet loss wouldn't you think?

The 30 day graph on the site shows a single spike on the 1st of march and absolutely nothing unusual after that.
Their own packet loss for North America also shows a steady 0% average.

Hardly indicative of a major internet problem

reply to post by davespanners


This sounds odd even to me, and admittedly I am akin to a barbarian standing next to a wizard where this stuff is concerned.

If you've voiced support for Hugo Chavez be prepared to be gang raped in a dark place by fellow Americans wearing lizard suits. CIA loves a good gang rape. Get the creative juices flowing for the mayhem later. Just saying..

I noticed this last night also. No response at all for a while and then it started working again. But it was flaky for a while.

Originally posted by davespanners
reply to post by endats01

 

The first item on the list for the "internet traffic report" that shows 100% packet loss is Router: anhm7204.exo.com (67.215.65.132)

I just pinged 67.215.65.132
Ping 67.215.65.132
[hit-nxdomain.opendns.com]
Round trip time to 67.215.65.132: 1 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Round trip time to 67.215.65.132: 0 ms
Average time over 10 pings: 0.1 ms

Pretty strange for something showing 100% packet loss wouldn't you think?

I would say they have done one of a couple things.
Switched it’s ip address
Killed it’s ping response.
Taken it off the DNS list.
Or multiple of the above to try and shield it from direct attack.
Basically trying to obfuscate it’s real address to any potential attackers.

Or they could have just taken it off line killing connectivity until the storm dies down.

The 30 day graph on the site shows a single spike on the 1st of march and absolutely nothing unusual after that.
Their own packet loss for North America also shows a steady 0% average.

Hardly indicative of a major internet problem

I would say that they automatically exclude data from nodes that show %100 data loss. Otherwise their list of several currently non responding nodes would drive the average way off the graph.

And the paths they have selected does not cross all networks, and it does not take advantage of even a fraction of the possible routs. So it is useless in that regard unless it just happens to be at ground zero of the attack.

Just to clarify. Those ping results show that there is 0 packet loss from that IP not 100% as the internet traffic report claims .

Heres the ping from a different site just to make it clearer

--- PING 67.215.65.132 (67.215.65.132) 56(84) bytes of data. ---
64 bytes from 67.215.65.132: icmp_req=1 ttl=54 time=6.54 ms
64 bytes from 67.215.65.132: icmp_req=2 ttl=54 time=6.76 ms
64 bytes from 67.215.65.132: icmp_req=3 ttl=54 time=6.77 ms
64 bytes from 67.215.65.132: icmp_req=4 ttl=54 time=6.59 ms


--- 67.215.65.132 ping statistics ---
packets transmitted 4
received 4
packet loss 0 %
time 3003 ms

Originally posted by davespanners
Just to clarify. Those ping results show that there is 0 packet loss from that IP not 100% as the internet traffic report claims .

I know that. The thing is you are using a different DNS server. You are coming at it through a different rout.

It takes time for DNS changes to propagate. The DNS server they are using may not have taken the update yet after they switched the IP address of the node. That would cause the IP address they get from the DNS lookup to be invalid and not lead to anything. Your DNS server has updated, so you can get them.

They may have killed the ping response to packets coming from outside the network, and you are coming to it from inside the network.

Or they may have cut connectivity to the network that the web site’s server is operating from. That will cause it to not get a response. But the network you are on is connecting via a different part of the network, so you can get a response from the back side.

Just because one person on the internet can get a response, doe not mean you can.

And on that note.
I have an update on GLP.

They evidently moved servers. My DNS server has finally updated and I can get to them now. They are practically next door neighbors to me now. They have moved to a server that is on the ATT network.

They are only five network hops from me.

How you doing GLP, welcome to the neighborhood.

reply to post by Mr Tranny


They moved servers earlier today. I saw the threads on their message boards. However now they are down again and I am getting Error 504 Gateway Timeout again.

Originally posted by masta12d
reply to post by endats01

 

[snip]

For the slow one here
What makes you think insulting ATS staff and site users would have a positive effect in your message? More importantly, if you have such disdain for ATS then why are you here? If I didn't like the site I wouldn't come here, you clearly don't like the site....so what's your excuse?

And BTW **^$%&*%^

If it originated with a GLP member... Im not shocked. The first thing I thought of was OPPT... they are upset, panties wadded, and the type to do something like this if you read any of the oppt-ers rhetoric. In any case, ATS is awesome and I got a chuckle from the funny mental pic of Lucas pooping his pants.

reply to post by Krazysh0t


It is currently working for me. it’s loading at blazing fast speed for me right now.

Your network is evidently having a problem with connectivity to the ATT/SBC network.
What type of service provider do you have? DSL, cable, satellite, fiber, ISDN? That would give people a better idea where the problem is.

If you did a tracert to it, you could find where the break in the network is.

Your DNS server and your tracert program should be showing a destination ip ending in 75. If it is not, then it’s not updated.

reply to post by Mr Tranny


It works now, but for a good hour or two it was down.

reply to post by tothetenthpower


People that use LOIC or HOIC are stupid. They can be traced. You can't use a VPN or a proxy because you will attack that proxy IP address as well.

Is this an ongoing problem? I still haven't noticed anything different online.


I did not notice any police cars parked on my street today either. I have no idea why I saw so many yesterday. They kept taking off after I spotted them too which made it seem weird.

A IT friend claims that a DoS attack can be very good for a web site.

His claim is that the very heavy traffic during a DoS attack will raise the sites rating with google and other search engines.

And he has the proof as he set up a site then did a two week DoS attack on the site and ended up first on a google search for a site that few knew about and was way down on google ratings.

Since then i have been skeptical about sites that have regular DOS attacks for no apparent reason

Still slow here at my end

Funny you said police
I'm at a fly in mine 500 Km north off Timmins Ontario
Yesterday saw two different set of OPP around here weird are what

Even VONAGE has been down alot of times since today. Hope this problem doesn't get worse.

It's so obvious CIAL trolls who were hired to disrupt sites, have moved up to hacking/DDOSing and such!

Error 404--Not Found
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.4.5 404 Not Found

The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.

If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.

Originally posted by ANNED
His claim is that the very heavy traffic during a DoS attack will raise the sites rating with google and other search engines

In no possible way is that information correct.

Consider: if a site is "attacked" it's not accessible for real traffic.