Whats up with CCBILL?
 

Why is it crawling so fucking slow...?


Argh

i can't even load reports :(

Oh no here we go again

this has been a fucked up week with ccbill......and after 4 days I am still i getting timeouts on joinpages and the webadmin.

:Oh crap

sad :Oh crap

At least they're running slow for you. They're flat out down for me again. Going on almost an entire week of problems.....

You know, Cisco DOES sell solutions to help you deal with DDOS attacks. They're not cheap, but they're cheaper than an entire marketplace loosing sales for a week:

http://www.cisco.com/en/US/products/...d800fa55e.html

slow for anyone else?

same BAT-time, same BAT-chanel

Very slow here as well.

The entire net is slow for me today.

been a bad week for ccbill with these attacks. Hopefully the get it stopped soon.

the week is a total loss for me, after feeds and hosting costs for existing members and stuff, not having the new sales go through will practically make it a non profit week. i hope ccbill gets their shit together soon. this is horrible

does it feel good to get assfucked, when you're straight?
 

<rant>

Dear CCBill,

Communicate with us and you'll receive less SCREAMING phone calls from your TOP clients! :1orglaugh

Why is it ALWAYS the same shtick;

"what problem are you having" ....

"we're performing maintenance tonight.."

"can you send us a traceroute?"

"HAHA OKAY HERE YA GO -->

traceroute -I bill.ccbill.com
traceroute to bill.ccbill.com (64.38.240.80), 30 hops max, 38 byte packets
1 10.0.0.1 (10.0.0.1) 0.294 ms 0.211 ms 0.213 ms
2 66.236.98.161 (66.236.98.161) 0.869 ms 0.805 ms 0.859 ms
3 65.107.52.125.ptr.us.xo.net (65.107.52.125) 37.820 ms 24.088 ms 24.331 ms
4 ge5-0-0.MAR1.Phoenix-AZ.us.xo.net (207.88.81.49) 349.037 ms 355.427 ms 349.604 ms
5 p5-1-0-1.RAR1.LA-CA.us.xo.net (65.106.5.21) 367.699 ms 366.307 ms 356.240 ms
6 p0-0.IR1.LA3-CA.us.xo.net (65.106.5.46) 365.480 ms 365.436 ms 355.747 ms
7 bpr2-so-6-1-0.LosAngeles.savvis.net (208.173.55.201) 381.544 ms 354.990 ms 365.334 ms
8 dcr1-ae3.LosAngeles.savvis.net (208.172.44.9) 357.407 ms 376.509 ms dcr2-ae3.LosAngeles.savvis.net (208.172.44.133) 365.988 ms
9 acr1-so-0-0-0.Phoenix3px.savvis.net (204.70.193.89) 382.050 ms dcr2-so-5-0-0.LosAngeles.savvis.net (204.70.192.118) 365.548 ms acr1-so-0-0-0.Phoenix3px.savvis.net (204.70.193.89) 381.276 ms
10 208.172.236.74 (208.172.236.74) 371.084 ms acr1-so-0-0-0.Phoenix3px.savvis.net (204.70.193.89) 365.267 ms 208.172.236.74 (208.172.236.74) 371.977 ms
11 * 208.172.236.74 (208.172.236.74) 378.427 ms *
12 * * *

Gee that explains the maintenance 100%. During your DDOS attacks, your hosting company CWIE decided to make routing changes and take us off our "PREMIUM LEVEL 3 bandwidth", & setup peering through a cheap POS line like SAVVIS....

WTG CCBILL :thumbsup , thanks for fewer sales!

Thank G-D for EPOCH!

</rant>

It's been down all day for us also...How much really do you need to turn over per month to get your own merchant account set up. Non US merchant account that is. Who's reliable, well known and can get us set up with one?

Also ..What's the best cascading system out there ..one that's easy to install.

CCBill/CWIE say everything is just fine....its our XO T-1 that is the problem. Wow, our T-1 cost of 40% fewer sales? Guess it's time to find a new T-1 provider.... :-\

Oh NO wait, wait,I got it, we can go back to a Qwest circuit, and have CWIE as our ISP again, that way our CCBill join forms will ALWAYS pull up!!!

g-damn it feels good to de-virginize my ass.

Thanks again CWIE/CCBill :-D

IM going with Paycom

thank you ccbill, bravo crew, you guys are amazing. you should listen to your LARGER clients more often, instead of nearly giving us heart attacks and taking years off our lives from the heartache! :disgust

traceroute bill.ccbill.com
traceroute to bill.ccbill.com (64.38.240.80), 30 hops max, 38 byte packets
1 10.0.0.1 (10.0.0.1) 0.255 ms 0.191 ms 0.229 ms
2 66.236.98.161 (66.236.98.161) 0.857 ms 0.941 ms 0.747 ms
3 65.107.52.125.ptr.us.xo.net (65.107.52.125) 7.337 ms 7.080 ms 8.329 ms
4 ge5-0-0.MAR1.Phoenix-AZ.us.xo.net (207.88.81.49) 5.487 ms 5.690 ms 5.734 ms
5 p5-1-0-1.RAR1.LA-CA.us.xo.net (65.106.5.21) 16.099 ms 15.912 ms 15.854 ms
6 p0-0.IR1.LA3-CA.us.xo.net (65.106.5.46) 15.848 ms 15.814 ms 15.852 ms
7 so-4-0-3.gar2.LosAngeles1.Level3.net (209.0.227.33) 16.598 ms 16.468 ms 16.976 ms
8 so-0-1-0.bbr1.LosAngeles1.Level3.net (4.68.96.81) 16.600 ms 17.081 ms 16.834 ms
9 as-1-0.mp1.Phoenix1.Level3.net (64.159.1.121) 25.957 ms 25.841 ms as-0-0.mp2.Phoenix1.Level3.net (4.68.128.150) 25.842 ms
10 ge-1-1-51.car1.Phoenix1.Level3.net (4.68.98.2) 25.835 ms ge-1-2-52.car1.Phoenix1.Level3.net (4.68.98.34) 26.197 ms 25.853 ms
11 g2-4.cr1.phx1.cwie.net (4.79.166.2) 25.838 ms 25.851 ms 25.968 ms

I sent them a solution last week that would have got them back up within 3 hours... seems CCBILL did not want to invest the money to keep there clients happy, very strange...

not a geek, but i'd be thinking about internap if i was ccbill.

Almost 4pm Pacific
 

And still very slow here. Join pages are still timing out

Ratio's just keep falling for me :(

How can they not have fixed this mess yet? I can understand if Mensniche is down for a week but CCBill...

Hey Guys,
Let's try to be a bit more constructive here.

In order to solve the problem, CCbill / Cavecreek needs lots of feedback.
I'm saying this from direct experience in the last days.
Any info you can give them, or post here, is welcomed.

When the signup page is failing, you should send them:
- Your location
- A Traceroute
- Time of failure
- Any other possible useful info

This is the only way that this issue is going to be solved.
If you just post: "Signup pages don't come up", that's pointless.
Signup pages are coming up in Chicago, but not somewhere else.
If they don't know where, they cannot look into the issue.

We're all in the same ship. Any help we can give them, will help resolve the problem.
For example, signups in the last 4 hours have been between fantastic, and very good.
Is it the same for you guys? If not, maybe your traffic is coming from somewhere else.

Please post here, or email them anything useful you have. Trust me, it will help a great deal, and it will fix the problem in 1/10th of the time.

I know that Trizzo is running some script to check for problems, and we're about to do the same thing.

Thanks for listening...

Yea Metstaff!!
 

Sales are much better now YEAAA!!
AMEN METSTAFF :angrysoap

damn this seems to be continuing..

I see no problems... But sometimes... :Oh crap

Kind of hard for me to show a trace route when the problem appears to be intermittent. My numbers alone show that a lot of people aren't making it through the join process I dont have fucking time to baby sit. Redirect to Paycom.

A full fucking week. What a joke.

maybe the ccbill servers need to be moved to Isprime :thumbsup

seems ok at this end!

tony

Don't try to be a smart ass, do you think their network admins don't know that?
What makes you think they don't have CCIEs who know 10fold what you think you know?

DDoSes, on a massive scale, are very hard to deal with. Look at what happened to SCO and windowsupdate - both of those are highly publicized cases that most people should be familiar with. In both cases, there was nothing that either company could do to stay online in the short term - the strategy was to move servers to geographically redundant locations, making use of many upstream providers, and provide each bank of servers with filtering hardware and plenty of bandwidth.

Works for me
 

Both the admin and signup pages work for me.... that and I am getting sales. What pages cant you guys load?? Signups or admin?? I have normal sales as well so must be isolated if at all.....

Greetings:

It just so happens that in my past life I was an internationally renown computer security expert :thumbsup

HAHAHA

past life??!!?? So you invented computers I assume!! Too funny!

Some people have problems loading anything at all, some people can access it just fine. It appears to be a routing issue, thus the need for the traceroutes.

That only goes up to a gig, you'd need maybe ten of them against a serious DDOS and the bandwidth to feed it. I know they're also a hosting co. but that's a lot of bits for anyone to handle.

There are however companies that specialize in solving these kinds of problems.

I'd like to know exactly how much traffic is causing their problem, and whether its a packetflood or HTTP based attack.

Dos attack?

LDS
As long as you have some past transaction history of some kind, you can usually be placed with a merchant account. I've placed merchants that do anywhere from 2k a month to 3 mill pm and they've all been happy.

The reason most say you should be doing X amount in volume is because of the monthly fees. There are also sometimes jurisdictional incorporation fees but those are dependant on which banking solution is chosen. At one time the monthly fees were pretty outrageous but times have changed and so have the fees with many banks.

for example:
US merc monthly maintenance - $12 , monthly minimum - $25
Non US monthly maintenance - from $50 -$150, monthly minimum - from $0 to $150 (depending on the bank used)

If you are interested, I'd be happy to talk one-on-one with you to see if we can find a reliable solution for you .. just hit my email anytime :)

Works fine for me. I check everyday and haven't noticed anything different.

just got a slug of new sales after a mediocre day.

but recurrings are WAY off---hope they'll continue to try the pickup the recurrings.

yup, that's why i switched us to Epoch for primary lately

We were down for like a week due to a ddos, might even be the same person/company behind it, the point is we came out the other end and in better shape, we have better security in place and we compensated our affiliates for any downtime. Lets see what CCBill do? I send them a solution over a week ago which would have got them up in 3-6 hours, but they have not spent the $$ To do it, this makes me think that customers will be lost.

Your Name?
I was in the 'blackhat scene', if you're "internationally renowned" then I'll recognize the name :winkwink: