there is some problem with blockchain.info since last some days
have seen many members complaining different issues with them in last few days
hope they will fix it soon
Topic: Blockchain.info conformation email not being recieved (tried for a few days) (Read 1225 times)
November 01, 2014, 03:06:36 PM
November 01, 2014, 08:20:09 AM
I use the email provider Yandex which is only being used for this I've used them for years for all different types of things and I think they are reliable and great. But everytime I try sending the verfication email to verify my email at blockchain it never gets to my inbox, spam or anything. I've checked my filters and nothing at all is black listed.
Is this a problem with Yandex or Blockchain.info itself? I've tried for the past 48 hours on and off waiting hours inbetween requests.
If any one has any ideas or solutions then please let me know I'll be very grateful. I don't really want to change from yandex as outlook is my other alternative and I only use them for disposable or 1 site inboxes. The Yandex email I have created will be used for Bitcoin related accounts & emails.
I've never had a problem with Yandex before and if I have they have sorted it within 24 hours but I don't think Yandex is at fault this time and that's why I've held from contacting support. I have done a few internet searches and found that this is indeed a common problem with the blockchain.info API.
Is this a problem with Yandex or Blockchain.info itself? I've tried for the past 48 hours on and off waiting hours inbetween requests.
If any one has any ideas or solutions then please let me know I'll be very grateful. I don't really want to change from yandex as outlook is my other alternative and I only use them for disposable or 1 site inboxes. The Yandex email I have created will be used for Bitcoin related accounts & emails.
I've never had a problem with Yandex before and if I have they have sorted it within 24 hours but I don't think Yandex is at fault this time and that's why I've held from contacting support. I have done a few internet searches and found that this is indeed a common problem with the blockchain.info API.
Jump to: