Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

api.del.icio.us returning 503 error #38

Open
arestivo opened this issue Apr 6, 2015 · 9 comments
Open

api.del.icio.us returning 503 error #38

arestivo opened this issue Apr 6, 2015 · 9 comments

Comments

@arestivo
Copy link

arestivo commented Apr 6, 2015

In the past couple of days, api.del.icio.us has been returning a 503 error:

Failed to load resource: the server responded with a status of 503 (Service Unavailable: Back-end server is at capacity)

@sdarlington
Copy link

Since they don't seem to be bothered to reply: they were moving their data centres. Contrary to what their blog stated, the API was broken for the best part of a week.

@peoplemerge
Copy link
Contributor

I apologize for missing these until now. Normally with prod issues, I hear about them faster when you go through our ticketing system: [email protected]

Regarding 5xx errors, it may be true depending on what calls you were making, api.del.icio.us might have appeared down for the best part of the week. The only reports we got were from the users of the obsolete bookmarklet getting "rate limit exceeded" errors. It took the majority of the engineering team almost a whole day to isolate the bug and fix it.

But that was only for the rate limit exceeded messages. There was a full site outage for 20m on Friday Apr 3. Then there was another outage Monday Apr 6 for about 4 hours but only on the API. On Wed, there was an outage for 2 hours, also only on the API.

Is anyone currently having issues? If so, could you post a sample CURL?

@sdarlington
Copy link

The API was technically up but you had an invalid certificate until late Thursday or early Friday 10th. (I emailed feedback@ and support@ about this on 7th and 8th respectively.)

It appears to be working now.

@peoplemerge
Copy link
Contributor

Ah yes so that was you. True we did have certificate errors on icio.us. That screwup was my personal contribution and I was solely responsible but the fix was my contribution too :). Though in my defense, once we got your ticket on the 8th, it was fixed within 24 hours. Not too shabby for a free service, right??

@sdarlington
Copy link

At the risk of going very much off topic... I don't mean to disparage your work and my intention was not to "call you out" as much as note that the communication around the move could have been a lot better.

@peoplemerge
Copy link
Contributor

@sdarlington yes I appreciate the feedback.

There are currently very few channels we have to communicate with developers. It's a problem. If you have ideas I'm open to suggestions.

As to our current albeit limited channels: are you subscribed to the Delicious daily trending emails? We sent out a survey post-migration, and it's one of our limited means of reaching a larger section of our user base, including devs. Also we did display a banner on the Delicious site if you use it daily or even weekly.

@sdarlington
Copy link

It seems to me that if you're moving over to OAuth 2, you're missing a trick by not requesting contact details when people create a new app.

My main interface to Delicious is my own app (!), so I didn't see the email. I did see the blog albeit after the migration was complete (and before the SSL certificate was fixed).

@maidsforstl
Copy link

I'm trying to sign for del.icio.us from https://maidsforstl.com St. Louis house cleaning Services, but getting an error: Sign in error alert. Any help is apreciated

@sdarlington
Copy link

@maidsforstl Delicious was shut down months ago!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants