Monitor the health and performance of FiveM and related services
1176
Total Tracked Servers
24/7
Uptime Goal
99.9%
Availability
Track recent platform incidents and their resolutions
Apr 30, 23:09 UTC
Resolved - Nucleus is now operating normally again, and you should be able to connect.
Apr 30, 22:49 UTC
Monitoring - A fix has been implemented and we are monitoring the results.
Apr 30, 22:47 UTC
Identified - The issue has been identified and a fix is being implemented.
Apr 30, 22:38 UTC
Investigating - Our Nucleus proxy is currently experiencing issues, leading to users.cfx.re URLs for your server not working properly. We are actively working on a fix.
Apr 8, 17:55 UTC
Resolved - The fix has now been rolled out - thanks for your patience and our apologies for the inconvenience.
Apr 8, 17:38 UTC
Identified - The issue has been found and a fix will be deployed in the next few minutes.
Apr 8, 17:26 UTC
Investigating - We are aware of the issue with unstable/canary clients and are actively working on a fix.
Switching to production branch may currently corrupt your game install, please wait for us to release a fix.
Apr 8, 07:20 UTC
Completed - All done!
Apr 8, 07:00 UTC
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Apr 1, 10:51 UTC
Scheduled - Our forum will be undergoing routine maintenance, this will not impact playability. Authentication for Cfx.re services and Tebex may be intermittently unavailable in the maintenance period.
Apr 7, 12:40 UTC
Resolved - New game builds containing the fix have now been deployed to our release/production channels. Our apologies for the inconvenience.
Apr 7, 12:36 UTC
Update - New game builds are now being deployed.
Apr 7, 12:15 UTC
Identified - We are aware of the "Unable to resolve dependency for ros-patches[0.0.0.0]" error when launching FiveM or RedM. New builds containing the fix are being built and are expected to be deployed in the next 30min. We will provide further updates.
Feb 27, 09:53 UTC
Resolved - This incident has been resolved.
Feb 27, 02:48 UTC
Monitoring - We have implemented a fix and will be monitoring over the next few hours.
Feb 27, 01:28 UTC
Identified - The issue has been identified and a fix is being implemented.
Feb 27, 00:21 UTC
Investigating - We are currently investigating an issue with our runtime service. Connections to servers will take more time than usual until we bring back the service online.