Hello,
I cannot login to
Anyone knows whats going on there?
same here. Cannot login to
I love how they dont bother to post a message or a note here for example, or on their site, when there is a problem ... or at least send an email to their paying customers ...
The interface was working about 2 hours ago, then stopped. Zeropark is also down, shows error.
But traffic routing seems to be working correctly, so hope it's just client side issue.
same issue here. it seems to be some global amazon / AWS problem. Also all hasoffers networks I'm working with didnt count leads anymore from 11:35 CET.
It is working for me now
CR is very low here,lost money...
did the issue affect your CR?
Cr on
Update: It does look like the conversions are slowly starting to populate in voluum.
same here... wtf...been down for almost 12 hours now.
Front end was down, and as some mentioned, CR seems to be way down. Hope I get paid for the unreported leads.
Edit: 2/3 of leads are not reported on aff network (judging by sudden unexplainable CR drop) as well for some 3/4 hours now.
They should seriously work a bit on their PR, paying close to $1000 per month for a service and not hearing a word from them when they run into problems kinda sucks...
Same here, cannot load the UI, now it works, but missing up to 50% of conversions..
It was a global AWS outage, see here:
http://venturebeat.com/2015/09/20/am...dium-and-more/
One of my offers was not working for a couple of hours....the redirect between network and offer was down.
Does anyone know a good service/tool to monitor uptime of websites/offers including the redirect?
An service where I can plugin in my affiliate link from the aff network and the service/tool monitors all redirects along the way?
Update - check how my EPC has dropped for past 3 hours on aff network NOT only
*3AM-7AM was low volume so EPC is not statically significant in that time frame.

Hi,
Firstly, sincere apologies for the inconvenience and frustration caused by this incident.
It originated from a temporary AWS downtime yesterday afternoon for their US East (Virginia) server that affected many other services.
During the downtime, campaigns which were targeted to the US may have incurred slight discrepancies in the amount of traffic and inbound conversions handled.
Subsequently, as our US east server is specifically used to also process outbound postbacks to a third-party (source) , conversion discrepancies may also be apparent within your reports source-side.
From our own cross-analysis of traffic handled before, during and after the outage, approximately only 0.08% of traffic wasn’t accounted for during the downtime.
Due to the extent of the fault with AWS, we couldn't easily disable the region to route requests to the next nearest server in Oregon (US west) as a counter measure.
That is, It started with DynamoDB not working and thus resulted in many other AWS services not working at the same time.
As you can imagine, incidents like this are frustrating both for us internally and subsequently our userbase.
Moving forward, we have already started work on
We're meeting today to map-out dependencies that may have broken, in addition to creating fail-safe procedures for future instances of downtime.
Our ultimate goal is to be able to handle complete AWS region downtime and eliminate situations like this completely.
In addition to this, users may have also faced issues with logging-in to their
Users that were already logged-in could continue to work during this period, same for users accessing our mobile apps.
For those of you who were directly affected by this incident, kindly contact our support team by submitting a ticket via the support tab in your Voluum panel.
Alternatively, you can also submit a ticket directly to us via: tickets@voluum.uservoice.com
Best regards,
Adrian