I can log in, but I'm getting a 503 with the following: "Something is technically wrong.
Thanks for noticing—we're going to fix it up and have things back to normal soon."
Back up, and they sent out a message on status.twitter.com:
Update [12:12pm PDT]: During a planned deploy in one of our core services, we experienced unexpected complications that made Twitter unavailable for many users starting at 11:01am. We rolled back the change as soon as we identified the issue and began a controlled recovery to ensure stability of other parts of the service. The site was fully recovered by 11:47am PDT. We apologize for the inconvenience.
There will be a lot of graphs that don't look great around the operations team. I wonder how much of an impact each minute that the service is down has on their uptime %.
[+] [-] rubiquity|12 years ago|reply
http://imgur.com/eb3AbX6
[+] [-] Timothee|12 years ago|reply
From http://www.copyright.gov/title17/92chap4.html#401:
If a notice appears on the copies, it shall consist of the following three elements:
(1) the symbol © (the letter C in a circle), or the word “Copyright”, or the abbreviation “Copr.”; and
(2) the year of first publication of the work
If they haven't touched this page since 2012 (totally reasonable), I think it should be 2012.
This blog post (http://www.photoattorney.com/qa-what-year-should-i-use-for-m...) also mentions that you can use a range for when it covers multiple years of publication (like a blog).
[+] [-] ErikAugust|12 years ago|reply
That's what most people used JavaScript for before AJAX...
[+] [-] GuerraEarth|12 years ago|reply
[+] [-] stronglikedan|12 years ago|reply
[+] [-] koenigdavidmj|12 years ago|reply
[+] [-] caio1982|12 years ago|reply
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] aaronmarks|12 years ago|reply
[+] [-] crabasa|12 years ago|reply
"Service issue - Most users are experiencing issues accessing Twitter on web and mobile apps. We’re looking into it."
http://status.twitter.com/
[+] [-] sc30317|12 years ago|reply
Update [12:12pm PDT]: During a planned deploy in one of our core services, we experienced unexpected complications that made Twitter unavailable for many users starting at 11:01am. We rolled back the change as soon as we identified the issue and began a controlled recovery to ensure stability of other parts of the service. The site was fully recovered by 11:47am PDT. We apologize for the inconvenience.
[+] [-] NiVanc|12 years ago|reply
[+] [-] gioi|12 years ago|reply
[+] [-] erichurkman|12 years ago|reply
[+] [-] MrEliasen|12 years ago|reply
[+] [-] beat|12 years ago|reply
[+] [-] aalpbalkan|12 years ago|reply
Twitter is currently down for maintenance. We expect to be back shortly. For more information, check out Twitter Status. Thanks for your patience!
This is too bad. It comes if you refresh enough. But in the middle of the day, why would they do maintenance? Sorry Raffi, you failed this time.
[+] [-] gabriel|12 years ago|reply
[+] [-] gtirloni|12 years ago|reply
[+] [-] scotthtaylor|12 years ago|reply
[+] [-] Xylakant|12 years ago|reply
Well, that's simple math: A year has roughly 525600 minutes, that makes one minute about 0.000190258752 % of the potential uptime.
Monthly, weekly, daily uptime calculations are left as an exercise to the reader, as well as proper calculations for leap years.
[+] [-] gtirloni|12 years ago|reply
[+] [-] aSp1de|12 years ago|reply
http://geopeeker.com/fetch/?url=http%3A%2F%2Fwww.twitter.com
[+] [-] scotthtaylor|12 years ago|reply
Next best thing, post to HN.
Down in London, UK.
[+] [-] The_Shrike|12 years ago|reply
[+] [-] shamsulbuddy|12 years ago|reply
[+] [-] unknown|12 years ago|reply
[deleted]
[+] [-] Aqueous|12 years ago|reply
Maybe: Technically, something is wrong.
Or: Something is wrong with our technology.
[+] [-] afandian|12 years ago|reply
[+] [-] julespitt|12 years ago|reply
[+] [-] agumonkey|12 years ago|reply
[+] [-] seleucia|12 years ago|reply