Author

Topic: problem fixed (Read 517 times)

newbie
Activity: 2
Merit: 0
May 26, 2013, 05:36:30 AM
#8
I'm also a Bitstamp user. I din't have any problems with it so far. I think it's the most reliable exchange service available at this moment.
newbie
Activity: 7
Merit: 0
May 25, 2013, 12:00:07 AM
#7
I've personally always found Bitstamp to be incredibly reliable. I've only ever had one problem with a withdrawal and that was sorted out in 4 hours! Smiley

Bitstamp is not scam. Support will answer within minutes. Do you create a ticket?

newbie
Activity: 13
Merit: 0
May 24, 2013, 11:21:45 PM
#6
I've personally always found Bitstamp to be incredibly reliable. I've only ever had one problem with a withdrawal and that was sorted out in 4 hours! Smiley
hero member
Activity: 588
Merit: 500
Hero VIP ultra official trusted super staff puppet
May 24, 2013, 01:08:56 PM
#5
Seems they (and some other payment services) were at the bitcoin conference and are back now catching up with the queue. Happens every year so far when we have a conference in the community, so much that it might be used later for an attack vector to be honest (maybe that's why MtGox didn't go).
member
Activity: 75
Merit: 10
May 24, 2013, 01:05:27 PM
#4
I was able to transfer a couple btc worth to ripple no problem yesterday, but today I tried to transfer some more ripple from bitstamp and as soon as I click on ripple it sends me to a page that says  Oops Internal Server Error.  Same for everyone else?
sr. member
Activity: 392
Merit: 250
May 23, 2013, 04:49:14 AM
#3
Wait is the solution of (almost) all your problems
full member
Activity: 147
Merit: 100
Make world a better place to live!!!
May 23, 2013, 04:45:59 AM
#2
Hello i just click their website thiw is what is writen:

<<  Website currently unavailable

The website you are trying to access is currently unavailable. Please try again at a later time.
If you are the site owner, here is a help resource to help resolve the issue.  >>

Any news for it will be helpfull.
member
Activity: 84
Merit: 10
May 22, 2013, 07:32:39 PM
#1
problem fixed
Jump to: