Sign in to Bunker
OperationalBased on the latest supporting health checks
Bunker / Service status
Service health, specific checks and recorded uptime.
A clear view of the systems behind your game.
Current service health
Every enabled Bunker service is responding normally.
Based on the latest supporting health checks
Based on the latest supporting health checks
Based on the latest supporting health checks
Based on the latest supporting health checks
Based on the latest supporting health checks
Plan ahead
No upcoming maintenance is scheduled.
A clear record
We've resolved the issues on our end.
We are monitoring recovery after maintenance.
**Security Incident Update – Issue Identified** We have identified the cause of the current service disruption as a security incident involving our infrastructure provider, Railway. Railway has confirmed that an unauthorised third party may have accessed sensitive environment variables, including certain API keys and infrastructure credentials. As a precaution, The FUT Bunker has temporarily suspended access to its services while we complete a full security review. **🔐 Payment Security** We want to reassure members that this incident is not a reported breach of Stripe's payment-card storage systems. - Our previous Stripe API keys have been revoked and replaced. - All previous Stripe webhook signing secrets have also been revoked and replaced. - There is currently no indication that members' payment-card details held by Stripe have been compromised. - We are continuing to review our payment integrations for any suspicious activity. **🛡️ Infrastructure Security** Our development team is continuing to rotate remaining credentials, review affected services and verify the security of our infrastructure. Access to the Bunker Portal, API, Discord integrations and other connected services remains restricted as a precaution. **🚧 Service Restoration** Railway has begun restoring its deployment infrastructure, although its investigation and recovery work remain ongoing. The FUT Bunker will remain in maintenance mode until we are satisfied that our infrastructure and integrations are secure. We cannot yet provide an estimated restoration time. **Your security remains our priority.** We appreciate your patience and will continue providing updates as more information becomes available. **The FUT Bunker Development Team**
Emergency Security Maintenance We are temporarily taking all The FUT Bunker services offline following a security incident reported by our infrastructure provider, Railway. Railway has disclosed potential unauthorised access to environment variables containing sensitive credentials, including API keys and database credentials. As a precaution, we are taking the following actions: Temporarily suspending access to our services. Revoking and regenerating API keys, database credentials and authentication secrets. Reviewing relevant security logs for suspicious activity. Verifying the security of our infrastructure before restoring services. There is currently no confirmed evidence that The FUT Bunker's customer information has been accessed or compromised. Our investigation and precautionary security checks are ongoing. During this maintenance, the portal, account features, trading tools, subscriptions and other connected services may be temporarily unavailable. There is currently no confirmed restoration time. Services will be brought back online only after the necessary security checks have been completed. We apologise for the disruption and appreciate your patience. The FUT Bunker Development Team
The issue around the Player database has been resolved. All services are working normally.
We seem to have fixed the issue around the Player database issue and are monitoring the published fix.
We are investigating an issue around the player database.
Services should now start coming back online as normal.
Most of the Portal's data will be unreachable during this time; mainly targeted at the FUT Hub.
The connected platform
1d history · recorded every minute
Checks whether Bunker’s shared services and their required connections are responding.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 520 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether Bunker can reach its main data store.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 9 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks the service that helps protect Bunker from too many requests.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 2 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether boosting services can reach their data store.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 28 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether Bunker can connect to the player data service.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 42 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks the Discord connection and settings needed to sign in to your Bunker Account.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 471 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether Bunker can connect securely to Stripe for payments.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 246 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks for recent payment updates that are taking too long to activate purchases.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 10 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether membership records can be read and Premium access rules are working.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 11 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether the player data service and the services it needs are responding.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 33 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks the temporary storage used to serve player data quickly.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 2 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether the information needed to locate player datasets is available and valid.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 20 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether the giveaway bot and the services it needs are ready.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 520 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether the giveaway bot is connected to Discord.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 0 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether the giveaway service can reach its data store.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 28 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether giveaways can connect to Bunker’s shared services.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 457 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether the Portal’s health service and its connection to Bunker are responding.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 520 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Checks whether the Portal can connect to Bunker’s shared services.
2026-11-14 13:03 UTC – 2026-11-14 13:33 UTC · 100.00% uptime · 30/30 minutes observed · 461 ms average check time
Time taken by health checks, not page load, checkout or sign-in speed. Missing measurements stay gaps. Use the history slider for interval details.
Stay in the loop
Get incident and maintenance emails from [email protected]. Confirm your email to start; unsubscribe whenever you like.
Built on observations
The backend records checks even when this page is closed. This view refreshes every 30 seconds. Monitoring currently shares the backend infrastructure.
Uptime is the share of observed minutes that were operational. Degraded and outage minutes lower uptime; missing checks lower coverage. Planned maintenance does not erase failed checks. Lighter bars indicate partial coverage. All times are UTC.
History accumulates from the day each check is enabled. A yearly view does not imply a year of observations.