Websocket GET System Status
Introduction
We added a websocket topic to check the system status. This helps us tell you faster if the system is down for maintenance or broken. It doesn't cover normal updates.
URL
- Mainnet:
wss://stream.bybit.com/v5/public/proxy
info
- Turkey users registered from "www.bybit-tr.com", please use
wss://stream.bybit-tr.com/v5/public/proxy
- Kazakhstan users registered from "www.bybit.kz", please use
wss://stream.bybit.kz/v5/public/proxy
- Testnet:
wss://stream-testnet.bybit.com/v5/public/proxy
Topic:
system.status
Response Parameters
Parameter | Type | Comments |
---|---|---|
topic | string | Topic name |
ts | number | The timestamp (ms) that the system generates the data |
data | array | Object |
> id | string | Id. Unique identifier |
> title | string | Title of system maintenance |
> state | string | System state |
> begin | string | Start time of system maintenance, timestamp in milliseconds |
> end | string | End time of system maintenance, timestamp in milliseconds. Before maintenance is completed, it is the expected end time; After maintenance is completed, it will be changed to the actual end time. |
> href | string | Hyperlink to system maintenance details. Default value is empty string |
> serviceTypes | array<int> | Service Type |
> product | array<int> | Product |
> uidSuffix | array<int> | Affected UID tail number |
> maintainType | string | Maintenance type |
> env | string | Environment |
Subscribe Example
{"op": "subscribe", "args":["system.status"]}
Response Example
{
"topic": "system.status",
"ts": 1751858399649,
"data": [
{
"id": "4d95b2a0-587f-11f0-bcc9-56f28c94d6ea",
"title": "t06",
"state": "completed",
"begin": "1751596902000",
"end": "1751597011000",
"href": "",
"serviceTypes": [
2,
3,
4,
5
],
"product": [
1,
2
],
"uidSuffix": [],
"maintainType": 1,
"env": 1
}
]
}