The place to discuss how to make 23 work in special ways with the 23 api

../services/upload/ not completing anymore

Th Clvr Mnky   February 26, 2011, 02:41 PM

As of 9AM EST I'm finding that /upload works, but it is not returning a valid response. It is timing out at my end.

I can't really say if this is a problem on my net, but I can get to other places, and some REST calls to 23 still work.

[9:48EST] Works now.

[10:03EST] REST and POST calls are breaking intermittently. Arbitrary calls are timing out constantly.

 
Steffen Fagerström Christensen Team 23   February 26, 2011, 05:34 PM

We had some trouble during the night (European time, which collides with this) resulting in about 20m of collective downtime within a span of 3-4 hours. Hopefully, these error are related to that -- can you give it another try and see if stuff works now?

/Stc

 
Th Clvr Mnky   February 26, 2011, 06:31 PM

Oh man, I'm getting terrible pings from my node:


PING 23hq.com (77.66.17.58) 56(84) bytes of data.
64 bytes from 77.66.17.58: icmp_req=1 ttl=51 time=306 ms
64 bytes from 77.66.17.58: icmp_req=2 ttl=51 time=221 ms
64 bytes from 77.66.17.58: icmp_req=3 ttl=51 time=218 ms
64 bytes from 77.66.17.58: icmp_req=4 ttl=51 time=220 ms
64 bytes from 77.66.17.58: icmp_req=5 ttl=51 time=218 ms
64 bytes from 77.66.17.58: icmp_req=6 ttl=51 time=218 ms
64 bytes from 77.66.17.58: icmp_req=7 ttl=51 time=222 ms
^C64 bytes from 77.66.17.58: icmp_req=8 ttl=51 time=219 ms

--- 23hq.com ping statistics ---
8 packets transmitted, 8 received, 0% packet loss, time 38796ms
rtt min/avg/max/mdev = 218.008/230.711/306.428/28.657 ms

[Later]

Wait, that's totally wrong. This is also counting my wi-fi hop. Here's the values from the edge box, closest to my provider:

PING 23hq.com (77.66.17.58): 56 data bytes
64 bytes from 77.66.17.58: icmp_seq=0 ttl=52 time=162.121 ms
64 bytes from 77.66.17.58: icmp_seq=1 ttl=52 time=138.887 ms
64 bytes from 77.66.17.58: icmp_seq=2 ttl=52 time=134.720 ms
64 bytes from 77.66.17.58: icmp_seq=3 ttl=52 time=137.585 ms
64 bytes from 77.66.17.58: icmp_seq=4 ttl=52 time=139.194 ms
64 bytes from 77.66.17.58: icmp_seq=5 ttl=52 time=134.277 ms
64 bytes from 77.66.17.58: icmp_seq=6 ttl=52 time=138.526 ms
64 bytes from 77.66.17.58: icmp_seq=7 ttl=52 time=134.225 ms
64 bytes from 77.66.17.58: icmp_seq=8 ttl=52 time=134.156 ms
64 bytes from 77.66.17.58: icmp_seq=9 ttl=52 time=137.452 ms
64 bytes from 77.66.17.58: icmp_seq=10 ttl=52 time=138.105 ms
64 bytes from 77.66.17.58: icmp_seq=11 ttl=52 time=139.995 ms
64 bytes from 77.66.17.58: icmp_seq=12 ttl=52 time=134.954 ms
64 bytes from 77.66.17.58: icmp_seq=13 ttl=52 time=140.525 ms
--- 23hq.com ping statistics ---
14 packets transmitted, 14 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 134.156/138.908/162.121/6.810 ms

Sorry about that.

 
Th Clvr Mnky   February 26, 2011, 07:05 PM

But, yeah, things are sloooow, which might be part or all of the problem. Even posting to this group is slow.

I'll check back later tonight. Need to run some errands.

[Later]

Things seem to be back to normal. I can upload and replace photos with no significant problems.

 




About 23

About 23
What is 23 and who's behind the service?
Just In
Discover the world from a different angle.
Here's a crop of the latest photos from the around the world.
Search
Search photos from users using 23
Help / Discussion
Get help or share your ideas to make 23 better
23 Blog / 23 on Twitter
Messages and observations from Team 23
Terms of use
What can 23 be used for and what isn't allowed
More services from 23
We also help people use photo sharing in their professional lives
RSS Feed
Subscribe to these photos in an RSS reader
  • Basque (ES)
  • Bulgarian (BG)
  • Chinese (CN)
  • Chinese (TW)
  • Danish (DK)
  • Dutch (NL)
  • English (US)
  • French (FR)
  • Galician (ES)
  • German (DE)
  • Italian (IT)
  • Norwegian (NO)
  • Polish (PL)
  • Portuguese (PT)
  • Russian (RU)
  • Spanish (ES)
  • Swedish (SE)

Popular photos right now