HTTP/2 302
server: nginx
date: Sat, 02 Aug 2025 20:46:49 GMT
content-type: text/plain; charset=utf-8
content-length: 0
x-archive-redirect-reason: found capture at 20100521174149
location: https://web.archive.org/web/20100521174149/https://status.twitter.com/
server-timing: captures_list;dur=0.665976, exclusion.robots;dur=0.023913, exclusion.robots.policy;dur=0.011327, esindex;dur=0.013532, cdx.remote;dur=16.881688, LoadShardBlock;dur=494.526196, PetaboxLoader3.datanode;dur=267.210018, PetaboxLoader3.resolve;dur=54.603126
x-app-server: wwwb-app217
x-ts: 302
x-tr: 623
server-timing: TR;dur=0,Tw;dur=0,Tc;dur=0
set-cookie: wb-p-SERVER=wwwb-app217; path=/
x-location: All
x-rl: 0
x-na: 0
x-page-cache: MISS
server-timing: MISS
x-nid: DigitalOcean
referrer-policy: no-referrer-when-downgrade
permissions-policy: interest-cohort=()
HTTP/2 200
server: nginx
date: Sat, 02 Aug 2025 20:46:51 GMT
content-type: text/html; charset=UTF-8
x-archive-orig-date: Fri, 21 May 2010 17:41:49 GMT
x-archive-orig-server: Apache/2.2.3 (Red Hat)
x-archive-orig-x-tumblr-perf: "ch:4/rate-limiter,tumblelog_id_for_host,tumblelogs,auto cm:0/ ce:0/ c:0/0 d:0/0 e:0/0 auto-hit"
x-archive-orig-p3p: CP="ALL ADM DEV PSAi COM OUR OTRo STP IND ONL"
x-archive-orig-x-tumblr-user: twitterstatus
x-archive-orig-set-cookie: tmgioct=nj66zQpRPsUDi3CndzjBekaW; expires=Mon, 18-May-2020 17:41:37 GMT; path=/; httponly
x-archive-orig-etag: 7d641b516e4fb032e894edc4b529eefb
x-archive-orig-link:
; rel=icon
x-archive-orig-content-length: 17761
x-archive-orig-x-cache-auto: hit
x-archive-orig-vary: Accept-Encoding
x-archive-orig-x-tumblr-usec: D=27372
x-archive-orig-x-cache: MISS from rack1.tumblr.com
x-archive-orig-x-cache-lookup: MISS from rack1.tumblr.com:80
x-archive-orig-via: 1.0 rack1.tumblr.com:80 (squid/2.6.STABLE6)
x-archive-orig-connection: close
x-archive-guessed-content-type: text/html
x-archive-guessed-charset: utf-8
memento-datetime: Fri, 21 May 2010 17:41:49 GMT
link: Twitter Status
Users are seeing an elevated number of errors on twitter.com and we’re working to recover from this problem.
We pushed out a change today that disabled the feature which keeps you logged in when you close your browser. It will be available again shortly.
We have been experiencing increasing latency over the past week that is affecting both twitter.com and the Twitter API. We have identified some potential solutions and are working to resolve the issue.
