Backendless not accessible right now

Bug
1

Application ID: 4A47197B-AE30-FA84-FF56-0071F4010900

Oops. An internal error [8289eef71bdc3fb185dac2a437ce0429] has occurred. We are working on it. Please try again later

Problem description

Describe what you did in console that led to the error. Please provide a description of what actually happens. Be descriptive: “it doesn’t work” does not describe what the behavior actually is. This will help us with reproducing the problem.

We are just opening a method and it’s taking some time to load.

And we are getting this error at the moment. and we can’t check it because of the issue where Backendless takes time to load.

image
image785×132 12.4 KB

image
image722×305 8.05 KB

2

As we have just discussed in Slack, I have acknowledged the problem.
Channel: general - Backendless - 477 new items - Slack 2024-03-25 16-54-46

1 Like
3

@mark-piller Hi, do we have any ETA for the issue?

4

Unfortunately we don’t have an ETA. It was not a scheduled maintenance downtime. We are not taking any breaks from fixing it and it is the highest priority

2 Likes
5

The service has been restored

1 Like
6

Are you saying it is 100%? I just had a cloud service die with “Task execution is aborted due to timeout”.

7

I was misinformed in the local messages. Sorry, it has been hectic. We’re still doing some additional work.

8

Is there a chance that the service isn’t going to be back up and stable tonight?

9

All in due time, Team. I’m sorry this is happening.

10

We are stabilizing it by the minute. Console and all API services should be up now. If you see anything odd, please let us know.

Regards,
Mark

11

Is there ANY chance a long service call could still time out?

12

Hi, @Kelly_Oglesby

Everything should work fine now. Do you still have any issues?

Regards,
Serhiy

1 Like
13

image
image1202×347 15.9 KB

I also got a message:

14

I have the same problem now.

15

We are also experience the issue and can not access the platform.

Request URL: https://develop.backendless.com/console/status
Request Method: GET
Status Code: 500 Internal Server Error

16

Guys, I just posted an update on our blog describing the problem and what we are doing about it:

I appreciate your patience with us; I understand how frustrating it is. We are doing everything we can to restore the system.

Regards,
Mark