Friends Project - Notice history

Fix implemented and properly deployed

Cluster No.2 of an API has memory leak issues.

While investigating a root-cause. We've provided a fix by reloading all the workers inside that cluster.

Seems to be stable now.

The server recovered itself after getting 1.2k hitches in svNetwork thread.

We're suspecting this to be DDOS attack, But still finding root-cause.

We're still monitoring this issues.

We just resolved the issue!, Sorry for any inconvenience caused.

We implemented a fix and currently monitoring the result.

We've recovered the TS3 Server.

-- For this incident, We've losing all the trust to our datacenter. We'll find other datacenter that have suit all the requirement we want (uptime, network, security, etc.)

We've got the license and started to recovering the teamspeak server.

We've recovered Sentry server.

We're still waiting new TS3 server license key from our sponsor.

We've issued the OS reinstallation for Sentry.

For the TS3 Server, We're waiting for our sponsor to provide a license key.

The server is come back on but still unable to boot into its OS.

We're continuing trying to recover the server.

We still waiting a response from the datacenter regarding one of our server physical status that handle two component.

TS3 Server and Sentry seem to don't want to go back on yet. We're contacting our datacenter support to physically check the status of the server.

The datacenter power has come back on. But all servers affected in this incident have to be turned on again.

We're recovering our service as soon as possible. Sorry for any inconvenience this may cause.

Our datacenter is still fixing their UPS (uninterruptible power supply, uninterruptible power source) issues and don't have any update regarding this incident yet.

Our datacenter is still fixing their UPS issues and don't have any update regarding this incident yet.

Our datacenter is currently having UPS fault and the IDC is fixing their problem.

Looks like our datacenter or our core router is having an outage and causing these issues.

We're contacting our datacenter to find the root cause of this incident.

We are currently investigating this incident.

We've got contacted from our datacenter.

The cause of this incident was 3BB (Jastel Datacenter) is maintenance their network and the link gets switched from problem link to working link.

The problem will persist until 08:00 AM of 01/04/2022 [UTC+7]

The issues are from the provider side.

We're contacting our datacenter to get the information about this incident.

This incident has been resolved.

It appears to be the connection from 3BB to our service are slowly recovering.

We're currently monitoring this incident.

Things have returned to normal.

We appreciate your patience, sincere apologies for the inconvenience!

We're having some sort of bad network configuration recently going-on, Service are recovering.

We're sincerely apologize for any inconvenience caused by this incident.