BitLaunch Outage History

BitLaunch is up right now

Pingoru has recorded 49 incidents for BitLaunch: 8 in the last 12 months and 3 in the last 90 days.

Source: status.bitlaunch.io

49incidents recorded
8last 12 months
3last 90 days
11 hourstypical duration

Incidents, newest first

Critical September 10, 2026 Outage in Los Angeles 13h 47m LAX1

Started Sep 10, 2026, 07:30 AM UTC· resolved Sep 10, 2026, 09:18 PM UTC

  1. investigating Sep 10, 2026, 07:30 AM UTC

    We are currently investigating this issue.

  2. resolved Sep 10, 2026, 09:18 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical April 29, 2026 London Outage 1h 6m LON1

Started Apr 29, 2026, 12:42 PM UTC· resolved Apr 29, 2026, 01:48 PM UTC

  1. investigating Apr 29, 2026, 12:42 PM UTC

    There is currently an outage in our London location. We have contacted our upstream to investigate this issue.

  2. monitoring Apr 29, 2026, 01:15 PM UTC

    Service has been restored. However, our upstream network team is currently checking in with their own upstream, as their handoff link experienced a disruption.

  3. resolved Apr 29, 2026, 01:48 PM UTC

    This incident has been resolved.

Read the full incident report →

Major March 5, 2026 BitLaunch Amsterdam (AMS2) Outage 23h 56m

Started Mar 05, 2026, 09:06 AM UTC· resolved Mar 06, 2026, 09:02 AM UTC

  1. investigating Mar 05, 2026, 09:06 AM UTC

    We are currently investigating this issue.

  2. investigating Mar 05, 2026, 09:12 AM UTC

    This appears to be an upstream outage, however our team is continuing to investigate.

  3. investigating Mar 05, 2026, 09:35 AM UTC

    We are awaiting further updates from our upstream. This issue appears only to affect internet connectivity.

  4. identified Mar 05, 2026, 10:15 AM UTC

    Upstream have identified an issue with routing and are working to fix it. More information will be provided here as we receive it.

  5. identified Mar 05, 2026, 11:03 AM UTC

    We're still awaiting a resolution from our upstream.

  6. identified Mar 05, 2026, 12:14 PM UTC

    The issue has been traced to a core router. Upstream is working to fix the issue.

  7. identified Mar 05, 2026, 03:05 PM UTC

    Our upstream network team is still actively working to resolve the issue affecting one of the core routers in the Amsterdam region. At this time, the investigation and remediation are ongoing, and we unfortunately do not have a confirmed ETA yet. Please be assured that their engineers are prioritizing this matter and are working diligently to restore full service as quickly as possible.

  8. identified Mar 05, 2026, 07:19 PM UTC

    One of our upstream's QFX router aggregation members has failed, and our cabinet/equipment has uplink connections through this device, causing the outage. The data center team is investigating and performing a hard reboot of the switch.

  9. resolved Mar 06, 2026, 09:02 AM UTC

    A replacement switch has been successfully installed, and network connectivity has been restored.

Read the full incident report →

Minor February 1, 2026 Degraded Performance in Dallas 1d DAL1

Started Feb 01, 2026, 11:54 AM UTC· resolved Feb 02, 2026, 12:00 PM UTC

  1. identified Feb 01, 2026, 11:54 AM UTC

    Connectivity issues are currently impacting this region. Our upstream is currently working on improving stability in this region.

  2. identified Feb 01, 2026, 09:57 PM UTC

    We are continuing to work on a fix for this issue.

  3. monitoring Feb 02, 2026, 09:44 AM UTC

    A fix has been implemented and we are monitoring the results.

  4. resolved Feb 20, 2026, 11:58 PM UTC

    This incident has been resolved.

Read the full incident report →

Major July 22, 2025 BitLaunch LAX outage 11h 59m LAX1

Started Jul 22, 2025, 10:38 PM UTC· resolved Jul 23, 2025, 10:38 AM UTC

  1. investigating Jul 22, 2025, 10:38 PM UTC

    We are currently investigating a network outage in LAX. We'll provide any updates here.

  2. identified Jul 22, 2025, 11:31 PM UTC

    The issue appears to be with a failed PDU which is being replaced now.

  3. monitoring Jul 22, 2025, 11:52 PM UTC

    The issue was with a circuit breaker which has now been replaced. Services should be back to normal.

  4. resolved Jul 23, 2025, 10:38 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical July 8, 2025 Outage in Bucharest 1h 17m BUC1

Started Jul 08, 2025, 05:43 PM UTC· resolved Jul 08, 2025, 07:01 PM UTC

  1. investigating Jul 08, 2025, 05:43 PM UTC

    Unfortunately we're experiencing a further issue in this region. We are working diligently to bring it back online with increased network performance in the region.

  2. monitoring Jul 08, 2025, 06:29 PM UTC

    Network connectivity is restored

  3. resolved Jul 08, 2025, 07:01 PM UTC

    Network as been restored and is now at double capacity. We apologize for the downtime that this caused.

Read the full incident report →

Minor July 4, 2025 Small Delay Processing Payments 4h 50m Payments

Started Jul 04, 2025, 07:36 AM UTC· resolved Jul 04, 2025, 12:27 PM UTC

  1. identified Jul 04, 2025, 07:36 AM UTC

    We have identified an issue with our payment system which will result in a small delay before transactions are credited. We expect this to be resolved sometime soon.

  2. resolved Jul 04, 2025, 12:27 PM UTC

    This incident has been resolved.

Read the full incident report →

Critical June 25, 2025 Outage in our Los Angeles region 1h 13m LAX1

Started Jun 25, 2025, 07:54 AM UTC· resolved Jun 25, 2025, 09:08 AM UTC

  1. investigating Jun 25, 2025, 07:54 AM UTC

    We are currently investigating this issue.

  2. investigating Jun 25, 2025, 08:06 AM UTC

    We have contacted our upstream to receive information on the nature of the outage

  3. monitoring Jun 25, 2025, 08:40 AM UTC

    Connection has been restored and we're looking into the cause of the issue with our upstream

  4. resolved Jun 25, 2025, 09:08 AM UTC

    The issue was caused by a problem with our upstream's iBGP session. Their network team has identified the root cause and successfully resolved it.

Read the full incident report →

Major June 12, 2025 Issues with Login 1h 31m Web App

Started Jun 12, 2025, 07:03 PM UTC· resolved Jun 12, 2025, 08:34 PM UTC

  1. investigating Jun 12, 2025, 07:03 PM UTC

    We are currently experiencing issues with our login system. We're actively investigating this issue.

  2. identified Jun 12, 2025, 07:37 PM UTC

    The issue is related to the current widespread Cloudflare outage. Please let the support team know if you require any urgent assistance with your account and we can help.

  3. monitoring Jun 12, 2025, 08:30 PM UTC

    Logins are currently working as expected. We will continue to monitor.

  4. resolved Jun 12, 2025, 08:34 PM UTC

    This incident has been resolved.

Read the full incident report →

Major June 5, 2025 Amsterdam Outage 1h 27m AMS1

Started Jun 05, 2025, 10:01 AM UTC· resolved Jun 05, 2025, 11:28 AM UTC

  1. investigating Jun 05, 2025, 10:01 AM UTC

    It looks like our upstream is currently experiencing some issues with network connectivity and as a result of this, occasional disconnects are occurring. We are requesting further information

  2. monitoring Jun 05, 2025, 10:49 AM UTC

    Network connectivity has been restored and we are continuing to monitor for further incidents

  3. resolved Jun 05, 2025, 11:28 AM UTC

    This incident has been resolved.

Read the full incident report →

Critical March 16, 2025 Chicago networking outage 8h 2m CHI1

Started Mar 16, 2025, 09:39 AM UTC· resolved Mar 16, 2025, 05:41 PM UTC

  1. investigating Mar 16, 2025, 09:39 AM UTC

    We are currently investigating this issue.

  2. identified Mar 16, 2025, 09:43 AM UTC

    We have confirmed that this is an issue with our upstream and we have contacted them for a resolution.

  3. identified Mar 16, 2025, 10:21 AM UTC

    We are continuing to push our upstream for a resolution.

  4. identified Mar 16, 2025, 11:16 AM UTC

    We are continuing to push our upstream for a resolution.

  5. identified Mar 16, 2025, 12:00 PM UTC

    Our upstream are reporting an issue with one of their switches which they are working to resolve.

  6. identified Mar 16, 2025, 02:09 PM UTC

    We are continuing to push our upstream for updates. Unfortunately the issue is largely out of our control at this point - we'll provide updates as soon as we have them.

  7. identified Mar 16, 2025, 02:33 PM UTC

    A fix is being deployed and we are working with our upstream to restore the connection.

  8. identified Mar 16, 2025, 04:01 PM UTC

    We are continuing to work on a fix for this issue.

  9. identified Mar 16, 2025, 05:27 PM UTC

    We believe the switch is replaced at this point and we're monitoring the situation.

  10. identified Mar 16, 2025, 05:31 PM UTC

    We are continuing to work on a fix for this issue.

  11. monitoring Mar 16, 2025, 05:31 PM UTC

    A fix has been implemented and we are monitoring the results.

  12. resolved Mar 16, 2025, 05:41 PM UTC

    We have received confirmation from our upstream that this event is resolved: > One of the TOR switches experienced a failure, impacting the virtual chassis and causing downtime. Our network engineers determined the switch is beyond recovery and requires replacement. To restore connectivity, we have moved your uplink to a functioning switch. Connectivity has been successfully restored.

Read the full incident report →

Major January 21, 2025 Node issue in London 38m LON1

Started Jan 21, 2025, 11:36 AM UTC· resolved Jan 21, 2025, 12:15 PM UTC

  1. investigating Jan 21, 2025, 11:36 AM UTC

    We are working with datacenter technicians to diagnose an issue with a physical host in our London region. Some user servers will be affected.

  2. identified Jan 21, 2025, 11:44 AM UTC

    Unfortunatetly despite best efforts of technicians, it looks as though this physical host is not able to be recovered. We will be contacting affected users shortly.

  3. resolved Jan 21, 2025, 12:15 PM UTC

    We have contacted all users affected by this hardware issue. Please reach out to our support if you have any questions.

Read the full incident report →

Critical November 10, 2024 Payments Interrupted 3h 12m Payments

Started Nov 10, 2024, 07:16 PM UTC· resolved Nov 10, 2024, 10:28 PM UTC

  1. investigating Nov 10, 2024, 07:16 PM UTC

    We are currently investigating this issue.

  2. resolved Nov 10, 2024, 10:28 PM UTC

    This incident has been resolved.

Read the full incident report →