BerryByte Outage History

Started Oct 30, 2026, 04:06 PM UTC· resolved Oct 30, 2026, 07:31 PM UTC

1. investigating Oct 30, 2026, 04:06 PM UTC

   Type: Incident Affected Components: Game Servers Oct 30, 16:06:07 GMT+0 Investigating - We are currently investigating this incident..

2. resolved Oct 30, 2026, 07:31 PM UTC

   Type: Incident Duration: 3 hours and 26 minutes Affected Components: Game Servers Oct 30, 19:31:56 GMT+0 Resolved - This incident has been resolved.. Oct 30, 16:06:07 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Oct 21, 2026, 08:30 AM UTC· resolved Oct 21, 2026, 10:39 AM UTC

1. investigating Oct 21, 2026, 08:30 AM UTC

   Type: Incident Affected Components: VPS Services, Dedicated Servers, Game Servers Oct 21, 08:30:00 GMT+0 Investigating - We are currently investigating this incident..

2. resolved Oct 21, 2026, 10:39 AM UTC

   Type: Incident Duration: 2 hours and 10 minutes Affected Components: VPS Services, Dedicated Servers, Game Servers Oct 21, 10:39:57 GMT+0 Resolved - This incident has been resolved.. Oct 21, 08:30:00 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Oct 03, 2026, 11:18 PM UTC· resolved Oct 04, 2026, 05:22 AM UTC

1. resolved Oct 04, 2026, 05:22 AM UTC

   Type: Incident Duration: 6 hours and 4 minutes Affected Components: US East 2 (Ashburn, VA) Oct 4, 05:22:35 GMT+0 Resolved - This incident has been resolved.. Oct 4, 00:00:00 GMT+0 Monitoring - We have not observed any further packet loss over the past 30 minutes, and affected machines appear to be stable. We are still waiting on confirmation from our data center provider regarding the root cause, so we're continuing to monitor closely.. Oct 3, 23:18:23 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Jul 08, 2026, 09:24 AM UTC· resolved Jul 08, 2026, 09:57 AM UTC

1. resolved Jul 08, 2026, 09:57 AM UTC

   Type: Incident Duration: 33 minutes Affected Components: , US West (Seattle, WA) → Jul 8, 09:57:44 GMT+0 Resolved - This incident has been resolved.. Jul 8, 09:30:08 GMT+0 Identified - We are currently in the process of migrating the server to replacement hardware.. Jul 8, 09:24:53 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Jun 02, 2026, 08:16 AM UTC· resolved Jun 02, 2026, 08:33 AM UTC

1. resolved Jun 02, 2026, 08:33 AM UTC

   Type: Incident Duration: 17 minutes Affected Components: , EU West (London, UK) → Jun 2, 08:33:54 GMT+0 Resolved - This incident has been resolved.. Jun 2, 08:16:48 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started May 18, 2026, 06:15 PM UTC· resolved May 21, 2026, 03:23 PM UTC

1. postmortem May 21, 2026, 03:23 PM UTC

   Type: Incident Duration: 2 hours and 46 minutes May 21, 15:23:30 GMT+0 Postmortem - Over a roughly 24-hour period, some users may have experienced intermittent errors or unavailability on services hosted on the `aiba` hypervisor. **What happened** The hypervisor experienced a hardware fault (CPU cooler failure), and we temporarily migrated its workload to a backup machine to keep services running. About a day later, the backup machine developed a separate hardware issue (memory instability) that caused the disruption during this window. We have repaired the original hypervisor and migrated the workload back to it to restore service.. May 18, 21:01:14 GMT+0 Resolved - This incident has been resolved. A full RFO (reason for outage) will follow within the next couple days.. May 18, 20:54:46 GMT+0 Monitoring - We implemented a fix and are currently monitoring the result.. May 18, 18:15:26 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started May 14, 2026, 12:52 PM UTC· resolved May 14, 2026, 01:39 PM UTC

1. resolved May 14, 2026, 01:39 PM UTC

   Type: Incident Duration: 47 minutes Affected Components: Legacy Billing / Client Area May 14, 13:39:07 GMT+0 Resolved - This incident has been resolved.. May 14, 12:52:03 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started May 12, 2026, 04:20 AM UTC· resolved May 12, 2026, 04:54 AM UTC

1. postmortem May 12, 2026, 04:54 AM UTC

   Type: Incident Duration: 21 minutes May 12, 04:54:49 GMT+0 Postmortem - On 2026-05-12 at approximately 04:02 UTC, the `rene: vps-dfw-7950X` hypervisor became unreachable due to a kernel fault on the host. The host was recovered via power cycle and all VMs returned to service automatically. **Timeline (UTC)** * 04:02 - Hypervisor (and subsequent VMs) stopped responding to network and console. * 04:07 - NOC alerted; investigation began. * 04:16 - Out-of-band investigation confirmed the host was wedged at the kernel level and not recoverable in software. * 04:25 - Host was forcefully power-cycled. Boot and VM auto-start completed within a few minutes. * 04:29 - All VMs confirmed running. We've identified the kernel condition that caused the host to hang and applied a configuration change to prevent it from recurring. Additional monitoring has been added to detect early warning signs of this class of issue across our fleet. We're sorry for the disruption. If you're still experiencing issues with your VM, please contact support and we'll take a look.. May 12, 04:41:53 GMT+0 Resolved - This incident has been resolved.. May 12, 04:32:34 GMT+0 Monitoring - We implemented a fix and are currently monitoring the result.. May 12, 04:20:58 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Apr 25, 2026, 05:55 AM UTC· resolved Apr 25, 2026, 12:13 PM UTC

1. resolved Apr 25, 2026, 12:13 PM UTC

   Type: Incident Duration: 6 hours and 18 minutes Affected Components: US East (Valley Forge, PA) Apr 25, 12:13:16 GMT+0 Resolved - This incident has been resolved.. Apr 25, 05:55:44 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Apr 10, 2026, 12:39 PM UTC· resolved Apr 10, 2026, 12:54 PM UTC

1. resolved Apr 10, 2026, 12:54 PM UTC

   Type: Incident Duration: 15 minutes Affected Components: , EU West (London, UK) → Apr 10, 12:54:46 GMT+0 Resolved - This incident has been resolved.. Apr 10, 12:42:04 GMT+0 Monitoring - A fix was implemented by Cosmic and we are currently monitoring the result.. Apr 10, 12:39:40 GMT+0 Investigating - We are currently investigating this incident. Seems to only affect connections between both regions..

Read the full incident report →

Started Apr 03, 2026, 05:30 AM UTC· resolved Apr 03, 2026, 06:31 AM UTC

1. resolved Apr 03, 2026, 06:31 AM UTC

   Type: Incident Duration: 1 hour and 1 minute Affected Components: , , EU Central (Germany), EU West (London, UK) → US Central (Dallas, TX) → Apr 3, 06:31:39 GMT+0 Resolved - This incident has been resolved.. Apr 3, 05:42:40 GMT+0 Monitoring - Cosmic has implemented a fix and we are currently monitoring the result. Ref: <https://status.as30456.net/cmnigw4ki0ejswkl8ij6nn44f>. Apr 3, 05:30:53 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Mar 25, 2026, 06:19 AM UTC· resolved Mar 25, 2026, 09:28 AM UTC

1. resolved Mar 25, 2026, 09:28 AM UTC

   Type: Incident Duration: 3 hours and 9 minutes Affected Components: , US Central (Dallas, TX) → Mar 25, 09:28:41 GMT+0 Resolved - The issue has been resolved, and all services are now running on temporary replacement hardware. We’ll schedule maintenance in the next couple of weeks to migrate services back to the original hardware after resolving the issues on it.. Mar 25, 08:51:22 GMT+0 Identified - The machine is now back online. However, due to ongoing issues with the host operating system, we will be migrating all customers to another machine temporarily. This will allow us to reinstall and rebuild the original machine on a new host OS. Once the reinstall is complete and stable, we’ll migrate all customers back to it.. Mar 25, 07:31:01 GMT+0 Identified - We are continuing to work on a fix for this incident.. Mar 25, 06:19:58 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Mar 23, 2026, 09:40 AM UTC· resolved Mar 23, 2026, 04:30 PM UTC

1. resolved Mar 23, 2026, 04:30 PM UTC

   Type: Incident Duration: 6 hours and 50 minutes Affected Components: , EU West (London, UK) → Mar 23, 16:30:09 GMT+0 Resolved - This incident has been resolved.. Mar 23, 15:41:49 GMT+0 Monitoring - CosmicGuard has now fixed the issue, and we are continuing to monitor the situation to ensure everything remains stable.. Mar 23, 14:53:42 GMT+0 Identified - CosmicGuard (our DDoS mitigation partner) is still investigating the issue. You can monitor their progress here: <https://status.as30456.net/cmn31qz0511dmt3c6v3eht9fm>.. Mar 23, 10:19:21 GMT+0 Identified - Our DDoS mitigation partner, CosmicGuard, has identified an issue on their end and is currently investigating. We’ll provide updates as more information becomes available.. Mar 23, 09:40:17 GMT+0 Investigating - We are currently investigating this incident. This issue seems to be primarily affecting UDP connections..

Read the full incident report →

Started Mar 04, 2026, 03:07 PM UTC· resolved Mar 04, 2026, 05:26 PM UTC

1. resolved Mar 04, 2026, 05:26 PM UTC

   Type: Incident Duration: 2 hours and 19 minutes Affected Components: , US West (Seattle, WA) → Mar 4, 17:26:42 GMT+0 Resolved - This incident has been resolved.. Mar 4, 15:46:34 GMT+0 Identified - We are continuing to work on a fix for this incident.. Mar 4, 15:07:21 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Feb 26, 2026, 09:27 AM UTC· resolved Feb 26, 2026, 04:43 PM UTC

1. resolved Feb 26, 2026, 04:43 PM UTC

   Type: Incident Duration: 7 hours and 16 minutes Affected Components: EU Central (Germany) Feb 26, 16:43:18 GMT+0 Resolved - This incident has been resolved.. Feb 26, 14:38:11 GMT+0 Identified - We are continuing to work on a fix for this incident.. Feb 26, 11:45:03 GMT+0 Identified - We are continuing to work on a fix for this incident.. Feb 26, 09:27:44 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Feb 16, 2026, 11:00 PM UTC· resolved Feb 16, 2026, 11:09 PM UTC

1. resolved Feb 16, 2026, 11:09 PM UTC

   Type: Incident Duration: 9 minutes Affected Components: , EU West (London, UK) → Feb 16, 23:09:00 GMT+0 Resolved - This incident has been resolved.. Feb 16, 23:00:00 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Jan 29, 2026, 09:28 AM UTC· resolved Jan 29, 2026, 10:58 AM UTC

1. resolved Jan 29, 2026, 10:58 AM UTC

   Type: Incident Duration: 1 hour and 30 minutes Affected Components: Asia (Singapore) Jan 29, 10:58:51 GMT+0 Resolved - This incident has been resolved.. Jan 29, 09:32:54 GMT+0 Identified - We have identified the issue to be partial connectivity loss affecting specific regions. This has been escalated to the data center provider.. Jan 29, 09:28:27 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Jan 19, 2026, 02:36 PM UTC· resolved Jan 19, 2026, 04:57 PM UTC

1. resolved Jan 19, 2026, 04:57 PM UTC

   Type: Incident Duration: 2 hours and 21 minutes Affected Components: US East 2 (Ashburn, VA) Jan 19, 16:57:39 GMT+0 Resolved - This incident has been resolved.. Jan 19, 14:36:30 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Jan 06, 2026, 01:42 AM UTC· resolved Jan 06, 2026, 05:12 AM UTC

1. resolved Jan 06, 2026, 05:12 AM UTC

   Type: Incident Duration: 3 hours and 31 minutes Affected Components: US East 2 (Ashburn, VA) Jan 6, 05:12:45 GMT+0 Resolved - This incident has been resolved.. Jan 6, 01:42:10 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →

Started Dec 05, 2025, 09:55 AM UTC· resolved Dec 05, 2025, 11:01 AM UTC

1. resolved Dec 05, 2025, 11:01 AM UTC

   Type: Incident Duration: 1 hour and 6 minutes Affected Components: , US Central (Dallas, TX) → Dec 5, 11:01:19 GMT+0 Resolved - This incident has been resolved.. Dec 5, 09:55:03 GMT+0 Investigating - We are currently investigating this incident. This seems to be isolated with 1.1.1.1, and not 1.0.0.1 for nameservers.

Read the full incident report →

Started Dec 03, 2025, 06:58 AM UTC· resolved Dec 03, 2025, 07:06 AM UTC

1. resolved Dec 03, 2025, 07:06 AM UTC

   Type: Incident Duration: 8 minutes Affected Components: , EU West (London, UK) → Dec 3, 07:06:22 GMT+0 Resolved - This incident has been resolved.. Dec 3, 07:02:41 GMT+0 Monitoring - A fix was implemented and we are currently monitoring the result.. Dec 3, 06:58:19 GMT+0 Investigating - We are currently investigating this incident..

Read the full incident report →