Dear customers and API users: qwerly.com/letter.html

@CbStoleMySocks we know, we know :)

@CbStoleMySocks ello

Finished the month with 2020 developers on the API. Thanks for all the support!

RT @youcvcom En youcv.com utilizamos el API de Qwerly, pruébalo, te sorprenderá :)

What a great idea! They get a $10k referral fee for a hire: http://j.mp/pGzuTc

We'll be down from now for, hopefully, no more than a couple of hours.

There may be a small amount of downtime today as we're doing some work on the production databases.

We are recommending a 24 hour wait time between 202s going forward, given large queues from our big customers.

We just broke 1,500 developers on the Qwerly API. Thanks for the support, everyone!

.Qwerly t-shirts are here. Develop a library for the API (http://qwer.ly/iorNNp), get a shirt! http://twitpic.com/5wl0w7

Thanks @livelinkuk! Drupal module for Qwerly http://bit.ly/npxjCL #drupal

Things are looking better now. Sorry for the downtime.

Qwerly is experiencing issues at the moment. We're working on it and will let you know when we're back to working order.

Looks like the issue has been fixed and full service restored. Thanks for your patience.

Customers signed up today will meet "dev. not active" messages from the Mashery proxy. They're aware of the issue and are working on it now.

STATUS: Qwerly processing time once again under 30 seconds (low queues).

Heavy loads on the Qwerly API continue. Please expect 202s to resolve within 24 hours, unlike the usual 30 seconds.

Sorry about the longer wait times for resolving 202s at the moment. We've been experiencing huge volumes for the last 48 hours.