Maxs

#2438-Again server down issue facing
Maxs

#1 Maxs
Maxs

Hello team, please check again server was down for 26 minutes at midnight of your and mine timezone.


@stats.uptimerobot.com.../796562949


humble request to resolve this issue permanently.

#2 Admin.
Admin.

This is unacceptable. The worst part is that messages aren't marked as read, making it impossible to have a smooth workflow.

#3 Kamrul Hasan
Kamrul Hasan
#2

Admin.

Dear user,


Read/unread issue has been resolved.


Thank you

#4 PrimeX
PrimeX
#3

Kamrul Hasan

Hello Kamrul. The server is down again please do the needful urgently.


1768220907_Screenshot%202026-01-12%20at%204.26.34%E2%80%AFPM.png



#5 Maxs
Maxs
#4

PrimeX

Yes server was down today evening... bs team please resolve

#6 Kamrul Hasan
Kamrul Hasan

We were updating BotSailor, and the process took only a few minutes—no more than 2–3 minutes. Thank you.


Best regards,

Kamrul Hasan

#7 Maxs
Maxs
#6

Kamrul Hasan

Great so can you share what you have updated during that time?

#8 PrimeX
PrimeX
#6

Kamrul Hasan

Hello Kamrul Hasan,


This is not about whether the downtime was 2 minutes or 3 minutes.


The core issue is impact of downtime happened during working hours and there was no prior notice about maintenance or updates. Any unannounced downtime directly affects live operations and client communication.


If updates can cause even a short outage you guys should inform users in advance a simple maintenance notice would prevent confusion and repeated escalation.

#9 Sales
Sales

Load Balancer is a requirement as user growth increases, not an option.

#10 Maxs
Maxs
#9

Sales

BS team already using load balancer.. they have to only inform us before pushing an update.

#11 PrimeX
PrimeX
#10

Maxs

Exactly you are right they need to streamline the process and make the updates publicly available. They should also publish them on the roadmap features which they have been unable to do for a long time.

#12 Sarower Hasan
Sarower Hasan

Dear Users,


Thank you for taking the time to share your concerns. We understand the urgency and concerns you’ve raised, and we take them very seriously. Our team is continuously working to improve system stability, update transparency, and overall service reliability to ensure a smoother experience.

We truly appreciate your patience, understanding, and continued support as we make these improvements. Please feel free to reach out if you have any further concerns or suggestions.


Thank you.

#13 BotSailor
BotSailor

Thank you for sharing this earlier.


We’d like to confirm that BotSailor has completely restructured its backend infrastructure since then. The platform has gone through deep code, database, and system-level optimizations, and our server architecture has been upgraded to a multi-node environment with load balancing across multiple high-capacity servers.


As a result, BotSailor is now significantly faster, highly stable, and operating without unplanned downtime.


We appreciate the early feedback — it played an important role in helping us build a much stronger and more scalable platform.



#14 Maxs
Maxs
#13

BotSailor

Hi Team,

Thank you for the update and for sharing the improvements made to infrastructure.

It’s great to hear that the backend has been fully restructured and that the platform is now running on a multi-node, load-balanced architecture. The focus on performance, stability and scalability is reassuring and I appreciate you taken feedback seriously and finally resolved an performance issue.


Thank you.

#15 Maxs
Maxs

@stats.uptimerobot.com.../796562949

In last 6 Hours Server was down for 67 Minutes.


BS team please fix this issue on priority already from last 3 days Intent detection was not working with AI and now server down issue started.



#16 PrimeX
PrimeX

Hello BS Team,


The service was down yesterday. It happened again today.


There has been no official update no incident report and no proactive communication from your side.


This is not acceptable for a platform used in daily operations.


Just 2 weeks back you guys confirmed that the infrastructure was restructured, upgraded to multi node architecture and operating without unplanned downtime. Yet we are still facing repeated outages.


Today we informally came to know that there was a DDOS attack with a significant influx of requests. If this is the reason, why was there no immediate official communication to users?


When incidents happen, professional platforms:

• Share real time updates.

• Confirm the root cause.

• Provide estimated resolution time.

• Publish a post incident report.


If this is due to a DDOS attack, what mitigation systems are in place? Was the load balancing and upgraded architecture not designed to handle this?


At this stage, the bigger concern is not just downtime. It is the lack of transparency and seriousness in handling production level disruptions.