Join BoxWorks in San Francisco Nov 12-13! Keynotes, product demos, and Box Master Classes. Reserve your spot!

Comments

7 comments

  • geoff-kt

    It looks like the service has recovered. We have not seen an error since 2017_02_23T14:01:13.500Z (GMT).

    0
    Comment actions Permalink
  • learnupon

    Confirming we were seeing it too (on all requests). Seems OK now again.

    0
    Comment actions Permalink
  • geoff-kt

    We saw another period of errors from 2017_02_23T14:09:28Z (GMT) to 2017_02_23T14:10:56Z (GMT).

    0
    Comment actions Permalink
  • learnupon

    We're still getting intermittent 502 (bad gateway) errors as well (on SVG page loads)

    0
    Comment actions Permalink
  • Murtza

      Thanks for reporting this issue. As mentioned in this thread, there was a service issue with the View API earlier today. We posted a note on our status page with more information. 

    0
    Comment actions Permalink
  • jbowler

    We are seeing a number of 502s come in today -- is there another problem? The status page is still green.

    0
    Comment actions Permalink
  • Howard

    Hi ,

     

    Thanks for your post and yes we've updated the status page: https://status.box.com/ to identify this 502 error.

     

    "Investigating - We are investigating reports of issues establishing connections to our Content API. Some requests may return a 502 error response with the description “Could Not Connect”. We are actively investigating and will provide further updates as soon as possible."

    0
    Comment actions Permalink

Please sign in to leave a comment.